Privacy
Translation privacy: practical boundaries
Understand what to avoid sharing, how private history should be cached and why file links must expire.
4 min readUpdated: Aug 1, 2026
01
Treat translation text as private by default
Personal messages, customer conversations and documents can contain identifiers even when the user does not think of them as sensitive.
Private translation text should stay out of metadata, structured data, analytics payloads, shared caches and application logs.
02
Separate public and private caching
Versioned icons and static scripts benefit from long immutable caching. Account pages, histories and signed file URLs require private or no-store policies.
The service worker should cache a safe application shell, never authenticated API responses or personal files.