Privacy Policy

Last updated: July 25, 2026

RegSecure is built on a zero-content-backend architecture. We have no application servers that process or store your user content — video calls, documents, signatures, recordings, and chat messages stay in your browser and travel peer-to-peer. Our infrastructure is limited to: Cloudflare (serves the static app bundle, terminates TLS at the edge), a stateless signaling relay (helps browsers find each other), and STUN/TURN servers for NAT traversal. See Section 4 for the precise data exposure at each layer.

1. Who We Are

RegSecure® is a product of Particular Ltd. ("we," "us," "our"). Our platform provides encrypted video consultations, document signing, file sharing, session recording, and chat for regulated industries.

Contact: contact@regsecure.com

2. Our Architecture — Why This Policy Is Short

Unlike traditional SaaS platforms, RegSecure has no application servers that process or store user content, no databases, and no file storage. The static application bundle is served via the Cloudflare CDN (which terminates TLS at the edge and sees only the request for the bundle, not session content). A stateless signaling relay helps browsers find each other (it never sees your media, messages, or keys) and standard STUN/TURN servers handle NAT traversal. All session content is processed entirely within your browser and transmitted peer-to-peer using end-to-end encrypted WebRTC connections.

We cannot decrypt or store your session content. The application bundle is served via the Cloudflare CDN; session traffic (audio, video, documents, signatures) is browser-to-browser and never traverses our application servers. The infrastructure breakdown in Section 4 lists every party that sees any byte of network traffic and exactly what they can see.

3. What We Do and Do Not Collect

Data Type	Collected?	Details
Video & audio streams	No	Peer-to-peer via WebRTC. Never touches our servers.
Documents & signatures	No	Transferred via encrypted WebRTC data channel.
Session recordings	No	Recorded locally in your browser's memory (RAM). Never uploaded.
Chat messages	No	Sent via encrypted data channel. Not stored anywhere.
Shared files	No	Transferred peer-to-peer via encrypted WebRTC data channel. Never stored on any server.
User accounts / passwords	No	RegSecure does not require registration or login.
Cookies	No	We do not use cookies.
Analytics / tracking	No	No analytics scripts, no tracking pixels, no third-party analytics.
Connection signaling data	Transient only	Connection setup messages (HTTPS REST polling, no WebSockets) pass through our relay server to establish P2P connections. These are not logged or stored, and the relay holds them only in volatile memory (rooms expire after 2 hours). Once the peer-to-peer connection is established, the relay is no longer involved — with one narrow exception: Safety-Code verification messages. These are a pair's own confirmation ("codes match" / "don't match") and, if any pair reports a mismatch, a session-wide alert notifying every other participant. They are normally sent directly peer-to-peer, but fall back to the relay when the direct channel is unavailable. All of them are end-to-end encrypted (AES-256-GCM under ECDH keys), so the relay forwards ciphertext it cannot read or forge, and none are ever stored.
IP addresses	Transient only	Standard web server logs may temporarily contain IP addresses at the infrastructure level (Cloudflare, Hetzner). We do not actively collect or analyze these.

4. Third-Party Services & Infrastructure

Every party that sees any byte of network traffic on the path between your browser and your peer — plus the out-of-band services that monitor our infrastructure — and exactly what they can see:

Service	Purpose	Data Exposure
Cloudflare (CDN & proxy)	Serves the static application bundle for both `regsecure.com` and `app.regsecure.com`. Terminates TLS at the edge.	Sees the request for the application bundle (IP, URL, headers) on initial page load. Does not see session content — once the app is loaded, audio, video, documents, signatures, and chat travel browser-to-browser and do not pass through Cloudflare. Subject to Cloudflare's standard DPA.
Hetzner (signaling relay, `relay.regsecure.com`)	HTTPS REST signaling for connection setup. Held in volatile memory only (2 h room TTL).	Transient signaling messages (SDP, ECDH public keys), plus — only as a fallback when the direct peer-to-peer channel is unavailable — end-to-end-encrypted Safety-Code verification messages (a pair's own confirmation, and the session-wide mismatch alert) the relay cannot read or forge. No media, document, signature, or chat content. Not logged or written to disk.
Self-operated TURN/STUN servers on Hetzner (EU — Nuremberg, and US — Ashburn)	Self-operated relay in two regions (EU and US) for redundancy. Handles STUN for NAT discovery, and TURN forwarding of encrypted packets when direct peer-to-peer fails; your browser uses whichever region connects.	STUN binding: your client's public IP is visible to this self-operated host only — no public STUN provider (e.g. Google) is used. TURN relay: encrypted packet bytes only; cannot decrypt (DTLS-SRTP for media, ECDH-AES-256-GCM for the data channel). Zero retention: server logs are disabled at the daemon level — connection metadata is not retained.
UptimeRobot (uptime monitoring) and ntfy.sh (capacity alerts)	External monitoring that verifies our servers are online and alerts us before capacity limits are reached.	Operational metadata only: whether a public endpoint responds, and aggregate server-load figures contained in our own alert messages. These services are not on the session path and never receive session content, documents, identities, or any user data — which remains end-to-end encrypted and never reaches our servers in readable form.

None of these services have access to your video, audio, documents, signatures, recordings, or chat messages.

5. Data Retention

Since we do not collect user content, there is nothing to retain. Session data exists only in participants' browsers during active sessions and is lost when the browser tab is closed.

If you make a recording, it exists only in your browser's memory until you download it or close the tab. We never have access to recordings.

6. Your Rights

Because we do not collect or store personal data from your sessions, traditional data subject rights (access, deletion, portability) do not apply to session content — we simply do not have it.

If you have questions about any data that may exist in infrastructure logs (such as IP addresses in Cloudflare or server logs), you may contact us at contact@regsecure.com and we will respond within 30 days.

7. Children's Privacy

RegSecure is intended for professional use in regulated industries. We do not knowingly provide services to children under 16. If you believe a child has used RegSecure, please contact us.

8. Security

All media streams are encrypted using DTLS-SRTP (mandatory in WebRTC). Data channel communications — chat, documents, signatures — are additionally end-to-end encrypted at the application layer with AES-256-GCM under keys derived via ECDH, on top of the DTLS transport. These protocols operate end-to-end between participants.

Our relay server handles only connection signaling (and, as a fallback when a direct peer-to-peer channel is unavailable, end-to-end-encrypted Safety-Code verification messages it cannot read or forge) — it never has access to encryption keys or session content.

If any pair's Safety-Code verification fails, every participant in the session — including the host — is alerted immediately, and the host can end the session for everyone.

9. International Data Transfers

Session content travels directly between participants' browsers (peer-to-peer), so in the normal case there is no international transfer of your content. When a direct connection isn't possible (e.g. symmetric NAT), media is relayed through a self-operated TURN server; these are located in Germany (Hetzner, EU — Nuremberg) and the United States (Hetzner, US — Ashburn), and your client uses whichever region connects. Anything passing through a TURN server is end-to-end encrypted and cannot be read by it (DTLS-SRTP for media, AES-256-GCM for the data channel). The static application files are served via Cloudflare's global CDN, and the stateless signaling relay is located in Germany (Hetzner, EU).

10. Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated date. If we make material changes to how we handle data, we will provide notice on our website.

11. Contact

If you have questions about this privacy policy or our data practices:

Particular Ltd.
Email: contact@regsecure.com
Website: regsecure.com