Skip to content
Menu
Workspace

Privacy Policy

Effective · September 16, 2026

We use your information to run your account, translate your content, and deliver the features you choose. This page explains what we collect and how to contact us about it.

01Who this policy covers

This policy covers translocale.io and the TransLocale dashboard, API, CLI, MCP server, and hosted translation services. The operator and contact details appear at the end of this page.

For account, billing, and service administration, we decide how your information is used. When a team supplies content for translation, we process it to provide that team's requested service. Your workspace administrator also controls membership and access to shared content.

02Information we collect

  • Account details: your name, email address, profile image, sign-in provider identifier, verification status, authentication records, and the policy versions and time recorded when you agree during signup. Social sign-in may supply access, refresh, and identity tokens, which are stored on the server.
  • Email preferences: your chosen topics, consent version and time, subscription changes, and email delivery and suppression records.
  • Setup preferences: your app platform, preferred workflow, expected translation volume, and plan selection, when you provide them.
  • Workspace content: source text, translations, file and message names, languages, product context, glossaries, comments, review history, release versions, and information about who made changes.
  • Usage and billing: translation counts, job status, plan and subscription details, payment status, and Stripe customer and transaction identifiers. Payment-card details are submitted directly to Stripe; TransLocale does not store full card numbers or security codes.
  • Technical records: IP addresses, browser or device information, request and error logs, session records, credential activity, and security events used to operate and protect the service.
  • Support messages: the information you send when you contact us.

03How we use information

We use this information to authenticate users, manage team access, process files and translations, deliver releases, calculate usage, collect payments, answer support requests, and investigate abuse or service failures. We also use it to meet legal obligations and resolve disputes.

We do not sell personal information or use your translation content for advertising. We do not use Google account data or your translation content to train general-purpose AI models.

04Optional email updates

If you subscribe to email updates, we use your email address, subscription choices, and relevant workspace activity to send the setup guidance, plan information, or product updates you choose. Workspace milestones, such as importing a catalog or reviewing wording, help us choose relevant messages.

Subscribing is optional. You can change your choices in Email preferences or unsubscribe using the link in a marketing email. Essential account emails continue. We record consent and delivery events and retain a hash of your email address in our suppression records to respect unsubscribe requests, including after account deletion.

05Optional website analytics

If you allow analytics through Privacy choices, we use Google Analytics to measure visits to our public pages, successful file checks, and clicks to open the workspace or signup page. The Google tag receives the public page address without query strings or fragments, the referring site's origin, cookie identifiers, and browser and device information. Google also receives network information when your browser connects to its service.

We do not send translation contents, filenames, form values, email addresses, account identifiers, or private workspace page addresses to Google Analytics. Advertising storage, advertising personalization, and Google signals are disabled in this integration. A click toward signup is not treated as a completed account creation.

Analytics stays off until you allow it. You can change your choice using Privacy choices on any public page. We respect Do Not Track and Global Privacy Control. Declining or withdrawing consent stops this integration's collection and removes its first-party Google Analytics cookies; it does not delete data already received by Google. Your choice is stored in your browser for up to six months.

06Google and GitHub sign-in

Google sign-in provides basic identity information: your name, email address, profile image, and account identifier. We use it to create or authenticate your TransLocale account and maintain its security. We do not request access to Gmail, Google Drive, or your contacts. GitHub sign-in similarly provides profile and email information; it does not grant TransLocale access to your repositories.

TransLocale's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We do not use Google user data for advertising or AI model training. Access by people is limited to what is needed for authorized support, security, legal obligations, or other uses permitted by that policy.

You can revoke TransLocale's Google access in your Google Account settings. Revoking provider access does not by itself delete your TransLocale account or stored workspace content; contact us to request deletion.

07Translation and connected AI tools

When you request AI translation, the relevant text, language choices, glossary, and product context are processed by Cloudflare Workers AI. The resulting translations and job records are stored so you can review and export them. Cloudflare states that it does not use Workers AI customer content to train its models without explicit consent.

The public file checker sends submitted content to our server for analysis; it does not start an AI translation job. Imported catalogs, saved projects, and translation jobs are stored separately as part of your workspace.

If you connect an AI assistant or another client through MCP, CLI, or API credentials, that client can receive the data allowed by its permissions. The assistant provider's own privacy terms apply to data it receives. Review those terms and the access you grant. Publishing a delivery release makes its translation content available to apps with the corresponding delivery credential; do not publish secrets in app strings.

08Who receives information

We use the providers below to operate TransLocale. They receive the information needed for their role. Authorized workspace members can access shared content according to their role. People providing support may access relevant records when needed to resolve your request or protect the service.

We may disclose information when required by law, to protect people or the service, or as part of a business transfer subject to appropriate confidentiality and privacy protections. We will give notice when required.

  • Cloudflare: website delivery, application hosting, database and file storage, security, logs, and AI translation processing.
  • Stripe: subscription payments, checkout, billing management, and fraud prevention.
  • Resend: sign-in and subscribed marketing email delivery, including the recipient address, email content, and delivery records.
  • Google or GitHub: authentication when you choose that provider.

09Cookies, storage, and security

We use cookies for authentication and security. The editor also uses browser session storage to recover unsaved drafts within a tab. You can clear these through your browser settings, but doing so may sign you out or remove unsaved work.

We use HTTPS, access controls, and scoped credentials to protect information. No service can guarantee complete security. Keep authoring credentials private and revoke access you no longer need.

Our providers operate internationally, so information may be processed outside your country, including in the United States, and may be subject to local laws. TransLocale does not currently promise storage in a particular country.

10Retention and your choices

We keep account and workspace information while it is needed to provide the service. History and release records support collaboration and recovery. Security, billing, backup, and legal records may need to be retained longer for their specific purpose. We delete or de-identify information when it is no longer needed, subject to legal requirements.

You can export supported translation files and revoke connected-tool credentials. Contact us to request access to, correction of, or deletion of your personal information, or to close your account. We may verify your identity. Some records may need to be retained for legal obligations, security, or disputes; we will explain any applicable limits.

For content in a team workspace, contact its administrator as well. Copies already exported to apps, repositories, or third-party assistants are outside TransLocale's control. You may also raise a concern with the privacy regulator that applies where you live.

11Children and policy changes

TransLocale is intended for adults using a software localization service. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action.

We will update the date on this page when this policy changes. For material changes, we will provide an appropriate notice and request consent where required before using information for a new purpose.