Mitletter handles documents that often contain addresses, account references, payment details, legal wording, health information, and other sensitive household context. Privacy therefore has to be treated as product behavior, not just policy text.
Mitletter processes account data, imported document files, extracted metadata, reminders, draft responses, and limited operational telemetry needed to run the service.
Depending on usage, that can include original scans, derived summaries, document titles, due dates, issue flags, and the account attributes needed to keep the vault available across sessions.
The data is used to ingest letters, extract key fields, produce summaries, support search, identify actions, keep reminders in sync, and maintain account access.
Mitletter is designed to help users understand and act on their letters, so the data processing should stay aligned with that purpose.
When live AI mode is enabled, OCR, summarization, translation, and search assistance are processed through the authenticated Mitletter API using the configured AI provider.
That processing is there to interpret the uploaded letter, extract the important facts, produce summaries, answer vault questions, and prepare action items or action suggestions.
The app uses secure device storage for session material and can cache document data locally on-device. The server stores user records, document payloads, reminders, and uploaded source files for sync and retrieval.
When configured, server-side data can be encrypted at rest in the Mitletter backend.
Mitletter does not exist to sell document data. Sharing should remain limited to infrastructure and processing providers needed to operate the service, such as hosting, storage, billing, and the configured AI provider.
Those providers only receive what is necessary for the relevant function.
Documents, reminders, sessions, and uploaded assets remain stored until the user removes them or deletes the account, unless retention is legally required.
Account deletion should remove the user profile, sessions, reminders, stored documents, ingest records, and uploaded source files from the service.
Users can export account data, delete the account, manage billing, and review supporting legal pages directly from the Mitletter surface.
Those controls are part of the product promise: the user should be able to leave with their data or remove it when needed.
For privacy-related support, export questions, or deletion issues, contact support@mitletter.com.
Need a human path
Contact support@mitletter.com or go back to the main site to review pricing, workflow, and the product overview.
