What we hold, where it lives, and who else can see it.
Lingvo stores the strings you send it and the account that sent them. There is no advertising business here and no analytics vendor — the only reason we hold anything is to run the product you are paying for.
What we collect
Your account
Your name, email address and a password hash. We never store the password itself. If you joined by invitation we also keep who invited you, so a workspace owner can see how someone got access.
Your workspace content
The keys, source strings, translations, comments, glossary terms and file paths you push or type. This is the product — it is stored so it can be edited, exported and pulled back into your repository.
Operational records
Request logs, error traces and an activity trail of who changed what and when. Logs include IP addresses, which is unavoidable when running a network service and is what makes abuse and account compromise investigable.
What we do not collect
- No third-party analytics. The site and app load no external script of any kind.
- No advertising or marketing cookies, and no cross-site tracking.
- No tracking pixels in email. Our messages are plain text with no images.
- No payment card numbers — if and when card payments are added, the processor holds those details and we never see them.
The app stores three things in your browser's local storage: your session token, your light or dark theme choice, and — briefly — an invitation token while you finish signing up. None of them is a cookie and none is sent anywhere but to Lingvo.
Where it lives
The database and API both run in Sydney, Australia. Data is not copied to other regions except where a sub-processor below states otherwise.
| Provider | What it handles | Where |
|---|---|---|
| Neon | The Postgres database — every string and account record. | AWS ap-southeast-2, Sydney |
| Fly.io | Runs the API. Holds no data at rest beyond logs. | syd, Sydney |
| Cloudflare | Serves the website and terminates TLS. | Global edge |
| Brevo | Sends transactional email: resets, invitations, verification. | EU |
Machine translation and your strings
Nothing leaves Lingvo for a machine-translation provider until you ask for it. When you run a pre-translate or lingvo translate, the source strings for the keys you selected are sent to the provider you chose, and its reply comes back as a draft.
Which provider that is, is entirely your choice: Claude, OpenAI, DeepL, Google, LibreTranslate or MyMemory. Each has its own terms about retention and training, and those terms — not ours — govern what it does with the text once it arrives. If a provider's policy matters to you, choose accordingly, or do not use machine translation at all. Everything else in Lingvo works without it.
Who can see your content
Members of your workspace, according to the role you gave them. Owners and admins can change structure; translators can write translations; viewers can only read.
On our side, access to the production database is limited to the people operating the service, is used for support and incident response, and is not used to read workspace content otherwise. We do not sell data, and we do not train models on your strings.
Keeping and deleting
- Workspace content is kept until you delete it or close the account.
- Deleting a project removes its keys and translations; the deletion is not reversible from the interface.
- Operational logs are kept for a limited period and then discarded.
- Password-reset, invitation and verification tokens are stored hashed and expire on a fixed schedule.
- API tokens are stored hashed. A token shown once at creation cannot be recovered, only revoked and replaced.
Backups exist and are what a deleted record can briefly survive in. They roll over on their own schedule rather than being edited to remove single rows.
Your rights
You can export everything: lingvo export --bundle writes every locale in the format you configured, and needs no plan, no credits and no permission from us. That is deliberate — a localization tool you cannot leave is a hostage situation, not a product.
You can also ask us to correct or delete your personal data, or to tell you what we hold. Depending on where you live you may have further rights under the GDPR, the Australian Privacy Act or comparable law; we apply the same process to everyone regardless of which one applies.
Contact
Write to privacy@lingvo.dev for anything on this page, including access, correction and deletion requests. We answer from a person, not a ticket queue.
Last updated 10 August 2026. Material changes are announced by email to workspace owners before they take effect.