Legal
Privacy Policy
This policy explains how TextTrace handles information when you use the iPhone, iPad, or Mac application. TextTrace is the controller of information processed for its own purposes. Questions, rights requests, and complaints can be sent to ataerdal.dev@gmail.com.
See the app
A clear path from chat to file.
- Bring it in
- Check the details
- Export the result
Information we process
- Content you choose: supported chat export files and included attachments, selected iPhone backup data where that feature is available, screenshots, photos, scans, screen recordings, recognized text, edits, record titles, folders, and the exports you create. Retained sources and records are stored in the app’s private local container until you delete them or uninstall the app.
- Visual OCR evidence: exact duplicate screenshots and unchanged recording frames are removed locally without text recognition. Necessary unique full frames, a content hash, and job metadata are sent through TextTrace’s private backend to Google Vision to read visible conversation text and layout. Supported structured chat files and backup imports are parsed directly and are not sent to Google Vision for OCR.
- Account and security data: Firebase creates an opaque anonymous user ID and processes authentication, IP, token, and App Attest/App Check integrity data. TextTrace does not ask for your name, email address, phone number, contacts, or precise location to create this account.
- Purchases: Apple processes payment. RevenueCat receives the anonymous TextTrace user ID, App Store transaction and purchase history, product and entitlement status, app/device metadata, and related subscription events. RevenueCat does not receive imported chat content.
- Analytics: Firebase Analytics processes an app-instance/device identifier, app and device properties, operating system, app opens and updates, product interactions, subscription events, session information, and approximate geography inferred from network information. TextTrace disables Google Analytics collection of IDFV in its app configuration and does not use IDFA for advertising.
- Diagnostics: Firebase Crashlytics processes installation identifiers, crash stack traces, device/app/OS information, performance and diagnostic data, and sanitized error codes. TextTrace does not add recognized text, record titles, source files, file names, URLs, hashes, authentication tokens, or Firebase user IDs to Analytics events or Crashlytics reports.
- Support: if you contact us, we process your email address, message, and information you choose to provide so we can respond.
How and why we use information
We use information to import and preserve selected sources, perform the Google Vision OCR requested when you import visual media, create searchable records and exports, authorize Pro features, process and restore subscriptions, prevent fraud and abuse, secure the service, diagnose failures, provide support, and measure whether core product flows work.
Where applicable law requires a legal basis, processing is necessary to provide the service you request and perform our contract; based on our legitimate interests in security, fraud prevention, diagnostics, and limited product analytics; or necessary to comply with law.
No tracking, advertising, sale, or AI training
TextTrace does not track you across other companies’ apps or websites, does not use IDFA, does not serve third-party advertising, and does not sell or share personal information for cross-context behavioural advertising. TextTrace does not use selected content or recognized text to train generative AI models.
Service providers
TextTrace uses Apple for App Store billing, device frameworks, App Attest, and platform services; Google Cloud and Firebase for anonymous authentication, App Check, private backend infrastructure, Analytics, Crashlytics, and Google Vision OCR; and RevenueCat to validate purchases and manage subscription entitlements. These providers process information under their own terms and our service arrangements. We may also disclose information when required by law, to protect users or the service, or in a business transfer subject to appropriate safeguards. We do not give service providers permission to use imported content for their own advertising.
Retention and deletion
Local records, retained sources, edits, folders, and generated exports remain on your device until you delete them or uninstall the app. Cloud OCR evidence is deleted after processing, cancellation, terminal failure, or acknowledgement by the device. A scheduled sweeper, database TTL, and storage lifecycle rule are deletion backstops; uploaded evidence objects are capped at 24 hours. After the app safely stores and acknowledges a successful result, the backend deletes the source, result, and job metadata.
Analytics, Crashlytics, authentication, purchase, security, and support records follow the retention periods of the relevant service and may be kept as needed for security, fraud prevention, accounting, dispute resolution, or legal compliance. Firebase documents a 90-day retention period for Crashlytics crash data and may take up to 180 days to remove deleted Authentication data from live and backup systems. Apple and RevenueCat may retain transaction records as required for billing, fraud prevention, tax, and legal obligations.
Your choices and rights
You can delete an individual record, delete all imported data, or use Delete Account & Data in TextTrace Settings. Account deletion removes local imported data, requests deletion of associated remote OCR jobs, and deletes the anonymous Firebase account; it does not cancel an App Store subscription or automatically erase records Apple must retain. Manage or cancel a subscription in Apple Account settings.
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information, and to withdraw consent. Email ataerdal.dev@gmail.com to exercise a right or ask about RevenueCat and support records. We may need limited information to verify the request. You may also complain to your local data-protection authority.
Security and international transfers
TextTrace uses HTTPS, App Attest/App Check, anonymous authentication, private cloud storage, short-lived upload URLs, least-privilege service identities, integrity hashes, and content-free telemetry controls. No method of storage or transmission is completely secure. Apple, Google, and RevenueCat may process information in the United States and other countries under their contractual and legal transfer safeguards.
Children, changes, and contact
TextTrace is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided information, contact us so we can investigate and delete it where required.
We may update this policy when the product, processors, or law changes. Material changes will be reflected by a revised effective date and, where required, an in-app notice or renewed consent. Contact: ataerdal.dev@gmail.com.