H2Z Riser
TRUST CENTER

How video gets from the recorder to your phone, and who can open it.

The encrypted path, the keys, what leaves the site, and what isn't done yet. Each item carries its real status. Last updated October 24, 2026.

01 · THE ENCRYPTED PATH

End-to-end encrypted, by design.

Video is encrypted on the recorder and opened in the app. Nothing in between holds a key to it: not our cloud, and not the relay.

The app and the recorder each generate their own key pair, and the private keys stay on the device. They connect over QUIC, and each end proves its key in the handshake. The connection layer is the open-source iroh library.

The app tries the local network first, then a direct connection across the internet. If neither works, a relay forwards the encrypted packets as a last resort. The app shows which path it is on. Verification on shipping hardware is in progress (section 05).

AT THE SITERiser recorderencrypts the videoholds its own keyIN YOUR HANDRiser appopens the videoholds its own key1 · LOCAL NETWORK, OR 2 · DIRECT OVER THE INTERNET3 · RELAYfallback only · forwards encrypted packets it cannot openOUR CLOUDsign-in, permissions, auditno video · no key to the video
TRANSPORTQUIC between two keyed endpoints
PATHLocal network, then direct, then relay as fallback
OUR CLOUDSign-in, permissions and audit. No video.
02 · KEYS AND PERMISSIONS

Every request is checked at the recorder.

Access is granted with short-lived signed credentials. Each one is tied to a specific phone and limited to what that person needs. A copied credential does not work on another phone.

The recorder checks each credential itself. Access you remove is dropped quickly.

A recorder is claimed in person, by scanning a code at the device. Nothing is forwarded or exposed at the customer's firewall, and off the local network a recorder is reached only through the Riser app.

01Scan at the deviceclaim, in person02Admin signswho, what, until when03Recorder checksevery request04App connectsoutbound onlyno inbound portsRevoke an access and the recorder drops it quickly.
CREDENTIALSShort-lived, signed, limited in scope
CHECKEDAt the recorder
CLAIMIn person, at the device
INBOUND PORTSNone
03 · DATA FLOWS

What stays on site, and every connection that leaves it.

Live video and all recordings stay on site, with camera and recorder passwords, exported clips and the motion and event index used for search.

To verify it, put the recorder behind a firewall that logs outbound traffic. You should see only the four destinations below.

AT THE SITERiservideo stays hereCoordinationIDs, no videoRelayEncrypted, unreadableUpdate serverVersion, hardware typeLanguage modelOnly tasks you approveFour outbound connections. Everything else stays on site.
STAYS ON SITEVideo, recordings, passwords, clips, search index
LEAVESOnly the four connections in the table
SERVER ACCESS TODAYThe founder only
OUTBOUND CONNECTIONWHAT IT IS FORWHAT IT CARRIESOPERATED BY
Coordination serviceRegisters accounts and recorders, issues short-lived access tokens, distributes the revocation listAccount and device identifiers. No video.H2ZTECH
RelayForwards traffic between the app and the recorder when a direct connection can't be madeEncrypted traffic the relay cannot open.H2ZTECH
Update serverDelivers signed software updatesVersion number and hardware typeH2ZTECH
Language-model serviceUsed during setup tasks you start and approve: mapping the network, identifying devices, building the 3D site from a drawingThe drawing, device responses and network layout for that task. Never video, images or passwords.A third-party U.S. provider

Access to these servers today: the founder only. This page will name every person or role with access as that changes.

04 · WHAT THE PRODUCT LEARNS

Experience, not data.

Riser gets better at handling equipment. It does that without collecting anything about your customers.

Example of what may be shared, if you opt in: "Model X on firmware Y needs stream path Z." This boundary is part of the License Agreement.

MAY BE SHARED, IF YOU OPT INModel X, firmware YNeeds stream path ZThis symptom means that causeopt-inNEVER COLLECTEDCustomer names, addressesTopology, camera locationsDrawingsAny image or video
MAY BE SHAREDHow a model and firmware behave, the fix, the symptom
NEVER COLLECTEDNames, addresses, topology, drawings, images, video
05 · STATUS

Where each commitment stands today.

Each item carries its real state, and we update it as it changes. Details and links below.

Signed builds in our GitHub orgIN PROGRESSU.S. relay and update serversIN PROGRESSEnd-to-end path verified on hardwareIN PROGRESSThird-party penetration testNOT STARTEDVulnerability disclosureNOT STARTEDPrivacy, License, NDAA textsNOT STARTED
Code built and signed in H2ZTECH's GitHub organizationThe dependency list and signing key will be published here.IN PROGRESS
Relay and update servers in the United StatesProvider and region will be published here.IN PROGRESS
End-to-end path verified on shipping hardwareTest method and results will be published here.IN PROGRESS
Third-party penetration testSummary will be published here.NOT STARTED
Vulnerability disclosureReport to zhenghe@h2ztech.com. We acknowledge within 2 business days.NOT STARTED
Privacy Policy, License Agreement, NDAA StatementDrafted by H2ZTECH; attorney review before publication.NOT STARTED
06 · HOW SMALL THE CLOUD IS

Our cloud introduces. It doesn't hold your sites.

Recording, playback, search and on-site viewing do not call our servers. Video and recordings stay on your recorder and are never stored in our cloud.

Remotely, the cloud only helps the app and the recorder find and authorize each other. After that they talk directly wherever the network allows. We design to keep that role as small as possible.

AT THE SITE, NO CALL TO USRecordingPlaybackSearchOn-site viewingOUR CLOUDSign-inPermissionsIntroduces app and recorderno video
LOCALRuns without our cloud
VIDEOStays on your recorder
OUR CLOUDIntroductions and permissions only
07 · THE COMPANY

Who builds it.

H2ZTECH LLC is a Texas limited liability company based in Houston. It was founded by He Zheng.

Riser was started, developed and coded in the United States. Its source lives in H2ZTECH's GitHub organization, where every release is built and signed. H2ZTECH provides software only. Installation and on-site service stay with the integrator.

H2ZTECH LLCTexas LLC · Houston, TexasAI-native organizationSoftware onlyBuilt and signed in the U.S.He ZhengFounderBUILT IN THE U.S.Project started in HoustonResearch and developmentEvery line of codeReleases built and signedSoftware only. Installation and on-site service stay with the integrator.
BUILTStarted, developed and coded in the United States
SCOPESoftware only