Privacy policy
Effective 2026-11-15. What we see, what we keep, what we never have.
What the relay never has
The content your application exchanges. Frames are encrypted on the devices with keys derived there; the relay forwards ciphertext and keeps none of it.
What we record and why
- Developer account: email, name, hashed password, API tokens — to run your console and bill you.
- End-user accounts inside your application: email, hashed password, creation and last login — so your users can sign in on their devices. They are scoped to your application and never merged across applications.
- Device registry: what your application reports when a device registers — device name, platform, model, OS version, vendor identifier (iOS), Android ID, MAC address (desktop only; mobile systems do not expose it), hostname, OS user name, bundle identifier, app version, locale — plus the user agent and the IP addresses seen. Purpose: security of your users (showing which devices hold a session), enforcement that a key is used by its own application, and abuse investigation.
- Connection log: for each relay session: application, user, host and guest device, their IP addresses and user agents, start/join/end times, number of frames and bytes in each direction, end reason. Purpose: support, abuse detection, and your own visibility. Never the content.
- Events: failed logins, identity mismatches, payment refusals, key rotations, with IP address.
- Payments: amount, date, provider reference. Card data is handled by Stripe and never reaches us.
Who can see it
You see the registry, log and events of your own applications in the console, the developer API and the MCP. CybSin staff see all of it for operations and support. We do not sell or share it with third parties, except processors needed to run the service (hosting in Germany at Hetzner, Stripe for payments, email delivery from our own server).
Retention
Device registry and connection logs are kept for 12 months, then deleted. Account data is kept while the account exists and deleted within 90 days of termination. Payment records are kept as long as accounting law requires.
Your users
You are the controller for your application's users; we process on your behalf. Your application's privacy policy should mention that pairing and relay metadata is processed by CybSin as described here.
Rights and contact
Access, correction and deletion requests: support@cybsin.com. We answer within 30 days.