Privacy is a core concern for translation users. This guide explains how MAITO handles your data with both translation engines.
Local AI: Complete Privacy
How It Works
- Offline by default: No internet connection used for translation
- On-device processing: Everything happens on your computer
- No data transmission: Your text never leaves your PC
- No logging: MAITO doesn’t collect or store your translations remotely
What Stays Private
✅ Source text you translate
✅ Translation results
✅ Documents you translate - Word, PDF and text files are processed on your own machine and never uploaded
✅ Translation history
✅ Language preferences
✅ Usage patterns
Perfect For
- Confidential business documents
- Medical/legal records
- Personal sensitive information
- Classified content
- GDPR-strict environments
- Any privacy-critical use case
Zero-Knowledge Translation
With Local AI, not even MAITO developers can see your translations. They exist only on your computer.
Offline Document Translation
Since the latest release, the local engine translates documents as well as text. A Word, PDF or text file dropped on the Documents tab is opened, translated and written back on your own machine. The translated copy lands next to the original.
While a document translates, MAITO writes its intermediate files to a working folder on your own disk:
%LOCALAPPDATA%\Pangaia Software\MAITO\DocumentTranslation\Each translation gets its own subfolder, which is deleted when the translation finishes. Anything left behind by a crash or a forced shutdown is swept away automatically after seven days.
The One Exception: PDF Conversion
To translate a PDF, MAITO first converts it to a Word document. That conversion is done by a third-party component from GroupDocs, and its licence requires the component to contact GroupDocs’ activation servers when it runs.
What that does and does not mean:
| What is sent | An activation signal confirming the component is in use |
| What is not sent | Your document, your translation, your language pair, your name, your e-mail, or anything else about you |
| When it happens | Only when you actually start translating a PDF |
| What never triggers it | Text translation, Word documents, plain-text documents, webpage translation, and everything else in MAITO |
MAITO does not load this component at startup. It is loaded on the first PDF translation of a session, and only after you have seen the notice that explains this. The component keeps working offline for up to seven days between activations; after that it falls back to a trial mode that may watermark the converted document.
If you would rather not
Cancel at the notice and translate a Word version of the document instead. Word, text and webpage translation never touch this component.
DeepL: Cloud-Based with Strong Privacy
How It Works
- Cloud processing: Text sent to DeepL servers in Germany
- GDPR compliant: Adheres to strict EU privacy laws
- ISO 27001 certified: International security standard
- Encrypted transmission: TLS encryption in transit
- Temporary storage: Data not retained long-term (Pro plan)
DeepL’s Privacy Commitments
- EU-based servers: Data stays within European Union
- No training on your data: Pro plan doesn’t use your content for AI training
- Secure deletion: Temporary data deleted after processing
- Compliance: GDPR, ISO 27001, SOC 2
MAITO’s Role
- No middleman: MAITO connects directly to DeepL
- No logging: MAITO doesn’t save your DeepL translations to external servers
- Local history: Translation history stored only on your PC
Good For
- Non-confidential content
- Professional translations (quality priority)
- Document translation
- Users comfortable with reputable cloud services
DeepL vs Google Translate
DeepL has stricter privacy policies than Google Translate, especially on Pro plans where data is not used for training. DeepL is GDPR-compliant and EU-based.
Data Storage on Your Computer
What MAITO Stores Locally
Configuration Files (%APPDATA%\Pangaia Software\MAITO\config)
- Settings and preferences
- API keys
- Language preferences
- Window positions
Translation Models (%APPDATA%\Pangaia Software\MAITO\models\)
- Local AI model files
- Stored indefinitely until you remove them
Translation History (optional)
- Recent translations shown in UI
- Stored locally only
- Can be cleared anytime
- Not transmitted anywhere
Logs (%APPDATA%\Pangaia Software\MAITO\logs\)
- Error logs for troubleshooting
- No translation content logged
- Can be deleted anytime
What MAITO Never Stores
❌ DeepL translations remotely
❌ Your translation history on servers
❌ Usage patterns externally
❌ Personal information
Security Measures
API Key Protection
- Encrypted storage: API keys encrypted using Windows Data Protection API
- No plaintext: Keys never stored in plaintext
- Secure transmission: Only sent over HTTPS to DeepL
Secure Connections
- HTTPS only: All internet connections encrypted (TLS 1.2+)
- Certificate validation: Prevents man-in-the-middle attacks
- No insecure protocols: No HTTP, FTP, or unencrypted connections
Update Security
- Signed updates: MAITO updates are digitally signed
- Velopack security: Automatic updates use secure Velopack framework
- Verification: Updates verified before installation
Privacy Comparison
| Aspect | Local AI | DeepL Cloud |
|---|---|---|
| Data Location | Your PC only | DeepL servers (EU) |
| Internet Required | No (PDF conversion activates a component online) | Yes |
| Documents | Translated on your PC | Uploaded to DeepL |
| Third-Party Access | None (GroupDocs sees an activation ping for PDFs, no content) | DeepL only |
| GDPR Compliant | N/A (never leaves PC) | Yes |
| Data Retention | Your choice | Temporary (hours) |
| Training Use | No | No (Pro), Maybe (Free) |
| Audit Trail | Local only | DeepL logs |
| Encryption | N/A (never transmitted) | TLS in transit |
| Privacy Level | Maximum | High |
Recommendations by Use Case
Maximum Privacy Needed
Use: Local AI Examples: Medical records, legal documents, classified info, confidential business data
Balanced Privacy + Quality
Use: DeepL (Pro plan for no training use) Examples: Business documents, professional content, non-sensitive translations
Cloud-OK, Quality Priority
Use: DeepL Examples: Marketing materials, public documents, general content
Hybrid Approach
Many privacy-conscious users configure both engines: Local AI for sensitive content (zero cloud exposure), DeepL for non-sensitive professional content (better quality).
Common Questions
Q: Can MAITO see my translations?
A: No. With Local AI, everything is on your PC. With DeepL, your text goes directly to DeepL - MAITO doesn’t intercept or store it.
Q: Can I use MAITO in a GDPR-compliant way?
A: Yes. Local AI is completely GDPR-compliant (data never leaves device). DeepL is also GDPR-compliant as an EU-based processor.
Q: What if my internet is compromised?
A: With Local AI, this doesn’t matter - no data transmitted. With DeepL, connections are TLS-encrypted, protecting against eavesdropping.
Q: Can I audit what data is sent?
A: Yes! We have a complete beginner-friendly guide: How to Verify MAITO Doesn’t Send Data. It walks you through using Windows Resource Monitor (no technical knowledge needed) to see exactly what network connections MAITO makes. With Local AI, you’ll see zero translation-related traffic - apart from a brief activation call when you translate a PDF. With DeepL, you’ll see encrypted HTTPS requests to DeepL servers.
Q: Are my documents uploaded when I use Local AI?
A: No. The file is opened, translated and written back on your own computer, and the translated copy is saved next to the original. The only outbound call in the whole flow is the PDF conversion component’s activation ping, which carries no document content.
Related Articles
- How to Verify MAITO Doesn’t Send Data - Step-by-step verification guide
- What Is Local Translation - Complete privacy details
- DeepL vs Local - Privacy comparison
- Configure Local Translation - Setup private translation