Privacy
We can’t read your text. That’s architecture, not a promise.
Most translation services work by receiving your words. Traxlate works by never needing them: with a language pack installed, translation happens on your own device and nothing is sent anywhere. This page explains exactly what we do hold, which is far less than you might expect.
Last updated 8 August 2026
The short version
- Your text, files, PDFs, video, audio and camera images are translated on your device. They are not uploaded, so there is nothing for us to store, read, sell or hand over.
- Your translation memory, glossary and history stay on your device unless you turn on sync — and sync stores encrypted data we cannot decrypt.
- We hold an account record — your email address, an optional name, and a password hash — because you asked us to keep your subscription.
- We never see your card. Payments go directly to our payment processors.
- Analytics are off unless you switch them on, and they cannot carry your text even then.
What never reaches us
On any setting, with any plan: your files, documents, PDFs, video, audio, camera images, translation memory, glossary and history are processed on the machine in front of you. They are never transmitted to Traxlate. This is not a policy we choose to follow — the software has no path that sends them.
With a language pack installed, the same is true of ordinary text translation: zero bytes of what you type leave the device. If you want the longer explanation of how that differs from apps that merely say “on-device”, we wrote it up here.
The two exceptions, and they are both your choice
- Human translation. If you order a translation from a professional linguist, the text you submit is by definition sent to us and to that linguist. The page says so before you place the order.
- Language pack downloads. Downloading a pack is a normal file download, so our servers see that a download happened. The pack contains no personal data and the download reveals nothing about what you translate.
What we actually store
| Data | Why | How long |
|---|---|---|
| Email address | To identify your account and contact you about it | Until you delete the account |
| Name (optional) | Only if you choose to give one | Until you delete it or the account |
| Password hash | To sign you in. Stored as a scrypt hash — we cannot recover your password from it | Until you delete the account |
| Session records | To keep you signed in and let you sign other devices out. Includes the browser/device description your browser sends | 30 days, or until you sign that session out |
| Subscription and payment records | To know what you bought, and because tax law requires it | As required by law |
| Licensed device identifiers | To enforce one subscription per device, which is what you paid for | Until the device is deactivated |
| Sync data (only if you enable sync) | To move your memory, glossary and history between your devices | Until you turn sync off or delete the account |
We do not store your IP address against your account, and we do not build a profile of you.
Sync, in detail
Sync exists so your glossary and translation memory follow you between your own machines. It is end-to-end encrypted: your device encrypts the data before sending it, and the key never leaves your device. What our server holds is ciphertext plus the bare mechanics of storing it — which account it belongs to, which dataset (memory, glossary or history), how large the blob is, a version number, and timestamps.
We cannot read it. This has a visible consequence we would rather state than hide: because the server cannot understand your data, it cannot merge conflicting edits for you.
Analytics
Product analytics are off by default. If you turn them on, what we receive is deliberately incapable of carrying your content: every value is either a fixed option from a short list, a size bucket rather than an exact number, or a clamped duration. Sizes are bucketed on purpose — an exact character count is itself a fingerprint.
No advertising cookies. No third-party trackers. No cross-site identifiers.
Who else is involved
- Payment processors. Card payments are handled by Stripe and crypto payments by NOWPayments. They receive what they need to take the payment; we never receive or store your card number.
- Professional linguists. Only for human-translation orders you place, and only the text in that order.
- Hosting. Our servers run on infrastructure we rent, which is why the account and billing records above exist at all.
We do not sell your data. There is no advertising business here to sell it to.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it and close your account. Because almost everything Traxlate touches stays on your device, a deletion request is usually a very short list: your account record, your session records, and your encrypted sync blobs. Payment records we must keep for tax purposes.
If you are in the EU or UK, the GDPR gives you these rights explicitly, including the right to complain to your data-protection authority.
Children
Traxlate is not intended for children under 13, and we do not knowingly create accounts for them.
Changes to this policy
If we change what we collect, we will change this page and update the date at the top. We will not quietly start collecting something new and leave this page as it was.
Contact
For anything on this page — a copy of your data, a correction, or deletion — email aradsoft.ca@gmail.com.
Because almost nothing you translate reaches us, most requests are answered in full by deleting your account, which removes the record described above.
Who we are
Traxlate is a product of AradSoft CA, Ontario, Canada. This policy is governed by the laws of the Province of Ontario and the federal laws of Canada applicable therein.