What we receive, and what we never do

What never leaves your computer

None of the following is ever transmitted to us, during licensing, account operations, or anything else the application does on its own:

• Document contents, of source files or translations
• Filenames
• Folder paths
• Job names and job counts
• Client names, client codes and client rates
• Invoice numbers, line items, amounts, currencies and payments
• Word counts, page counts and character counts
• Reports and exports
• Email content, email addresses you have imported from, or WhatsApp messages
• The mail, OAuth and WhatsApp credentials you configure inside the application

All of it lives in a local database on your machine, with credentials held in separate files encrypted through Windows’ own credential protection.

What we do receive

Only what is needed to run an account and a licence:

• Account — your email address, and a name if you give one.
• Sign-in — handled by Clerk, our authentication provider. Your password is set with them and we never see it; we hold no password, no session token and no reset token at all.
• Licence — which plan you hold, its status and dates, and a hash of your licence key.
• Installation identity — a public key generated on your machine, its fingerprint, the operating system, the Transsist version, a name for the device, and a one-way digest used only to recognise a reinstall on the same hardware.
• Payments — if and when billing is enabled, reference identifiers from our payment provider. We do not receive or store card details.
• Security events — failed sign-ins, denied access attempts and similar, so abuse can be investigated.

The device name is the one field to be careful with

It defaults to your computer’s hostname and exists so you can tell your laptop from your desktop in the device list. You can rename it to anything. It is the only field in the whole system where you could put something private if you chose to, so we mention it rather than leaving you to notice.

How the privacy is enforced, not just promised

A promise is not a control. These are the actual mechanisms, and they are the reason the list above can be stated so flatly:

• Our database has nowhere to put your work. There is no column for a document, a path, a client or an amount, so adding one would be a visible change to the schema.
• Every request the application sends is validated against a closed schema, so an unexpected field is rejected rather than quietly stored.
• Our logs redact anything shaped like a path, a filename, a client name, an invoice figure or a secret — automatically, at every level of nesting.
• We do not store credentials at all, so a breach of our database would contain nothing anybody could sign in with.

What the application connects to

Transsist connects to our licensing server, and to nothing else of ours. There is no telemetry, no analytics and no crash reporting.

It also connects to services you configure with your credentials — your mail provider over IMAP or SMTP, Google or Microsoft if you use OAuth sign-in for mail, and the WhatsApp Cloud API if you enable it. Those connections go directly from your machine to those providers. They do not pass through us and we cannot see them.

This website

Session cookies are set by Clerk, and only after you sign in. There are no advertising cookies, no tracking pixels and no third-party analytics, and the fonts are served from our own domain rather than fetched from anyone else.

Who else is involved

Two companies process something on our behalf, and it is only fair to name them:

• Clerk handles sign-in. They hold your email address and your password. We never see the password.
• Resend delivers our email. They see the address we are writing to and what the message says.

Neither is ever given a document, a filename, a client name or an invoice figure — because, as above, we do not hold those either.

Keeping and deleting

Account and licence records are kept while your account exists, because a licence that cannot be looked up cannot be supported. Security events are kept so abuse can be investigated. Spent download links are cleared automatically.

To have your account deleted, ask us. We delete it here and with our sign-in provider. Deleting revokes your licences, which stops your installations from revalidating — but it does not touch anything on your machine. Your database, your invoices and your documents are yours, and we could not reach them if we wanted to.

If this ever changes

Any future feature that would send more than the above — a cloud backup, a shared glossary, anything — would be opt-in, explained before you turned it on, and announced. It would not arrive quietly in an update.

Questions

Ask us through support, or write to support@transsist.com. If you think something on this page is inaccurate, we would genuinely like to know.