Loading
Security & Privacy
Translators handle confidential documents. Here is exactly how Transsist Translator treats them — and what it does send, and why.
Stored in a local database on your PC. Never sent to us — our servers have nowhere to put it.
At activation, then roughly once or twice a day while you use the app online, to api.transsist.com over HTTPS:
Not your computer’s name, not hardware identifiers, not your files. Like any server, ours sees the connection’s IP address; we remove it from our licence records after 90 days.
How it is built
We keep only a one-way hash of your key, so our database cannot reveal it. Paid keys are emailed when issued; trial keys are shown once on screen.
Activation creates a key pair on your computer, protected by Windows. Licence approvals are signed, so they cannot be forged or copied to another machine.
Between check-ins the app works without a connection for 14 days (30 on Perpetual) — so an outage on our side does not stop your work.
Mail passwords, sign-in tokens and WhatsApp tokens you add are encrypted with Windows’ own data protection, separately from the database.
Require a passcode to open Transsist, and lock it when you step away.
Paddle, our Merchant of Record, takes your card details inside its own secure checkout. We receive a reference and the outcome — never card numbers.
Good to know
If you believe you have found a vulnerability, email support@transsist.com with “Security” in the subject and the details to reproduce it. Please give us reasonable time to fix it before disclosing it. The full detail of what we collect is in the Privacy Policy.