Your source strings are sensitive. We treat them that way.
Every string Tonguesage touches is encrypted in transit and at rest. Tenant isolation is structural, not policy. Here's how it works.
What we store, how we store it
String storage
Tonguesage stores string keys, source values, and translation values to power the sync engine and translation memory. We do not store your full codebase: only the string content extracted from locale files.
Encryption
All data is encrypted at rest using AES-256. All data in transit uses TLS 1.2 or higher. Webhook payloads are signed with HMAC-SHA256 so you can verify they came from Tonguesage.
Tenant isolation
Each Tonguesage account has its own isolated string tables. There is no shared string store between tenants. A query from one account cannot access another account's data by design.
Data retention
Translation memory and string history are retained for your account's active lifecycle. On account deletion, all string data is purged within 30 days. You can request earlier purge at any time.
How access to your repos and strings is controlled
OAuth-scoped repo access
Tonguesage requests only the minimum GitHub / GitLab / Bitbucket scopes needed to read locale files and write translated files back. We never request broad write access to your full codebase. You can revoke access at any time from your source control provider's OAuth settings.
Role-based access (Scale plan)
The Scale plan supports admin, reviewer, and translator roles. Translators can approve translations; reviewers can approve and merge; admins can manage integrations, team members, and billing. Roles are enforced at the API level, not just the UI.
Token rotation and audit log
API tokens can be rotated from your account dashboard. Every write action taken by a token (string approval, locale merge, webhook receipt) is logged with a timestamp to the account audit trail.
Designed with compliance in mind
Tonguesage was designed from the start with SOC 2 control objectives in mind: access control, availability, processing integrity, confidentiality, and privacy. We are working toward formal third-party SOC 2 Type II attestation as the product matures.
We are GDPR-aware: EU user data is processed in accordance with GDPR requirements. Our data processing agreement (DPA) is available on request for teams that need it for vendor onboarding.
For teams with specific security review requirements, we can provide our security questionnaire responses, architecture overview, and sub-processor list. Contact us at [email protected].
Have specific security requirements?
We're happy to work through a security review, provide our questionnaire, or answer specific questions about our data handling.