Skip to content
transglot.securityStart free
/securitythe controls, one by one

scoped.

How Transglot is secured.

every database query is scoped to your organization and project

Encryption, access control, tenant isolation and the audit trail, each one naming the mechanism that enforces it. The things we have not built are written down here as gaps.

  • tls 1.2 or better in transit
  • hmac-signed webhooks
  • append-only audit rows
  • four roles, five token abilities
the controls

Encryption, access, isolation and audit.

every tile names the mechanism that makes it true, and the tile that names a gap is the most useful one on the page
AES-256

Encrypted before it leaves the host

Database backups are encrypted on the way out. The file backup repository is password-encrypted and refuses to run without its key. Connected-app credentials and webhook secrets are stored as encrypted columns. Deploy tokens are stored as a SHA-256 hash and shown once, at creation. The live disks are not encrypted at the volume level, because we have not built that, and you should learn it here rather than in diligence.

Signed on the way out

Outbound webhooks are signed with HMAC-SHA256 over the timestamp and the body. The timestamp is sent too, so you can enforce your own replay window.

POST /hooks/translations
X-Transglot-Timestamp: 1756...
X-Transglot-Signature: hmac-sha256
signed over (timestamp, body)
compared with hash_equals

Identity and access

Four roles on every plan, Free included: owner, admin, developer and translator. Per-project and per-language grants sit on top, so a freelancer can be given one language and see nothing else. SAML 2.0 sign-in with just-in-time provisioning and SCIM 2.0 provisioning ship on Enterprise, and password login can be switched off for the whole organization.

Tenant isolation

Every query is scoped to your organization and project. An id belonging to somebody else answers 404 rather than 403, so the existence of another workspace never leaks. The shared exact-match memory pool is the one deliberate exception, and any project can leave it with a switch.

The audit trail

Role changes, token creation, billing changes, SSO configuration and SSO sign-ins are recorded, and the rows cannot be edited or deleted: the model throws on both. Password sign-ins are not in the trail today. Owners and admins on Enterprise export the whole trail as CSV. There is no hash chain and no cryptographic signature, so nothing here says tamper-evident.

Uptime and credits

We publish no percentage here, because any figure we typed would be our word for our own availability. Business and Enterprise carry a contractual monthly uptime target with a service-credit schedule, and that schedule is the SLA.

Where compliance actually stands

The same four rows the trust page and the trust center read, from the same config. A stamp can only say "held" when a boolean says so, and today none of them does.

  • SOC 2 Type II: audit in progress
  • ISO/IEC 42001 (AI management): pursuing
  • GDPR: aligned, not certified
  • CCPA / CPRA: aligned, not certified
the short answers

What a reviewer asks, answered first.

The questions a security review opens with, and the answers, in the order they usually arrive. Every line is a control in the codebase rather than a claim about one. The last line is a gap, and it stays here until it stops being true.

  • no findings quoted, because there is no third-party report yet
  • no certification implied: the compliance table on /trust reads from config
  • good-faith research is never met with lawyers
Mail security@transglot.aiThe trust center
illustrative output. this page runs no scan, of you or of us
posture notes, illustrative
~ % transglot security --explain
tls 1.2 or better, refused below at the edge
webhooks hmac-sha256 over timestamp and body
tokens stored as a sha-256 hash, shown once
tenancy every query scoped by org and project
abilities five on a project token, three on deploy
roles four, on every plan including free
audit append-only at the model layer, no chain
memory one shared exact-match pool, off per project
at rest live volumes are not disk-encrypted. backups are aes-256.

FAQs

The list a security review usually arrives with.

Is my data encrypted?
In transit, yes: TLS 1.2 or better, and anything older is refused at the edge. At rest, database backups are encrypted with AES-256 on the way out and the file backup repository is password-encrypted. The live database volumes are not disk-encrypted today.
Not yet. A SOC 2 Type II audit is in progress: readiness first, then the observation window. We hold no third-party security certification today, and the chips above are drawn from a config boolean that cannot say "held" until one is.
No, on any plan. Your strings go to the providers named in the trust center to be translated and for nothing else, under commercial terms. Metering records token counts, never the text.
Every query is scoped to your organization and project, and an id that is not yours answers 404 rather than 403, so the existence of another workspace never leaks. The shared exact-match translation memory pool is the one deliberate exception, it carries no owner at all, and any project can leave it with one switch.
Yes, on Enterprise: SAML 2.0 with just-in-time provisioning, SCIM 2.0 provisioning, and the option to switch password login off for the whole organization. Four roles plus per-project and per-language grants are on every plan, Free included.
Role changes, token creation, billing changes, SSO configuration and SSO sign-ins are all recorded, and the rows cannot be edited or deleted. Password sign-ins are not in the trail today. Owners and admins on Enterprise export the whole trail as CSV. There is no hash chain and no signature, so we do not call it tamper-evident.
We have no third-party report to quote. When one exists it will be named here with its date and scope rather than summarised as a number of findings.
Mail security@transglot.ai. Good-faith research under the published policy carries a written safe harbour, an acknowledgement within three business days and an initial assessment within ten business days. There is no paid bounty today.
A project token is stored as a SHA-256 hash and shown once, at creation. Project tokens carry five abilities and deploy tokens three, so a token handed to CI can be narrower than the person who made it. Tokens are a paid-plan feature: Free cannot mint one.
still have questions?

Send us your security questionnaire.

Read the trust centerMail security@transglot.ai
good-faith research is safe · no certificate claimed · no uptime figure published
Works with the tools you already run
All 41 integrations