Security
Tenant isolation. Projects, reviewers, reviews, and billing rows are scoped to a tenant. Customer admins only see their organization. Platform staff see operational metrics; string contents require an explicit, time-boxed support session with audit.
Authentication. Customer and platform sign-in use Clerk (MFA, Google, and Enterprise SAML/SSO where entitled). Sessions use httpOnly cookies. Production disables local password dual-read. Extension access uses a minted API JWT after password or Clerk auth — not long-lived invite tokens for new invites.
SSO & SCIM. Enterprise customers can enforce SAML SSO per organization and sync membership via Clerk Directory Sync. Offboarding removes org membership; audit actor rows are retained.
Audit. Security-sensitive actions write an append-only tenant audit log (people, money, publish, SSO, support sessions). Payloads never include translation string bodies or secrets.
Encryption & residency. Data in transit uses TLS. Each organization chooses a datacenter at signup — United States (N. Virginia), European Union (Frankfurt), or Asia Pacific (Singapore). That choice is stored on the workspace and on the Clerk organization. Physical multi-region isolation is an Enterprise Plus add-on.
Payments. Card and Connect payouts run through Stripe. LTrans stores Stripe customer and Connect account ids — not raw card numbers.
Published locales. Sandbox/live CDN files are publish-gated snapshots. Public by default for typical UI copy; private/tokenized delivery is available for enterprise needs.
Subprocessors · DPA · Privacy