TranslatePhoto.org Image Translation Privacy Policy
This policy explains what the application sends to OCR and translation providers, what signed-in accounts can store, how deletion works, and which production controls affect privacy.
Three privacy choices to make first
- Minimize. Crop the image to only the text needed for translation.
- Redact. Permanently remove names, faces, codes, and other details that are not needed.
- Choose the right route. Use an approved local or contracted workflow for regulated or confidential material.
What each type of use stores
Guest translations
Guest uploads are processed in application memory and sent to the configured OCR and translation providers. The app does not intentionally place guest images in the account file store. Hosting systems and providers may still process request data under their own policies.
Signed-in account files
Google sign-in provides an email address, account identifier, and display name. For a signed-in user, the normalized image, extracted text, translation, and a JSON copy may be saved for up to 30 days. The user can delete a saved result earlier.
Which provider receives what
Text recognition receives the prepared image
The prepared image bytes are processed to extract visible source text.
Translation receives the extracted text
The extracted text and selected target language are processed to create the translation. Before sending sensitive content, use the photo translation privacy checklist.
Security controls in the application
Credentials stay in server environment variables and do not appear in page source. Private routes use noindex response headers and no-store caching. Account downloads and deletions include ownership checks.
Production review is still required
Privacy questions and deletion requests can be sent to [email protected]. Requests must include enough information to locate the relevant account or saved result without sending the sensitive image again. The terms of use explain the separate duties that apply when using the service.