Proof Page
Public AI and Data-Handling Claims, Without Guesswork
This page exists to keep privacy and AI wording precise. It separates what LaTeX Cloud Studio states publicly today from what still belongs in roadmap or guided-rollout conversations.
Safe public wording
- Documents are not used to train AI models
- Privacy-first document handling
- EU-oriented hosting and GDPR-oriented handling
- Live AI assistance inside real LaTeX projects
Do not overstate
- Blanket legal compliance claims without context
- Public GA claims for SSO or audit controls
- Suggestion mode or track changes as live today
Proof Links
Use the right proof page for the right claim
The website should link to the page that matches the claim. Privacy claims point here or to the security docs. Migration claims point to the migration guide. Commercial pages should not improvise beyond that.
Security & Privacy docs
Canonical public source for privacy-first handling, training-data language, and EU-oriented posture.
Compliance overview
Marketing-safe explanation of infrastructure, consent, and enterprise-boundary language.
Migration guide
Use this when a claim depends on ZIP import, GitHub sync, or transfer workflows.
What we state publicly
- Documents are not used to train AI models.
- AI assistance is positioned as in-editor help for writing, proofreading, and fixing problems.
- Public materials frame the product around privacy-first handling and EU-oriented infrastructure.
What stays constrained
- We do not present self-serve enterprise identity or audit controls as fully public GA.
- We do not treat GDPR-oriented posture as a substitute for legal review in a customer-specific context.
- We do not claim roadmap review workflows like track changes as already live.
Proof table
Each claim should map to a public source
| Claim | Public proof | How to use it |
|---|---|---|
| User documents are not used to train AI models. | Security & Privacy docs | This supports the public training-data claim on marketing pages. It does not by itself imply broader legal certification language. |
| AI editing, proofreading, and problem-fixing features are live in the product. | Editor and AI assistance docs | This supports claims about in-editor AI help. It does not support suggestion-mode or track-changes language that is still roadmap. |
| Public positioning is privacy-first and EU-oriented. | Security & Privacy docs | This supports careful wording like EU-focused hosting or GDPR-oriented handling. It is weaker than claiming blanket legal compliance in all contexts. |
| Enterprise identity and admin controls are not broadly documented as GA yet. | Enterprise & Admin Overview docs | This is why website pages should treat SSO, audit controls, and similar features as guided rollout or roadmap unless public docs change. |