"AI-Powered Professional Document Translation Tool"
Doclingo is an AI tool for translating PDF, Office, and scanned documents, with a focus on preserving layout, OCR, bilingual output, and post-editing.
Supported formats include PDF, Word, PPT, Excel, images, and others; there are also features such as a glossary, online editing, document chat, highlight-to-translate, and API integration.
Doclingo
AI-Powered Professional Document Translation Tool
Location: USA ⓘ Place of founding: Pittsburgh, Pennsylvania, USA.
Premium+ Extended premium tier with higher limits/additional benefits compared to Premium; the page mentions Premium+ and additional booster/discount benefits, but some limit values are publicly displayed as “undefined.” Other Booster Package / Character Pack as a one-time, non-auto-renewing model; according to the Help Center, usable with the same premium benefits and no time limit. For API usage, character-based quotas apply; if the quota is exhausted, you can buy Booster Packages or upgrade to higher memberships. For larger volumes, a Bulk Purchase / Discount Quote is offered via Sales contact. According to the official help, payments are processed via PayPal and Stripe; invoices are issued through Stripe.
Target audience
Doclingo is aimed primarily at people and teams that need to translate complete documents rather than just raw text: students, researchers, freelancers, export/operations teams, agencies, legal departments, support/back-office teams, as well as developers who want to integrate document translation into their own systems. Official sources specifically mention academic papers, contracts, reports, manuals, invoices, scanned PDFs, and technical materials as typical scenarios. With features such as Translation Styles, glossary, OCR, and API, Doclingo comes across more as a specialized document processing tool with an AI translation core than as a simple text translator.
Outstanding features
Doclingo stands out most through its combination of layout preservation, OCR, bilingual side-by-side display, and interactive post-editing. In addition, there are glossaries for terminology consistency, Document Conversation and Summaries/Mind Maps, Text Selection for targeted interaction with already translated PDFs, Regional Translation to exclude logos, stamps, formulas, or signatures, as well as AI Proofreading and Translation Styles for academic, legal, and business contexts. In the paid/pro segment, there is also a multi-engine approach, including engines related to GPT, Gemini, Claude, and DeepSeek; for developers, there is an API with batch/asynchronous logic.
Key use cases
Doclingo is particularly strong with academic papers, contracts, reports, invoices/forms, manuals, technical drawings/CAD screenshots, and documents in general where structure and layout must be preserved. For scans, the OCR function is central; for legal or audit-adjacent processes, the bilingual output is helpful. In practice, Doclingo is also suitable for cross-border commerce, internal knowledge extraction from foreign-language documents, translation of research materials, and workflow automation via API in ERP/CMS/OA/BPM environments.
Usage & notes
The standard workflow is: upload document, choose language/engine or style, wait for the translation, then if needed edit online, exclude areas, adjust terminology, chat with the document, or download a bilingual version. Important: according to the Help Center, scans/OCR are tied to VIP/paid logic; Text Selection only works with text-based PDFs, not scanned images. For data protection, it is relevant that Doclingo on the one hand speaks of encrypted storage, 24-hour deletion, and non-use for model training, while on the other hand there are inconsistent operator details and contradictory privacy signals for the app. For legally binding, medical, official, or particularly sensitive documents, an additional human review or legal check is therefore advisable.
| Target audience | Assessment |
|---|---|
| Private individuals | Suitable – for occasional PDF/Office translations, especially with layout preservation. |
| Students / research | Suitable – for academic work, papers, foreign-language documents, and bilingual outputs. |
| Self-employed / freelancers | Suitable – for contracts, reports, manuals, Office documents, and multilingual client communication. |
| SMEs | Conditionally suitable – functionally interesting, but data protection/DPA and server location details are not sufficiently transparent for EU companies. |
| Large enterprises / regulated industries | Rather not suitable without review – there is a public lack of robust evidence of GDPR compliance, DPA, and EU data residency. |
Hosting & Data
1) On-prem / local hosting
Meaning: The company operates the solution on its own hardware or within its own infrastructure. In the strictest sense, not only the application runs locally, but ideally the model as well.
2) Private cloud / data center
Meaning: The solution runs in a dedicated or more clearly separated cloud environment, often with a hosting provider or hyperscaler, but in a German data center or in a particularly controlled environment.
3) EU SaaS / managed
Meaning: The provider operates the solution itself as a service. The company uses the tool as a ready-made cloud service, ideally with EU data residency.
4) Hybrid
Meaning: One part of the processing remains internal / local / in a private cloud, while another part runs in an external cloud or EU SaaS.
5) AVV / DPA
Meaning: This is the data processing agreement or Data Processing Addendum. It governs that the provider processes personal data on behalf of the customer and is bound by the customer's instructions.
6) No training
Meaning: The provider does not use your prompts, uploads, attachments, chat histories, or outputs for training or improving the general model — ideally excluded by contract.
7) Open-source / transparency path
Meaning: There is a path toward greater technical transparency and sovereignty, for example through:
- open models
- documented components
- self-hostable parts
- traceable architecture
- export / switching options
| On-prem / local hosting | ❓ |
| Private cloud / data center | ❓ |
| EU SaaS / Managed | ❓ |
| Hybrid | ❓ |
| DPA / AVV | ❓ |
| No training on customer data | ⚠️ |
| Open source / transparency path | ❓ |
On-prem / local hosting: indirect / not available
Not specified on the website. No on-premises, local, or self-hosting option was found.
Private Cloud / Data Center: Unclear
Not specified on the website. No information was found regarding a dedicated private cloud, isolated customer environment, or specific EU/EEA data centers.
EU SaaS / Managed: Indirect / Not Available
Although there is a SaaS offering on the website, no EU/EEA data residency is specified. Instead, the privacy policy states that data is generally stored within China.
Hybrid: unclear
Not specified on the website. No hybrid deployment models were described.
SLA / DPA: Indirect / Not Available
An SLA/DPA is not listed on the website, and no corresponding subpage was found.
No training: partially
The privacy policy states that uploaded translation content is to be used solely for the translation function and is to be deleted or anonymized upon completion. However, the website does not specify an explicit contractual exclusion of use for general AI training or a separate opt-out option.
Open Source / Transparency: Indirect / Not Available
Not specified on the website. No open-source components, open models, or self-hostable parts have been documented.
Data Processing
The website describes a cloud-based translation service. The “Pros” section lists several external AI engines, including DeepSeek, ChatGPT, Gemini, and Claude. The privacy policy states that translated documents, texts, and images are processed solely for the purpose of providing the translation function and are subsequently deleted or anonymized whenever possible. At the same time, the privacy policy lists China as the primary storage location and mentions possible cross-border transfers when using international cloud services. The website does not specify a precise EU/EEA data residency, a complete list of subprocessors, or a Data Processing Agreement (DPA).
Conclusion
For users in the EU/EEA, the website’s documentation is currently insufficient to classify Doclingo as GDPR-compliant. The fact that the website states data is generally stored in China, as well as the absence of a Data Processing Agreement (DPA), EU data residency, and a transparent list of subprocessors, are significant negative factors. Consequently, based on the information available on the website itself, its use cannot be reliably documented as GDPR-compliant.
Sources
| On-prem / local hosting | ❓ |
| Private cloud / data center | ❓ |
| EU SaaS / Managed | ❓ |
| Hybrid | ❓ |
| DPA / AVV | ❓ |
| No training on customer data | ⚠️ |
| Open source / transparency path | ❓ |
On-prem / local hosting: indirect / not available
Not specified on the website. No on-premises, local, or self-hosting option was found.
Private Cloud / Data Center: Unclear
Not specified on the website. No information was found regarding a dedicated private cloud, isolated customer environment, or specific EU/EEA data centers.
EU SaaS / Managed: Indirect / Not Available
Although there is a SaaS offering on the website, no EU/EEA data residency is specified. Instead, the privacy policy states that data is generally stored within China.
Hybrid: unclear
Not specified on the website. No hybrid deployment models were described.
SLA / DPA: Indirect / Not Available
An SLA/DPA is not listed on the website, and no corresponding subpage was found.
No training: partially
The privacy policy states that uploaded translation content is to be used solely for the translation function and is to be deleted or anonymized upon completion. However, the website does not specify an explicit contractual exclusion of use for general AI training or a separate opt-out option.
Open Source / Transparency: Indirect / Not Available
Not specified on the website. No open-source components, open models, or self-hostable parts have been documented.
Data Processing
The website describes a cloud-based translation service. The “Pros” section lists several external AI engines, including DeepSeek, ChatGPT, Gemini, and Claude. The privacy policy states that translated documents, texts, and images are processed solely for the purpose of providing the translation function and are subsequently deleted or anonymized whenever possible. At the same time, the privacy policy lists China as the primary storage location and mentions possible cross-border transfers when using international cloud services. The website does not specify a precise EU/EEA data residency, a complete list of subprocessors, or a Data Processing Agreement (DPA).
Conclusion
For users in the EU/EEA, the website’s documentation is currently insufficient to classify Doclingo as GDPR-compliant. The fact that the website states data is generally stored in China, as well as the absence of a Data Processing Agreement (DPA), EU data residency, and a transparent list of subprocessors, are significant negative factors. Consequently, based on the information available on the website itself, its use cannot be reliably documented as GDPR-compliant.
Sources
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| – Very strong focus on preserving formatting/layout in documents. | – Official company and country information is inconsistent: the website privacy policy names a Chinese operating company, while Apple/Google list TONDA in Japan. |
| – OCR for scans/image content. | – Price transparency is weak: the official pricing page is only partially readable in the accessible web view. |
| – Bilingual output for review workflows. | – For highly sensitive/GDPR-critical data, the reviewed official sources lack reliable information on server location, SCCs, and AVV/DPA. |
| – Glossary/terminology database for consistency. | – Google Play states in the app data privacy section, among other things, “Data isn’t encrypted,” which contradicts the website’s statements about TLS/SSL. |
| – Online editing, section exclusions, and post-correction. | – For legally/officially relevant documents, Doclingo itself recommends a human review; the refund policy also still refers to beta testing. |
| – Multi-engine approach and API for workflows/automation. |
Reviews
0 reviews in total
There are no confirmed reviews for this tool yet.
Submit review
Your review will only become visible after email confirmation. This protects the portal against abuse.
Report review
Please select the reason why this review should be checked.
GDPR-compliant usage possible?
The documentation available on the website does not demonstrate GDPR-compliant use for the EU/EEA region. On a positive note, according to the privacy policy, uploaded translation content is to be used solely for the translation function and, once the process is complete, should be deleted or anonymized whenever possible. However, several factors indicate that the service is not robustly compliant with the GDPR: According to the website, data is generally stored in China; EU/EEA data residency is not specified; a Data Processing Agreement (DPA) is not listed on the website; subprocessors are not transparently documented in a complete list; and the governing law and jurisdiction in the privacy policy refer to the People’s Republic of China.
Positive
A privacy policy is available on the website. It states that translation content is processed solely for the purpose of providing the translation feature and should be deleted or anonymized as soon as possible after the translation is complete. Additionally, the website lists SOC II compliance as a positive aspect.
Negative
The website does not mention EU/EEA hosting. Instead, it states that personal data is generally stored within the People’s Republic of China. A Data Processing Agreement (DPA) is not provided on the website. A complete list of subprocessors is not provided on the website. EU data residency, on-premises hosting, self-hosting, and an explicit opt-out from AI training are not mentioned on the website. The privacy policy is governed by the laws of the People’s Republic of China and designates Wuhan as the competent jurisdiction.
Server Location
According to the privacy policy, personal data is generally stored within the People’s Republic of China. If cross-border transfers occur—for example, in the case of international cloud services—the provider states that it will implement protective measures. No specific server or data center location in the EU/EEA is listed on the website.