Privacy Policy
How Textimony protects your private message records.
Textimony processes uploaded message exports to provide case analysis, reports, participant maps, and review tools.
Server-side analysis
Uploaded files are transmitted to the Textimony app service, stored as account-scoped case artifacts, parsed, and analyzed by the worker process.
Model training
Uploaded conversations stay inside the case workflow and outside public model-training or data-broker workflows.
Your choices
Users can choose what to upload, request access or deletion, and control what reports or exports they share outside Textimony.
What is processed
Account data, case names, notes, participant mappings, uploaded exports, normalized messages, reports, annotations, redaction choices, analytics events, and security logs may be processed to operate the service.
Security controls
The live service is delivered over HTTPS. App sessions use HTTP-only cookies, case artifacts are account scoped, and generated reports remain tied to source hashes, upload metadata, and report manifests.
Retention and deletion
Case data remains available while the account and case are active. Deletion requests are reviewed against backup limits, legal holds, disputes, abuse prevention, security incidents, and operational constraints.
Support access
Support should prefer metadata, logs, hashes, and user-provided screenshots before raw message access. Privacy questions, access requests, correction requests, export requests, and deletion requests route through privacy@textimony.io.
Analytics boundary
Public-site analytics, including Microsoft Clarity on public pages, are used to understand page performance and product interest. They are separate from private case content, uploaded conversations, source files, participant maps, and generated reports.
Disclosure boundary
Textimony does not sell uploaded conversations, use them for public model training, or expose private case records in public discovery files. Public sample messages and charts are labeled as illustrative and do not use real case data.