ReachAI — Privacy Policy

Last updated: 7 August 2026

ReachAI turns an Android phone into an SMS relay: it listens for texts from one trusted phone number you configure, sends the message to Anthropic's Claude to generate a reply, and texts the reply back. This page explains what data the app handles and where it goes.

Message content

• The text of messages relayed through the app is sent to Anthropic (the maker of Claude) to generate a reply. See Anthropic's privacy policy for how they handle that data.
• ReachAI itself does not store message content on any server — there is no backend and no message history or log kept by the app. Relayed texts do remain visible in the phone's default SMS/Messages app, since only that app (not ReachAI) can delete them from the device.

Settings stored on your device

• The trusted phone number you configure is stored locally on the relay device and used only to decide which incoming texts to relay.
• Your Anthropic API key is stored locally in encrypted storage (Android Keystore-backed AES-256 encryption) and is only ever sent to Anthropic to authenticate the app's requests on your behalf.

Diagnostics and usage data

ReachAI uses Firebase Crashlytics and Firebase Analytics (both provided by Google) to help diagnose crashes and understand basic app usage. This can include crash stack traces, device model and OS version, app version, and general app-event data. See Firebase's privacy and security documentation for details.

Permissions

On the phone acting as the relay, ReachAI requests SMS permissions (to receive and send text messages) and a notifications permission (to show its ongoing relay-status notification while running as a foreground service). These are used solely to operate the relay described above.

What ReachAI does not do

• No advertising or ad-tracking SDKs.
• No selling of your data to third parties.
• No server-side storage of your message content.

Contact

Questions about this policy: james@madrocket.co.uk