What we collect, and why

When Missed Call Rescue answers an incoming voice call, Telnyx records both sides of the call. Before spoken intake begins, the caller hears that the call is recorded and that the assistant is automated. Deepgram receives the live call audio to transcribe speech and run the voice interaction. We store the caller's phone number and the structured details they provide — such as service needed, city or ZIP, preferred timing, and a note they ask us to pass along — on the business's lead record.

Full voice transcripts are not written into Missed Call Rescue's durable voice call-outcome record, and raw call recordings are not copied into the application database. Transcribed caller and assistant turns can appear in the voice bridge's operational hosting logs while the service runs.

Text Recovery is a separate path. When a missed caller consents to text recovery, or when a caller texts the business line directly, we record the phone number and SMS conversation. Details the caller shares in that conversation are stored on the lead so the business owner can respond.

For business owners, we store the account identity from Google sign-in and, if calendar booking is enabled, an encrypted, owner-revocable Google Calendar token. We never see the owner's Google password.

Caller data is used to run the automated voice or text interaction, give the business owner the caller's request and, when the caller chooses a real offered time and booking is enabled, create the appointment. To do that, limited caller data is shared with service providers such as:

• Telnyx — our telephony provider, to deliver and receive calls and SMS and to make the raw call recording. When the account uses Telnyx-hosted recording storage, Telnyx stores that recording; Telnyx also supports account-level custom recording storage.
• Deepgram — our live voice processor, to transcribe caller speech, run the voice-agent session, and synthesize spoken replies. Our current voice requests set Deepgram's model-improvement opt-out.
• Anthropic and OpenAI — the current primary and fallback language-model providers in Deepgram's managed voice-agent configuration. Conversation text needed for a turn can be processed by the provider that serves it.
• Fly.io — hosts the voice bridge. Transcribed caller and assistant turns are written to its operational application logs.
• Google — when the business uses calendar booking, your appointment details (your phone number, and the service and location you gave) are written into the owner's Google Calendar event.
• OpenRouter — an AI message-classification service that receives your message text to work out what service you need. It also receives the text of emails sent to our support address, to group them into a daily summary for us.
• Resend — when the business has email summaries enabled, our email provider delivers the lead summary to the owner, which includes your phone number and the service and location you gave. It also receives email sent to our support address, so it can be summarized.
• Stripe — processes billing and subscription payments for business customers. Card details go to Stripe and are not stored by us.
• CRM or automation tools — when the business owner connects an integration such as Zapier, lead and booking details (caller name, phone number and job details) are sent to the destination the owner chose.

We do not sell caller or owner data, and we do not use it for advertising.

Mobile information — including SMS opt-in and consent status — is never sold or shared with third parties or affiliates for promotional or marketing purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

We keep the caller's phone number, SMS conversation, structured lead details and durable call outcome records for as long as they are needed to provide the service and to meet our legal, tax and dispute-resolution obligations — which includes keeping a record of consent and of any opt-out.

When a business owner applies to use Missed Call Rescue, we store the details from that application — the applicant's name, phone number and email, and the business details given. We keep these application records, including those for applications that are rejected or withdrawn, for as long as they are needed to run and account for signup and to meet our legal and dispute-resolution obligations; they are not on an automatic deletion timer.

Raw call recordings are created through Telnyx rather than copied into the Missed Call Rescue application database. When the account uses Telnyx-hosted recording storage, Telnyx stores those recordings; Telnyx also supports account-level custom recording storage. Missed Call Rescue does not currently run an application timer that deletes those Telnyx-held recordings, so their storage lifetime follows the account storage configuration and provider controls.

Voice transcript text can appear in Fly.io operational application logs; it is not part of the durable voice call-outcome record. Fly.io currently documents a seven-day searchable retention window for managed application logs. Deepgram voice requests use its model-improvement opt-out; Deepgram documents that opted-out request data is retained only for the time needed to process the request. Those provider rules do not set the retention of Telnyx recordings, Fly.io logs or our lead records.

Other technical and anti-abuse logs — delivery receipts, webhook and audit records — are cleared periodically once they are no longer needed for those purposes.

When you use our contact form, we collect your name, business name, email or phone, and any optional description of your current missed-call workflow. Resend sends these details to our support inbox to handle your inquiry. We do not create a customer lead record or send automated texts from this form.

We store a keyed digest of your IP address and an attempt timestamp for abuse prevention, cleared periodically once it is no longer needed for that purpose. The application does not store the inquiry body. Inquiry emails remain in our support inbox for handling; they are not on the automatic application deletion timer.

To request access or deletion of a website inquiry, email support@getmissedcallrescue.com.

Our public website counts page views with Vercel Web Analytics, without cookies. Only the public pages are counted, never the business dashboard or sign-in pages.

If you arrive from an ad, the ad's click identifier is kept in your browser tab and sent with a contact inquiry, so we can measure which ads work. It is not stored in a cookie or in our database.

Callers can opt out of the text-back conversation at any time by replying STOP; once opted out, we stop messaging that number from that business's line. Business owners can disconnect Google Calendar at any time from the dashboard, which revokes the stored token immediately.

Questions about this policy or a data request: email support@getmissedcallrescue.com. If another business that uses Missed Call Rescue texted you, you can also contact that business directly.