Legal & privacy

Privacy, in plain language.

This policy explains what Call Assistant collects and how information is handled when you sign in, place a call, or enable hold monitoring.

Effective August 3, 2026

Designed around the call—not around collecting your data.

  • No intentional call recording
  • No full transcripts saved by our server
  • Account deletion available in the app

01

Phone-number authentication

We use Firebase Authentication to send a one-time SMS code, verify your phone number, create your account, and keep you signed in. Firebase receives your phone number, verification information, device and network information, and security signals needed to prevent abuse. Your mobile carrier may charge its normal SMS or data rates.

02

Microphone and call audio

Call Assistant requests microphone access so you can speak during VoIP calls. While a call is connected, your microphone audio and the other party's audio are carried through Twilio. Muting your microphone stops your microphone audio from being sent, but it does not end the call or stop processing of the other party's audio. We do not use microphone access outside an active call.

03

Twilio and transcription

Calls are placed and transmitted through Twilio Programmable Voice, so Twilio receives call audio, the numbers involved, call identifiers, timestamps, status, and duration. Twilio Real-Time Transcriptions sends the representative/outbound audio track to its configured Google transcription engine. The resulting speech text is analyzed to detect phrases suggesting that a representative has joined. Transcription can begin when the call connects; representative alerts are sent only after you enable hold monitoring.

04

Are transcripts stored?

Our server does not save full transcripts in its database. It processes final transcript segments in memory. When a representative is detected, up to 120 characters of the matching transcript are included in the push-notification data sent through Expo and the device notification services. That excerpt may therefore be temporarily retained in service logs or notification systems under those providers' policies. Twilio and its transcription provider may retain or process audio and transcription data according to their terms and your Twilio configuration.

05

Notifications

If you allow notifications, the app obtains an Expo push token and associates it with your account while the server is running. Expo, Firebase Cloud Messaging on Android, and Apple Push Notification service on iOS may process the token, device information, and alert payload to deliver representative alerts. Notification permission is optional; you can disable it in device settings.

06

Other data we retain

Firebase/Firestore stores account entitlement information; destination numbers; account and Twilio call identifiers; call timestamps, status, and billed duration; daily usage and rate-limit counters; and fraud or security events. Active-call ownership, monitoring state, and push-token registrations are kept in server memory and are removed when no longer needed or when the server restarts. Short-lived rate-limit records are intended to expire through configured Firestore TTL rules. Other call, account, billing, and fraud-prevention records are retained while your account is active and as reasonably needed for billing, security, dispute resolution, legal compliance, and enforcing service limits.

07

Deletion

You can request deletion from Settings → Delete account or submit an account deletion request on this website. We verify account ownership before processing a website request. Deleting your account removes your Firebase Authentication account and clears live server state associated with it. Some call, billing, quota, and fraud-prevention records may remain after account deletion when reasonably required for security, accounting, disputes, or legal obligations; they are deleted or de-identified when no longer needed. Data already held by Twilio, Google, Expo, Firebase, Apple, or your carrier is governed by that provider's retention process.

08

Charges

Twilio charges the operator of Call Assistant for telephone connectivity and related services; Twilio does not bill you directly for calls placed in this app. Call Assistant may require an active paid subscription or prepaid call credit, and one credit may be consumed when a non-subscriber starts a connected call. Your carrier, internet provider, app store, or payment provider may separately charge you for SMS messages, mobile data, internet access, subscriptions, or credits. Any price shown at purchase controls; this policy does not create an additional fee.

09

Your responsibilities

You are responsible for calling only numbers you are authorized to call and for complying with notice, consent, recording, wiretapping, and transcription laws that apply to everyone on the call.

10

Questions?

For privacy questions or a deletion request you cannot complete in the app, use the developer contact listed for Call Assistant in the app-store listing.