LEGAL

Privacy Policy

Last updated: 23 October 2026
This policy explains what personal data OnlineDocTranslator handles, why, who else processes it, how long we keep it, and the rights you have.

1. Who we are

OnlineDocTranslator (www.onlinedoctranslator.ai) is run by Lumax Digital LTD, a company registered in England and Wales under company number 17305780, registered office 128 City Road, London EC1V 2NX, United Kingdom ("we", "us").

We handle personal data under the UK General Data Protection Regulation (UK GDPR) and the UK Data Protection Act 2018 and, for users in the European Union, the EU General Data Protection Regulation (EU GDPR). In this policy, "GDPR" means whichever of the two applies to you.

For any privacy question or request, write to info@lumaxdigital.co.uk.

2. Our role: controller or processor

  • Account, team and billing data. We decide how this data is used, so we are the controller.
  • Documents you upload and everything made from them (text, translations, memory, glossary, templates, certification files). You, or the client you work for, decide why these are processed, so you are the controller and we are your processor. We process them only to provide the service to you, under our data processing agreement (DPA), which you can save as a PDF.

If you are a translator's client and your personal data is in a document they uploaded, please contact that translator or agency first: they decide how your document is handled. We will help them answer you.

3. What data we handle

Account and team

  • Email address, full name, and your password, which we store only as a one-way (bcrypt) hash.
  • Your team, your role in it, and invitations you send or receive (the invitee's email and role).
  • The logos, stamps and signatures your team uploads to Media.
  • The date and time you accepted the Terms of Service.

Your content

  • The documents you upload (PDF, images, DOCX) and the text read from them.
  • Translations, edits and saved versions, comments, and instructions you give the AI.
  • Translation memory, glossary and learned terms, and document templates built from finished documents.
  • Certification files and templates you upload, stored with a SHA-256 fingerprint.
  • Delivery links you create for clients, with their expiry date and download count.
  • For protected delivery links (paid before download): the amount, when the client said they had paid, when the link was paid or unlocked, and the download count. We also store your team's PayPal.me name. We don't collect your clients' names. If a client chooses to give their email address when they say they have paid, we use it once to tell them the document is ready, then delete it; it isn't shown to you or your team. A client who pays on PayPal, or by bank transfer or another method outside the service, pays you directly, so we never receive or store their payment details. If the client tells us they have paid, we record when and email you.
  • When a client pays a protected link through Stripe, Stripe collects the payment details on the translator's own Stripe account, as the translator's payment provider. We only receive the payment status, the amount and the payment reference, and we store your team's Stripe account ID. We never receive card or bank details.

These documents often contain personal data about third parties, sometimes of a sensitive kind (for example identity documents, civil status records or medical reports).

Usage and billing

  • AI usage records: which action ran, which model, how many tokens it used and what it cost. We use these to meter credits and to price the service.
  • Your plan, subscription status, credit balance and credit history.
  • Payment data is handled by Stripe. We never see or store your card number. We receive your Stripe customer and subscription identifiers and the status of your payments. At checkout Stripe also collects your billing address, which appears on your invoices.

Technical data

  • Server logs kept by our hosting providers (such as IP address, time and requested address), used to run and protect the service.
  • Small items stored in your browser to keep you signed in. See the Cookie Policy. We do not use analytics or advertising trackers.

4. Why we use it, and on what legal basis

PurposeLegal basis (GDPR)
Create and run your account and team; translate, edit, store and deliver your documentsPerformance of a contract, Art. 6(1)(b)
Process payments, issue invoices, keep accounting recordsContract, Art. 6(1)(b); legal obligation, Art. 6(1)(c)
Send service emails, such as team invitationsPerformance of a contract, Art. 6(1)(b)
Tell a client who left their email address that their document is readyConsent, Art. 6(1)(a)
Keep the service secure, prevent abuse, fix errors, measure AI costsLegitimate interest, Art. 6(1)(f)
Answer requests and defend legal claimsLegitimate interest, Art. 6(1)(f); legal obligation, Art. 6(1)(c)

For your content we act on your instructions as processor; the legal basis for processing it, including any special categories of data, is yours as controller.

We don't send marketing emails, we don't sell personal data, and we don't make decisions about you based solely on automated processing that have legal or similarly significant effects.

5. How AI processing works

To translate a document, read scanned pages, rebuild the layout and answer requests in the editor, the relevant text and page images are sent to our AI provider, Anthropic, through its commercial API. If you or a team member choose GPT-4.1 (OpenAI) when creating a project, the document's text is also sent to OpenAI, through its commercial API, to write the translation. Anthropic still reads scanned pages and rebuilds the layout for that project, so it receives the document as well. The editor assistant always uses Anthropic.

  • No training. Under the providers' commercial API terms, data sent through the API is not used to train their models. We don't train models on your documents either.
  • The providers may keep requests for a limited time under their own terms, for example to detect abuse.
  • Corrections you make are reused only inside your own team (translation memory, glossary, templates). They are never shared with other customers.

Questions you ask in the in-app Help chat are sent to Anthropic to generate the answers. We don't store the questions or the answers; we keep only the number of messages and the tokens used.

6. Who processes data for us

We use these sub-processors. Each is bound by a data processing agreement. The same list is on our Security page and in our DPA.

ProviderWhat it doesLocation
AnthropicAI processing: translation, reading scans, layout rebuild, editor assistant and the Help chatUnited States
OpenAIAI translation, only for projects where GPT-4.1 (OpenAI) is chosenUnited States
SupabaseDatabase and file storage for your account and documentsEU (Ireland)
RailwayAPI hosting: the servers that run the application and process your documentsEU or US region, as configured
VercelHosting of the website and web appGlobal edge network
StripePayment processing for our own plans and credit packs: payments, subscriptions and invoicesEU and United States
ResendSending service emails, such as team invitations, password resets and ready noticesUnited States

Stripe also acts as an independent controller for some purposes, such as fraud prevention and its own legal obligations; see Stripe's privacy policy. We will update this list before adding a new sub-processor.

7. International transfers

Your documents and account data are stored in the EU (Ireland). We run the service from the United Kingdom, which the European Commission recognises as giving adequate protection to personal data. Some providers above are based in, or process data in, the United States. Where data leaves the UK or the European Economic Area, we rely on safeguards such as the European Commission's Standard Contractual Clauses with the UK Addendum, or the EU-US Data Privacy Framework and its UK Extension, where the provider is certified. You can ask us for more information about these safeguards.

8. How long we keep data

  • Projects (the uploaded document, its text, translations and exported files, saved versions, page images, certified copies, delivery files and comments) are deleted automatically 90 days after the translation is completed, or 90 days after upload if it never completes. Running a translation again starts the 90 days again. Projects that existed when automatic deletion began get the full 90 days from that date. The date shows on the project, and we send a notice in the app 7 days before. You can delete a project sooner yourself; doing so also deletes its translation memory entries.
  • Translation memory, glossary, learned terms and templates are not deleted with the project when it expires. They are your team's working assets and stay in its library until you delete them or the account. Memory entries and templates contain text from your documents.
  • Delivery links expire after 1, 7 or 30 days, as you choose, or when you revoke them. The file behind a link is deleted when you revoke it, or 7 days after it expires. A protected link's watermarked preview images are deleted when you unlock or revoke it, or with the file. A client's email address, if they gave one, is deleted as soon as we have emailed them that the document is ready, or when the link is revoked, expires or is deleted, whichever comes first.
  • Uploaded files waiting to become templates are discarded after 24 hours if you don't save them.
  • Your account stays until you delete it from Settings. If you own a team, deleting your account also deletes the team with its projects, memory, glossary, templates, certification files and credit history, and the stored files behind them. If you are a team member, only your own account is removed; the team's work stays with its owner.
  • AI usage records are kept for cost accounting. When the related account or project is deleted, the link to it is removed.
  • Invoices and accounting records are kept for as long as company and tax law requires (in the UK, generally 6 years from the end of the financial year).
  • Deleted data can remain in our providers' backups for a limited period before it is overwritten.

9. Security

All connections use HTTPS, stored files are encrypted at rest, and passwords are stored only as hashes. Projects are visible only to your team, and roles control what each member can do. Delivery links use long random tokens. We look them up by a one-way hash and keep the token itself only encrypted, so your team can copy a link again. Our Security page describes these measures in more detail.

10. Your rights

Under the GDPR you can ask us to:

  • give you access to your personal data and a copy of it;
  • correct data that is wrong or incomplete;
  • delete your data;
  • restrict how we use it;
  • give you your data in a portable format;
  • stop using it where we rely on legitimate interest (objection).

You can change your name in Settings and delete projects or your whole account at any time. For anything else, write to info@lumaxdigital.co.uk. We answer within one month. We may ask you to confirm your identity first.

Where we are a processor (your documents), requests from the people named in them should go to the customer who uploaded them; we will help that customer respond.

You also have the right to lodge a complaint with a supervisory authority. In the UK this is the Information Commissioner's Office (ICO). If you live in the EU, you can complain to the data protection authority of your country of residence.

11. Children

OnlineDocTranslator is a professional tool. It is not meant for anyone under 18.

12. Changes to this policy

If we change this policy in a way that matters, we will tell you by email or in the app before the change takes effect. The date at the top shows the latest version.

13. Contact

Lumax Digital LTD, 128 City Road, London EC1V 2NX, United Kingdom. Email for privacy requests: info@lumaxdigital.co.uk.