Privacy

Last updated 2 August 2026

The short version

We do not store the documents you translate. The text is held in memory only while the translation runs, then discarded. We keep a record that a translation happened — which language, how long the document was, when — but never what it said.

What we store

  • — Your email address and password (the password is hashed; we never see it)
  • — Your plan and how many translations you have used this month
  • — For each translation: the target language, the document length in characters, and the time
  • — If you contact us or join the waitlist: what you typed into that form

We do not store the document text, the translated output, the file, or the file name. There is no field in our database that could hold them.

Where your document goes

To translate a document we send its text to Anthropic, who provide the translation model. This is necessary for the service to work, and it means the text does leave our systems while the translation runs. Anthropic processes it to produce the translation and does not use it to train their models. We do not send your document anywhere else.

Who else is involved

  • Anthropic — performs the translation
  • Supabase — stores your account and usage records
  • Vercel — hosts the website
  • Mailgun — sends us a notification when you use the contact form

How long we keep things

Account and usage records are kept while your account exists. Because we never store document content, there is nothing sensitive in that history — it is counts and timestamps. Ask us to delete your account and we will remove it along with its usage records.

Your rights

Under the Digital Personal Data Protection Act, 2023, you can ask what we hold about you, ask us to correct it, or ask us to delete it. Email contact@globalreach-ai.com and we will respond.

If you handle sensitive documents

Whether it is patient records, customer orders or anything else you would rather not hand to a third party, the answer is the same: we do not store document content. Our database has no column capable of holding it, so this is not a policy we could quietly change — it would require rebuilding the system. We are happy to walk a compliance team through exactly how it works.

Questions? Get in touch.