Let's make it
simple.

Not yet. A Play-oriented build is prepared for testing and review, but Google has not approved or published it. The Play edition is intentionally a permission-minimized, manual message assistant.

The experimental sideload edition can request SMS permissions to monitor messages and optionally send automatic replies. Google Play restricts SMS permission use for non-default messaging apps, so the Play edition offers only manual, user-initiated message review.

The current app filters vote reminders, political campaigns and marketing ads; all three categories are on by default. Jev uses a single request for all enabled categories and does not require the incoming message to say “Reply STOP.” You choose the threshold and can preview before auto-sending.

Not currently. History indicates “Not deleted by TextSentry.” Android requires the active default SMS application to remove inbox messages. Clearing TextSentry history does not delete carrier SMS.

Google sign-in/sign-up is available in both Android editions through Cognito. RevenueCat subscriptions and capped OpenRouter keys are not yet live, so analysis still requires your own TypeSafe AI key.

No. You explicitly share or paste text, review an AI suggestion, and open your default SMS app to compose it yourself. The Play edition has no SMS monitoring or auto-send permissions.

No. The management key is a privileged credential for trusted AWS backend operations, kept in Secrets Manager. It will never be exposed on this site or built into Android APKs. Current Android builds continue to use your own TypeSafe key; subscriber key issuance, Google login and payments are not yet available here.

Current builds use TypeSafe AI’s Jev System One (jev-latest) with your own key. You choose categories and a confidence threshold; managed OpenRouter access is a separate future platform direction, not live.

In current builds, your TypeSafe key is encrypted locally in Android Keystore and requests go directly to TypeSafe. Optional Google account login is available via AWS Cognito, but managed subscriber keys are not yet integrated into Android. No SMS content is sent to AWS.

The example switcher uses hardcoded, fictional messages. It does not call an AI service, send SMS or transmit any of your input.

Eligible or explicitly submitted message content is sent over HTTPS to TypeSafe AI. Provider retention and privacy practices are governed by its own terms, not by TextSentry.

History shows recent processed message text, the Jev probability, suggested reply and confirmed, pending, failed or preview-only send status. Up to 100 entries are encrypted on your device. SMS is never marked deleted by TextSentry, since it cannot delete inbox messages without becoming the default SMS app.

Use Delete all TextSentry app data in Settings, or Android’s Clear storage. This removes local settings, encrypted message history and the API key, but not messages in your SMS inbox or data already sent to the AI provider.

No. The early automatic workflow in the sideload edition is for SMS; RCS, MMS and third-party messenger integration are not supported.

Visit Android GitHub Releases for signed experimental sideload APKs. Debug build artifacts are also available from CI.