Privacy policy
Effective 15 November 2026
This policy explains what personal data LSP SOFTWARE LTD collects when you use the hosted DotRelay service at dotrelay.dev, why, and what rights you have. DotRelay is pre-release software: features and this policy may change, and we will update the effective date when they do.
Who we are
LSP SOFTWARE LTD (company number 14566565, registered office Unit 82a James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE) is the data controller for the hosted service. Contact us at [email protected].
If you use a DotRelay server that someone else runs (a self-hosted instance), that operator controls your data there, and this policy does not apply to it.
What we cannot see
Your devices encrypt your variables before they leave them. We store only the encrypted result and never receive the keys to open it. That covers variable names, values and descriptions. Your encryption password, recovery code and passkey secrets never leave your devices. If you lose every device and your recovery code, we cannot recover your data for you.
DotRelay uses classical (not post-quantum) cryptography. Anyone you share a project with can read its values and keep copies, and removing them later does not erase what they already have.
What we collect
- Your GitHub account: your numeric GitHub user ID, username, display name, email address and avatar URL, received when you sign in.
- GitHub access tokens: the tokens issued to the DotRelay GitHub App on your behalf, stored encrypted. We use them only to look up repositories and accounts you ask DotRelay to link or invite. They are never sent to your devices.
- Sessions: sign-in sessions, with the IP address and browser or CLI user agent that created them.
- Teams and projects: team names, memberships, roles, invitations, the GitHub repositories linked to projects, and environment labels such as “production”. These are not end-to-end encrypted.
- Devices: each device's public keys and its display details (name, operating system and client type).
- Encrypted data and its metadata: the encrypted variables, keys and history, plus who published each change, from which device, when, and how large it was. We keep a record of administrative actions such as invitations, removals and device revocations.
- Security logs: IP address, endpoint, response status and transfer size for requests, used to detect abuse.
We do not use analytics, advertising or tracking cookies, and we do not sell personal data.
Why we use it
- To provide the service you signed up for: signing you in, syncing your encrypted data, and managing teams and devices (performance of our contract with you).
- To email you about your account and your teams, such as invitations, notices that project keys were shared with you, and notices to team owners and admins when someone joins (performance of our contract with you).
- Where you have agreed, or where the law otherwise allows, to send you news and offers about DotRelay. You can opt out at any time using the link in each email.
- To keep the service secure: rate limits, abuse detection and investigating incidents (our legitimate interest in protecting the service and its users).
- To meet legal obligations where they apply.
Cookies and local storage
We set one essential cookie, which keeps you signed in. The web app stores this browser's device keys and settings in your browser (IndexedDB and local storage); that data stays on your machine. The CLI stores its keys and session in its local configuration directory.
Who we share it with
We use these providers to run the hosted service. They process data only on our instructions.
| Provider | Purpose | Location |
|---|---|---|
| GitHub, Inc. | Sign-in, and looking up repositories and accounts on your behalf through the DotRelay GitHub App | United States |
| Hetzner Online GmbH | Servers that run DotRelay and hold its database | Finland |
| Cloudflare, Inc. | DNS, TLS and network protection in front of the service | Global network |
| Backblaze, Inc. | Database backups | United States (US East) |
| Resend, Inc. | Transactional email delivery (invitations and key-sharing notices) | United States |
Where data is transferred outside the UK, we rely on the safeguards UK data protection law provides for such transfers, such as adequacy regulations or standard contractual clauses. We may also disclose data when the law requires it.
How long we keep it
- Security logs: 30 days.
- Diagnostic logs, which never contain your values: 14 days.
- Sessions: until you sign out, or at most 30 days after last use and 90 days after sign-in.
- Expired sign-in codes, device enrollments and invitations: deleted automatically after they expire.
- Account, team and encrypted data: while your account exists. A project's signed history is kept so every member can verify it, including changes made by people who have since left.
- Database backups follow our backup provider's rotation and are overwritten over time.
Your rights
Under UK data protection law you can ask to access, correct or delete your personal data, to restrict or object to how we use it, and to receive it in a portable form. Email [email protected] and we will respond within one month. Deleting your account removes your account data; some records, such as signed history in projects other members still use, may be kept in a form that no longer identifies you where we can, or for as long as that project exists.
You can also complain to the Information Commissioner's Office (ico.org.uk), though we would appreciate the chance to help first.
Children
DotRelay is not intended for anyone under 16.
Changes
We will update this page and its effective date when this policy changes, and tell signed-in users about significant changes.