RelayPhone privacy policy

Updated 2026-11-09

RelayPhone is provided and operated by Zia Capital, LLC. Zia Studio is its app publisher name. This policy covers RelayPhone's connected apps and service. Contact support@ziahamza.com about privacy or data requests. Keep passwords, sign-in codes and private communication content out of an initial support email.

Information and purposes

We handle account and sign-in information, authentication records and sessions; your cloud numbers, preferences and calling devices; notification tokens; participants' numbers; call timing and status; messages and received attachments; and recordings, transcripts, summaries and assistant outcomes where captured. Assistant features process the audio, text and context needed for your task. Google and Apple sign-in do not give RelayPhone your provider password.

We use this information to authenticate you, deliver communications and notifications, maintain history and settings, operate numbers, provide assistant features, respond to requests and address reliability, security and abuse.

Audio recording starts off for new accounts. Existing accounts keep their current recording behavior. You can choose automatic recording during setup or in Settings and change recording before or during a call. Stopping recording stops new retained audio while earlier recorded audio remains subject to its retention setting. Transcription and real-time assistant processing are separate; turning off saved audio alone does not stop them. Starting a recording when transcription is off also enables transcription, as the control explains. You are responsible for required participant permissions and disclosures.

Device contacts require permission. Imported contact details stay on the device unless you choose an action that sends them to RelayPhone. Using a number to call or text sends it to RelayPhone and its carrier. Sharing contacts for caller screening sends eligible contact numbers and a device identifier. Choosing a language for an imported contact sends its number, source contact and device identifiers, and language preference to RelayPhone. Adding an app contact saves the details you enter to the connected service; these actions do not upload the rest of your address book.

For SMS, we process recipient numbers, message content, delivery results, keyword requests and suppression information. Opt-out status applies across the RelayPhone senders using the same SMS program so a sender's change of account or number does not remove a recipient's block. See the SMS program page for STOP, HELP and START.

Providers and diagnostics

Providers include Telnyx and other telecommunications carriers for numbers and communications; LiveKit for call media and rooms; OpenAI for speech, transcription and assistant processing; Cloudflare, PlanetScale and Turso for infrastructure and storage; Apple and Google/Firebase for selected sign-in and notifications; and PostHog for diagnostics and masked interface replay. Recipients and their providers may keep their own copies. Processing may occur outside your country. Limited disclosures may be needed for legal obligations, security, fraud or abuse.

PostHog receives app interactions, onboarding and screen events, operation outcomes, JavaScript errors and sanitized diagnostics. After sign-in, these may be linked to an opaque RelayPhone account identifier. Interface replay is configured to mask text, inputs and images and does not record call audio. Diagnostic filters exclude communication content, phone numbers, contacts, authentication headers and recording URLs. Configured diagnostics begin before sign-in; the current app has no individual diagnostics consent or opt-out control. Infrastructure processes request and network information, and support receives information you choose to send.

We do not sell personal information or use an advertising integration. Mobile information and SMS permission or opt-out data are not sold or shared for third-party marketing or promotion. Providers may process that data to deliver and administer the messaging program.

Retention and requests

Saved call audio normally expires after seven days. Available settings request earlier deletion after a completed summary or one day after reviewing finished text. The applicable deadline depends on when the recording was captured or processed. Audio deletion is asynchronous; provider or storage retries can delay physical erasure. Transcript and caption text expires 30 days after call creation unless cleared earlier or another expiry is recorded. That expiry preserves summaries, call history, assistant outcomes and SMS/MMS history, including received images. Those records, settings and cloud contacts have no general automatic age-based expiry and can remain until removed or a data-deletion request is completed. Recipient opt-out and sender-permission records protect SMS recipients and may need separate handling. Provider, diagnostic, support and backup copies have separate requirements; no uniform maximum or completed physical-erasure timetable is promised.

Delete your personal account from Settings after confirmation. End calls and pending assistant tasks, resolve unconfirmed number orders and leave shared accounts first; transfer shared ownership before leaving if necessary. Account access is closed and background cleanup removes sign-in identities, sessions, API keys, personal calls, texts, attachments, contacts, groups, transcripts, summaries and recordings, and releases your RelayPhone numbers. Recording cleanup includes a final storage sweep a day after its first confirmed removal. Provider or storage failures can delay completion and are retried. Offline devices clear saved account data when they next confirm sign-out. Creating an account again does not restore old history. Ask support for a copy, correction, specific data deletion or help with retained copies; support verifies ownership. Provider, diagnostic and backup copies remain subject to their separate retention requirements; no backup-expiry timetable is published. Recipients' copies and your exports need separate handling.

Application requests use HTTPS. Ordinary carrier calls and SMS are not end-to-end encrypted; providers process their content. Cloud speech and recording features also require service-side access. Contact support if you believe information about a child was submitted or a privacy right was not met. We will update this policy when these practices change.

When a sender shares a recipient invitation, we store their chosen public name, current assigned number and an unlisted invitation code. Anyone with that code or link can view the invitation while it remains valid. Codes expire after seven days or when the current assignment ends. Opening an invitation does not establish SMS permission.