Privacy isn't
an afterthought.
Here's what TextSentry does with your information, what stays on your device, and what you control.
TextSentry Android now offers optional Google sign-in through AWS Cognito. Google and AWS process basic account identity (including email) and the app stores OAuth tokens encrypted with Android Keystore. No SMS content is sent to the TextSentry account backend; eligible analysis text goes directly to TypeSafe AI (Jev) over HTTPS, subject to that provider's privacy and retention terms. Managed subscription keys are still under development and not yet used by Android. The website itself uses no analytics, advertising trackers or cloud message archive.
1. How the app works
Google Play edition (manual review)
You choose text to paste or explicitly share with TextSentry. This edition does not read your incoming SMS, inspect your inbox, monitor messages in the background or send SMS automatically. You review an editable AI suggestion and may choose to open your device's existing messaging app to compose a message. Your messaging app—not TextSentry—sends it when you decide.
Experimental sideload edition (SMS automation)
Only after you enable SMS monitoring and grant Android SMS permissions can TextSentry evaluate eligible incoming SMS. The text and sender may be transferred to TypeSafe AI for evaluation. Automatic replies require separate opt-in. Android WorkManager may temporarily store unprocessed incoming SMS bodies and sender data in an app-private, on-device work queue while processing is pending. After processing an SMS, TextSentry stores up to 100 recent evaluated messages in a private, AES-GCM-encrypted, Android Keystore-backed history on the device. Each entry includes the original processed text, sender, timestamp, Jev match probability, suggested STOP reply and Android's send result. The app also retains brief decision summaries and timestamped hashes used to prevent duplicate replies. Only messages processed by TextSentry are stored, not the full SMS inbox.
2. Information processed
- Google sign-in: Optional first-time sign-up and returning-user login use Google and Amazon Cognito. Cognito stores account identifiers such as email and user ID. The Android app encrypts access, ID and refresh tokens using Android Keystore; it never sees your Google password. Signing out removes the local account session, not the remote Cognito account.
- AI provider credentials: Your API key is stored locally and encrypted with Android Keystore. Your prompt and confidence threshold are stored in local app settings. The provider and model are fixed to TypeSafe Jev latest.
- Message content: Text you explicitly submit in the Play edition, or eligible incoming SMS bodies and sender numbers while sideload monitoring is enabled, is sent only to TypeSafe AI for analysis. For manually submitted Play messages, the app uses a placeholder sender number for analysis.
- Encrypted message history: The local history retains the original text of messages evaluated by TextSentry, their sender (or a manual-review label), timestamp, numeric Jev confidence, optional STOP suggestion, and verified, pending, failed or preview-only send status. The archive is limited to 100 entries, encrypted using a separate Android Keystore key and never uploaded to a TextSentry server. In the Play edition, this applies only to text you explicitly consented to analyze, and the app cannot verify what you subsequently send from your usual messaging app.
- Phone numbers for composing: In the Play edition, a number you enter for an outgoing SMS draft is passed to your Android messaging app. It is not sent to your selected AI provider by TextSentry.
3. What the AI provider receives
TypeSafe AI receives the text needed for the requested analysis. TypeSafe may process, store or retain submitted content according to its privacy and retention policies. TextSentry cannot control provider-side retention or delete data from those systems. Check TypeSafe's terms before submitting private information. Avoid submitting one-time codes, passwords and other sensitive text.
4. Your control and consent
Google sign-in is optional in both Android editions and does not enable SMS monitoring, auto-replies or paid AI access. You may sign out locally; contact support for remote account-deletion inquiries. In the Play edition, you must explicitly check the consent box and choose Analyze for each submitted message. The box resets after an analysis. In the sideload edition, you can independently enable or disable SMS monitoring and automatic sending and can pause monitoring. Both editions allow local data deletion. TextSentry does not use your messages for advertising or sell them.
5. Storage and deleting your data
TextSentry stores its configuration, provider key, encrypted Google/Cognito account tokens, encrypted message history (up to 100 evaluations), brief decision summaries and anti-duplicate records on your device. You can clear just the archive through History → Clear history or Settings → Clear local decision history. To erase all app-owned records and the history encryption key, select Delete all TextSentry app data, or use Android Settings → Apps → TextSentry → Storage → Clear storage. The app disables and cancels pending work when local data is deleted. These controls remove only TextSentry-owned data on the device and do not delete carrier SMS from your messaging inbox. Sideload permissions are RECEIVE_SMS for monitoring and SEND_SMS for separately approved auto-replies; no READ_SMS permission is needed to save messages this app already processed. Deleting system inbox messages requires a complete default SMS/MMS handler role, which TextSentry does not provide. History therefore records "Not deleted by TextSentry," which does not indicate whether your other SMS app later removed the message. Local data deletion cannot remove text already submitted to TypeSafe AI. Contact that provider separately to exercise provider-side deletion rights.
6. Sharing, tracking and security
Current Android builds have no in-app advertising, no ad identifiers, no tracker SDK, and no TextSentry-hosted analytics. Communications with TypeSafe AI use HTTPS. Android controls access to SMS permissions in the sideload edition. The website at TextSentry.org is static: it does not set cookies, collect form submissions or send demonstration text to any server. Ordinary hosting infrastructure may log HTTP requests.
7. Google accounts and future managed subscriptions
Android now supports optional Google sign-in/sign-up through Cognito. RevenueCat paid subscription verification and capped OpenRouter subscriber-key retrieval remain under development and are not yet live in the Android classifier. The website sign-in callback and checkout are not yet implemented; this website does not collect account login details or payments. Cognito retains limited account identity and the backend may associate future entitlement and key metadata, but no SMS content is sent to AWS. Google's and AWS's own service terms govern identity processing.
The privileged OpenRouter management credential is held in AWS Secrets Manager for server-side operations. It is not a subscriber credential and is never embedded in the static website or Android APKs.
8. Children and limitations
TextSentry is not designed for children. AI decisions can be inaccurate and should not be relied on for emergencies, identity verification or other critical communications. Automatic replies may have carrier charges, and replying to malicious senders can confirm that your number is active.
9. Contact and changes
For general app support, visit the project's GitHub issue tracker without sharing personal SMS content, phone numbers or API keys. For confidential security matters, use GitHub's private vulnerability reporting. Google sign-in is available in the Android app; managed subscriptions and capped OpenRouter client key retrieval remain in development and are not yet available. The website sign-in callback is not yet implemented. This policy may be updated as TextSentry evolves; the last-updated date will change when material revisions are made. It applies to both app editions and the static TextSentry.org website.
For a source-maintained reference, see the Android project's privacy policy.