Privacy Policy

Account data: When you create an account, we collect your email address and profile information through Supabase Auth.

Optional feedback when you leave: At a few points where you may be leaving VeraDial, you can optionally select a reason and enter one short line explaining why. You can always skip both fields, and skipping changes nothing about the action you were taking. We ask at these moments: when you delete your account, when you release your last phone number, and when you return to the app after turning off your subscription in the App Store or Google Play. We store a response without your user ID, email, phone number, IP address, device identifier, or subscription-provider identifier — including when your account still exists. We keep only the selected reason, the short line you entered, a rough account-tenure range, which of those moments it came from, and the date. Because you choose what to type, please do not include personal or sensitive information in the short line.

Caller profile: If you use AI Calling, we store your display name, website, and caller context that you provide. These are used to identify you on AI calls and voicemail greetings.

Phone numbers: We store information about your VeraDial-purchased and customer-provided phone numbers (including Twilio SID, capabilities, region, country, provisioning source, routing status, and custody status) and any verified caller IDs you add.

Number porting and custody: If you ask us to check or transfer a number, we collect the number, current carrier and account-holder details, authorized representative name and email, service address, account telephone number, account number or PIN where required, a recent carrier bill or other supporting document, authorization and cutover acknowledgments, and the provider status and identifiers needed to administer the request. Please provide carrier credentials and documents only through the porting process VeraDial identifies for you, not in an ordinary support message unless we specifically instruct you to do so.

Carrier account numbers, PINs, bills, and authorization documents are used only for the requested eligibility or transfer work. They may pass through an operator-controlled local submission process to Twilio, but VeraDial does not intentionally retain their raw values in its application database, logs, analytics, or durable operator records. A supporting document is uploaded to Twilio; VeraDial retains the resulting provider document identifier rather than the document itself. We retain the phone number, a one-way phone fingerprint, last four digits, account association while applicable, workflow and number type, authorization version and timestamps, provider order and phone-number identifiers, safe status and failure categories, routing evidence, event history, temporary-number disposition, and port-out or release evidence needed to operate the transfer and protect custody. Twilio and the carriers may retain the information they receive under their policies and legal or carrier requirements.

Call records: We maintain call logs including from/to numbers, duration, timestamps, and Twilio call SID for your account history.

Call recordings: When you enable call recording on outbound calls or AI calls, dual-channel audio is recorded by Twilio and stored on their servers. We store a reference to the recording and provide playback through our app.

Call transcripts: When you record a call, the audio is automatically sent to a third-party speech recognition service (Deepgram) for transcription. We store structured transcripts including speaker identification, text, and timestamps alongside the call record.

Call screening data: When call screening is enabled, we store the screening interaction data including the conversation transcript, the caller's stated identity and intent, a conversation identifier, and timestamp. We also store the line's configured and effective caller-notice mode; the exact notice text and version, if any; whether delivery started, completed, or was interrupted when that evidence is available; the reason a configured mode fell back; and, for permission mode, the structured permission outcome and time. When permission mode is used through the supported LiveKit path, the caller's answer to the permission question is processed in real time only to classify it as granted, refused, or unclear. VeraDial does not store the words spoken before permission; after a clear yes, transcript retention begins with the post-permission conversation. We maintain a versioned record of the exact acknowledgment accepted by an account holder who enables no spoken notice. We may re-process stored screening transcripts using Google's Gemini API to evaluate and improve receptionist quality, but screening calls whose effective mode had no spoken notice are excluded from that quality-grading processing. These evaluations produce internal quality ratings only; they do not create customer-facing content and do not send your data to any additional provider.

Assistant browser previews: When you start a signed-in Preview Vera session for one of your lines, your browser microphone audio and that line's current receptionist profile are processed in real time through the same LiveKit and AI voice services used for the demo receptionist. This preview does not place a phone call or test carrier forwarding. We store the final conversation turns under the existing demo-transcript controls, plus the account, selected line, random session identifier, start/end times, expiry, and end reason needed to limit, operate, and measure the feature. Product-analytics start and completion events include those identifiers and duration but not phone numbers, microphone audio, profile content, or transcript text.

Call forwarding: If you configure call forwarding, we store your forwarding phone number and enabled/disabled preference on your profile.

Location data: When you make or receive calls, we may collect your device's GPS coordinates to associate a location with the call record. Location data is used to display your calls on the Call Map feature. Location collection requires your permission and can be disabled through your device's system settings.

SMS content: We store message bodies, sender/recipient numbers, timestamps, and delivery status for messages sent and received through the service. For inbound MMS, we copy any attached media (such as photos) from Twilio into private cloud storage (Supabase Storage) and reference it on the message; the app retrieves it through short-lived signed URLs.

Consent records: We maintain SMS consent status and timestamps to comply with telecommunications regulations.

AI SMS receptionist drafts: If you turn on the AI SMS receptionist for one of your lines, the text of inbound messages on that line, recent message history for that conversation, and your line's receptionist identity and instructions are sent to Google's Gemini API to draft a reply. If an inbound message includes photos or other media (MMS), that media is sent to Gemini as part of the request so the draft can take it into account. We store the drafted reply, its status (pending, approved, sent, auto-sent, or discarded), and the timestamps of those decisions alongside the conversation. Each line runs in one of two modes: in approve mode nothing is sent until you review and tap to send, and you may edit the draft first; in auto mode an eligible draft is sent automatically, and a draft is downgraded to pending review when the model asks for a human. When Contact Memory is also enabled, the relevant contact summary may be included as context on the review lane.

AI email receptionist: If you turn on the AI email receptionist for one of your lines, Resend receives email sent to that line's VeraDial inbox address and passes it to VeraDial. We verify available sender-authentication results, block automated and list mail, convert the message to bounded plain text, and store the sender address, recipient line, subject, sanitized body, reply-thread identifiers, authentication summary, timestamps, and limited attachment metadata such as filename, media type, and size. VeraDial does not download, open, store, or send attachment contents to the AI in this version. The sanitized message, recent messages in that customer-started thread, and the line's receptionist identity and instructions are sent to Google's Gemini API to draft a reply. We store the draft, any owner edits, its review or delivery status, and the reply. In approve mode, nothing is sent until the account holder reviews it. In auto mode, only an eligible reply may send automatically; complaints, sensitive or uncertain requests, and messages with blocked attachments wait for human review. Replies remain locked to the authenticated sender and cannot start a new thread or select another recipient.

Message safety and abuse prevention: We may use automated systems and service providers to analyze attempted messages and related account activity to prevent fraud, abuse, illegal use, and violations of carrier or service rules. This processing may result in a message being refused. We retain limited safety and decision records as described in Section 6.

Carrier registration and business identity: If you ask to activate US business texting, we collect the business identity and messaging-program information required by mobile carriers and their registration providers. This may include your confirmed legal and display names, business address and country, business type, whether you have a tax or business registration number, website, public Terms, Privacy, and opt-in evidence URLs, messaging use case and description, sample messages, and your attestation that the information is accurate and that you have authority to submit it. We store only the safe metadata needed to show and operate the registration, such as masked identifiers, provider object IDs, statuses, failure categories, timestamps, sender bindings, public evidence URLs, and registration-event history.

For direct carrier registration, raw tax or government identifiers, identity-verification answers, and one-time passcodes may pass through VeraDial's server to Twilio for the requested submission, but VeraDial does not intentionally persist those raw values in its database, logs, analytics, or durable operation records. Twilio may retain the identity information it receives under its own policies and carrier requirements. Toll-free verification may instead collect full identity information directly in Twilio's hosted interface.

Carrier-registration fees: When a carrier-registration fee is offered, we store the displayed product, amount, currency, billing period, purpose, registration revision, authorization status, and RevenueCat transaction identifiers needed to match the purchase to the exact registration action and to handle failure, refund-review, renewal, or dispute states. We do not store payment card details.

Voicemail: We store voicemail recordings, transcriptions, duration, and caller information for voicemails left on your VeraDial number. Voicemail audio is recorded by Twilio and transcribed by a third-party speech recognition service (Deepgram).

Voicemail greetings: If you create a custom voicemail greeting, we store the greeting audio file. For AI-generated greetings, we also store the text you write and the voice you select; audio is generated by a third-party AI provider (ElevenLabs or Cartesia, depending on the voice type). For recorded greetings, your uploaded audio is converted to MP3 format on our server. All greeting audio is stored in cloud storage (Supabase Storage).

Voice cloning: If you create a cloned voice, we collect the voice sample you record, your consent acknowledgment, and metadata about the resulting voice model. The raw voice sample is processed server-side and sent to Cartesia to create the clone; VeraDial does not retain the raw sample after successful clone creation. We store the Cartesia voice identifier, clone name, consent record, and generated greeting audio made with that clone until you delete the clone, the greeting, or your account.

Message dictation: If you use the microphone button to dictate a message (for example in an SMS conversation or the in-app account assistant), the short voice clip is sent from your device to our server and then to a third-party speech recognition service (Deepgram) to convert your speech to text. The clip is processed only to produce the text and is not stored by VeraDial; the app removes the clip from the device's temporary storage after conversion. Only the resulting text appears in your message box, and it is retained only if you send or save the message. Dictation clips are limited to two minutes.

AI Call data: When you use AI Call, we store the phone number called, your call goal and notes, call duration, the AI provider used, and the full conversation transcript and summary generated by the AI agent. If you enable recording on an AI call, the recording is stored by Twilio and referenced in your account. Call audio is processed in real-time by the selected AI provider (ElevenLabs, OpenAI, Google, or xAI) and is not stored by VeraDial.

Call translation: When you enable two-way translation on an outbound call, your call audio and the other party's audio are streamed in real-time to OpenAI to generate translated speech. Translation audio is processed in transit to produce the translation and is not stored by VeraDial. We store the translation status of the call (whether translation was used and its outcome) alongside the call record.

Contact memory: If you explicitly turn on Contact Memory in Profile > Contact Memory, we generate a rolling AI summary for each phone number you interact with, using your call transcripts, voicemail transcriptions, AI call transcripts and summaries, and SMS message content from your own account. Summaries, a suggested next-call goal, and the phone number are stored in your account. Summarization is performed by a third-party AI provider (Google Gemini). When Contact Memory is disabled, existing summaries are not read through the feature and new summaries are not generated; existing summaries remain stored unless you delete your account.

Connected AI assistants: If you choose to connect a compatible AI assistant through VeraDial's read-only connector, the connector can return VeraDial account data needed to answer your request. Depending on the tool you ask the assistant to use, this may include call, AI-call, voicemail, and SMS phone numbers, statuses, durations, timestamps, screening summaries, call and voicemail transcripts, SMS message bodies and attachment media types, phone-line and receptionist settings, subscription and usage information, and contact summaries. Your basic profile (email address and name) may also be processed during the OAuth sign-in and authorization flow. The connector does not return call or voicemail audio, recording URLs, attachment URLs, passwords, authentication tokens, or internal telecom and AI-provider identifiers, and its published tools cannot place calls, send messages, or change your VeraDial account.

In-app account assistant: When you use Ask Vera in the mobile app or web dashboard, we store your questions, Vera's replies, the detected question category, whether the question was answered, the turn outcome, which fixed account-information tools were used, and a low-cardinality client surface (web, iOS, Android, or unknown). If you tap feedback, we also store a thumbs up or down on a reply plus an optional reason you pick from a fixed list. There is no free-text feedback box. Your latest question and a bounded set of your recent questions are sent to Google Gemini only to select a permitted intent, help entry, and at most one read-only account tool. VeraDial runs that selected tool and formats any account facts itself; your phone-line, routing, receptionist, carrier-forwarding, push-registration, subscription, and usage facts are not sent back to Gemini. The assistant does not receive your device contacts, call or voicemail transcripts, SMS bodies, voicemail content, or authentication credentials, and it cannot draft or place outbound calls.

Custom training sources: If you add custom training material so your receptionist can answer questions about your business, we store what you provide and what we derive from it. For an uploaded document, the file is stored in private cloud storage (Supabase Storage) along with its file name, type, and size. For a web address, we store the address and fetch that page's public content through a third-party extraction service (Firecrawl). In both cases, the extracted document or page text is sent to Google's Gemini API, which distills it into a short set of facts a receptionist can use. We store that distilled summary, a label for the source, its processing status, and any failure reason. The distilled summary — not the original file or page — is what gets supplied to your receptionist as caller context during calls. Deleting a training source deletes the stored file and its distilled summary.

Customer file requests: If a business sends you a VeraDial secure-upload link, we collect the images you choose to upload, the displayed file name, declared and detected file type and size, upload and security-scan status, a cryptographic file fingerprint, and request/access/deletion audit events. New files are private and quarantined. VeraDial validates and re-encodes accepted images to remove embedded metadata, and sends the original bytes over an authenticated connection to VeraDial's dedicated ClamAV malware scanner running in Google Cloud before the business can access them. File contents remain inside VeraDial's Google Cloud environment and are not sent to ClamAV, Cisco Talos, or another malware-scanning provider; the scanner downloads only malware-signature updates from ClamAV. The business can see the sanitized accepted image and its displayed name; automation webhooks receive only opaque request and file identifiers, never the image, file name, storage path, access token, or download URL. Do not upload information the requesting business does not need.

Connected automation endpoints: If you connect an automation tool (such as Zapier, Make, or n8n) or register your own webhook endpoint, we store the destination URL, a signing secret used to authenticate our deliveries, which event types you subscribed to, whether you enabled full content, and per-delivery attempt records including status codes and timestamps. When a subscribed event occurs, we deliver it to the endpoint you configured. Events cover completed call screening, received voicemails, AI SMS replies that were sent, booked appointments, and contact details submitted through website chat. The delivery includes the relevant caller or visitor details, the event's summary, and related identifiers and timestamps. Full call transcripts and voicemail transcriptions are removed from deliveries unless you explicitly turn on full content for that endpoint; a website-chat lead event contains the contact details the visitor explicitly submitted but not the chat transcript. Once data reaches an endpoint you configured, it is handled by that destination and by you, not by VeraDial; see Section 3.

Service emails: We send account and lifecycle email to your account email address through a third-party email provider (Resend) — for example, finishing setup, activation and first-call notices, trial reminders, and win-back messages. We store which of these emails were sent to you and when, your unsubscribe preference, and delivery outcomes reported back by the provider (such as delivered, bounced, or complained) so we can honor unsubscribes and stop mailing addresses that bounce or report our mail as spam. You can unsubscribe from lifecycle email using the link in any such message; this does not stop transactional messages required to operate your account.

Website chat: A business using VeraDial can add Vera's text-chat widget to its own website. When a visitor uses that widget, we store the visitor's messages, Vera's replies, the website origin, conversation status, and timestamps in the business's VeraDial account. If the visitor chooses to provide a name, email address, phone number, or follow-up note, we store those details with the conversation and show them to that business. The conversation and the business's receptionist profile, hours, booking link, and distilled custom-training facts are sent to Google's Gemini API to draft replies. The widget identifies itself as an AI assistant before the first message. It cannot complete a purchase, refund, booking, or other binding transaction; when a request needs a person, it asks for contact details so the business can follow up. A visitor can use the chat without creating a VeraDial account. The business that installed the widget decides why it uses the chat and is responsible for its own website notices and handling of the visitor information it receives.

Support chat: Our signed-in account dashboard and mobile app include a support messenger provided by Intercom. When the messenger loads, Intercom receives standard technical data the browser or device sends (such as IP address, browser or device type, and the screen or page where it is loaded) and may set cookies or local identifiers. If you chat, your messages are processed and stored by Intercom. We send Intercom your VeraDial account identifier and account email inside a signed, short-lived token so the conversation is attached to your account. Intercom's Fin AI Agent may automatically generate and deliver support answers using the VeraDial help material and behaviour guidance we provide; the messenger identifies the responder as AI. Fin cannot complete a refund, charge, cancellation, number transfer, account deletion, or other binding account action through chat, and the automated support channel does not guarantee a human handoff. When it cannot safely complete a request, it provides the available self-service next step or explains the limitation. We use these conversations to provide support, understand why customers leave, resolve disputes, investigate misuse, and improve VeraDial. The public VeraDial marketing website uses the VeraDial website-chat system described above rather than Intercom.

Bot protection: Our public demo builder and web signup pages use Cloudflare Turnstile to distinguish real visitors from automated abuse. When you complete the check, the challenge token and your IP address are sent to Cloudflare for verification. We store only the verification outcome, not the token.

Network and device information (fraud prevention): When you sign in and use VeraDial, our servers record the IP address your requests come from, together with your app's user-agent string and, where the app provides one, a random per-install device identifier (not a hardware or advertising identifier). We keep the times each address or identifier was first and last seen on your account. During mobile account creation, VeraDial may also ask Apple App Attest and DeviceCheck on iOS, or Google Play Integrity on Android, to confirm that the request came from a recognized VeraDial app on a qualifying device. VeraDial sends a one-time cryptographic challenge or its hash for this check; Apple or Google returns app/device-integrity signals, and Apple DeviceCheck also lets VeraDial read and update two fraud-prevention bits associated with the iOS device. These services do not give VeraDial a hardware or advertising identifier. VeraDial does not store the temporary DeviceCheck token or Play Integrity token in its database.

The network and device observations VeraDial stores are used to protect the service — detecting fraud, trial abuse, and coordinated misuse by recognizing when multiple accounts operate from the same network or device — and to respond to carrier, provider, and lawful requests. The random per-install identifier is also used for mobile product analytics and operator-device exclusion as described under “Product analytics” below. When signed out, the app may ask VeraDial whether that identifier has a previous live association with a designated VeraDial operator account; the app receives only a Boolean answer, not account or network information. The identifier is not used for advertising or sold. If you delete your account, these records are detached from the account — the link to the account is removed — while the network and device observations themselves are retained for fraud and abuse prevention. Apple's DeviceCheck bits are maintained through Apple and may remain associated with the device for fraud prevention after account deletion. See “Fraud-prevention records that outlast deletion” in Section 5.

When a previously banned account attempts to refresh its session and a new account is then created from the same IP address within a short period, VeraDial may place the new account under review to prevent ban evasion and provider charges. For this check, VeraDial stores only the event types and times, the new account's internal identifier, and keyed one-way fingerprints used to compare the IP address and deduplicate the events. VeraDial does not copy the raw IP address, email address, username, or full authentication-log entry into this detector's database. These detector records are retained as ban-evasion and repeat-account evidence. A match is used for a reversible service-protection hold and review; it does not by itself automatically suspend or ban the new account.

Device and forwarding support diagnostics: To troubleshoot app, notification, incoming-call, and call-forwarding problems, the mobile app reports a bounded support snapshot using the same random per-install identifier described above; VeraDial does not create a second device identifier. The snapshot may include the device manufacturer, model and general type, operating system and version, VeraDial app version and build, update runtime version, whether “Receive calls on this device” is enabled, the last reported Twilio Voice registration outcome and time, a fixed recovery reason (skipped, registration failed, or microphone denied), and the time an Expo push token was last registered for that install. These are client-reported timestamps and outcomes, not continuous monitoring or proof that a device is currently reachable.

To answer “why didn't my phone ring” for a specific call, the app additionally records a bounded per-call delivery event when an incoming-call push reaches your device: that the call invite arrived, whether the operating system allowed or declined presenting the call, a fixed reason code (for example Do-Not-Disturb or blocked-caller filtering on iOS, or a disabled notification permission or channel on Android), the call identifier VeraDial already stores with your call history, the event time, and — on Android — the notification permission, incoming-call channel importance, full-screen permission, and background-restriction state at that moment. These events contain no call audio, transcript, or caller content; an “allowed” event means the operating system accepted the call presentation, not proof the ring was heard or seen. They are used only to operate and troubleshoot your account, are deleted no later than 90 days after collection, and delete with your account.

When you ask VeraDial to detect the carrier for a number you are forwarding, Twilio Lookup may return the operating carrier name, line type, and country, or an error code when that information is unavailable. VeraDial stores that result and time alongside the carrier you selected and the existing forwarding-test evidence. A detected network and a selected carrier are kept as separate facts because an MVNO may resolve to its host network. VeraDial does not run bulk carrier lookups for support. These support records are used only to operate and troubleshoot your account; they are not used for advertising or cross-account profiling.

Google Calendar booking: If you connect Google Calendar, VeraDial creates a separate “VeraDial Bookings” calendar in your Google account and stores an encrypted Google refresh token, the Google account email address and account identifier you connected, and the identifier of that Bookings calendar. Calendar identifiers are assigned by Google and can resemble email addresses. To find open times, VeraDial requests only free/busy time ranges, and only from your main Google calendar and that Bookings calendar — events on your other Google calendars are not consulted and do not block a booking. VeraDial cannot read event titles, descriptions, attendees, or contents from any calendar it did not create, and it cannot modify your other calendars. The candidate appointment times Vera offers are processed by the AI provider handling that call so they can be spoken to the caller; your event contents are never accessible to VeraDial and are never sent. When Vera confirms an appointment, we write the event to the Bookings calendar and store the appointment time, timezone, caller name, callback number, and stated reason in your account. Calendar data is not sold, is not shared with advertisers, and is not used to train AI models. Disconnecting revokes VeraDial's access and stops new bookings; it leaves the Bookings calendar and your existing appointment records in place. Deleting your account revokes access and removes VeraDial's calendar records.

Appointment requests: If you turn on appointment requests for a phone line, Vera collects the caller's service address, what work they need, a callback number, their name if given, and any day or time they say they prefer, and stores that request in your account so you can schedule it. The service address is a location the caller gives us on the call — it is stored with the request and shown to you in the app. Vera does not schedule the appointment, does not select a time, and does not write anything to any calendar. When you later choose a time and ask Vera to confirm it, we store the time you entered and place an outbound AI call to the callback number, which is handled the same way as other AI Calls described above. Appointment requests are not sold, are not shared with advertisers, and are not used to train AI models. The address and other request details are excluded from product analytics. Deleting your account deletes your appointment requests.

Push notification tokens: We store device push tokens to deliver notifications to your device. Tokens are automatically deleted when you sign out or your session expires.

Billing: Purchase and subscription history is managed through RevenueCat and the Apple App Store / Google Play Store. We store your subscription status, billing period, and credit balance. We do not store payment card details directly. On Android, RevenueCat also receives the device's advertising identifier and a Meta-generated anonymous app identifier so subscription events can be attributed to advertising. On iOS, RevenueCat receives an Apple AdServices attribution token and the Apple Search Ads campaign details Apple returns for it, so subscription events can be attributed to advertising; see “Apple Search Ads attribution (iOS)” below. We do not configure either attribution path to add your email address, phone number, message content, call audio, or transcripts.

Referral program: Each eligible VeraDial account can receive a personal referral code. If a new customer creates an account through a referral link, we store the code used, the referring and referred account identifiers, the signup platform, the version of the program terms that applied, the signup date, and — if the referred customer later makes an eligible subscription payment — the first paid date, the end of the earning window, and the related RevenueCat event and transaction identifiers. This information is used to attribute the account, prevent self-referrals and fraud, review program eligibility, and administer earnings and payouts. A referring customer can see only anonymous referral status and dates in VeraDial; we do not reveal the referred customer's name, contact details, plan, payment amount, or account activity through the referral dashboard. Referral codes are kept separate from product analytics and are not sent to PostHog in captured page addresses.

Error and crash data: We collect error reports and crash data through Sentry to diagnose and fix issues with the app. This may include device information, OS version, and stack traces. No message content or call audio is included in error reports.

Signup platform: When your VeraDial account profile is first created, we store whether that signup completed on the web, iOS, or Android. We use this account-level field to measure acquisition and signup performance; it is not used to authorize access, admit an account, or decide that an account is abusive. Older accounts for which the original signup surface cannot be established remain marked as unknown rather than being inferred from a device used later.

Product analytics: We collect product analytics through PostHog to understand how the app and website are used (screen views, navigation paths, feature engagement, paywall and purchase events, website page views, demo funnel events, and app store click events). If you choose to answer the optional fixed-choice question shown when leaving a paywall or checkout, the reason you select is included in this product analytics and linked to the same account journey so we can compare it with later trial or subscription outcomes; there is no free-text field. Sensitive event properties (email, phone numbers, message content, transcripts, recording URLs, precise location coordinates, goals/notes/prompts) are stripped before analytics events are sent. Those event-property filters do not inspect the pixels or structural nodes in a session replay; the separate replay scope and masking rules below govern visual capture. We estimate approximate location (country, region, and city) from the network (IP) address an event arrives from; PostHog is configured to discard the IP address itself after this step, so raw IPs are not stored with analytics events. Mobile analytics events include the same random per-install identifier described under “Network and device information” above. This identifier lets us connect anonymous and signed-in activity from the same installation across account changes, distinguish device-level journeys, exclude VeraDial operator devices from customer measurements, and diagnose setup and replay behaviour. The app also sends a Boolean flag after an installation has been used with a designated VeraDial operator account so that installation remains excluded when accounts change. Neither value is a hardware or advertising identifier, both reset when the app is reinstalled or its storage is cleared, and we do not use them for advertising. When a website demo proceeds to signup, VeraDial may carry a random per-session demo journey identifier, the first VeraDial page path visited, and its page category to app.veradial.com and store that context with the account's first-touch attribution. This lets us connect the anonymous demo steps to signup, checkout, and subscription outcomes without putting contact or conversation data in the identifier. This handoff is disabled when the browser sends Do Not Track or Global Privacy Control. When Global Privacy Control is active on our app website (app.veradial.com), we do not initialize PostHog or send PostHog analytics or session-replay data from that site. On the app website, the signup and checkout pages collect page views — including the page address, referring page, marketing campaign parameters, and that anonymous demo-journey context, with tokens and other secrets removed from captured addresses — and may use masked session replay to diagnose signup and checkout problems; anything you type is masked, payment card fields are handled inside our payment processor's own frame and are never visible to the recording, and replay respects Do Not Track / Global Privacy Control. Outside those signup and checkout pages, analytics events do not include raw page URLs with query strings. On /demo and /demo/live only, we may use masked website session replay through PostHog to diagnose demo-funnel issues; all text and input values are masked, replay respects Do Not Track / Global Privacy Control, and internal traffic is excluded where flagged. In the mobile apps, we may use session replay throughout the app to understand navigation, feature use, errors, reliability, support problems, and customer funnels. On iOS, text entered into input fields and all images are masked on the device before anything is sent, while other static on-screen text can appear in a replay, including account, line, and settings details; phone and contact information; and content displayed in call, voicemail, transcript, message, assistant, or support surfaces. On Android, replay uses screenshots of the app: text entered into input fields and bitmap-backed image content are covered or omitted on the device before anything is sent, while other static on-screen text can appear in a replay, including account, line, and settings details; phone and contact information; and content displayed in call, voicemail, transcript, message, assistant, or support surfaces. Android also discards a screenshot when it cannot verify that the masks stayed aligned with the captured pixels. Passwords, one-time codes, payment fields, authentication/session/recovery/API tokens, encryption keys, and provider secrets are not intentionally captured. Replay does not include application logs, network requests or responses, call audio, or microphone audio. Access to replay is limited to authorized VeraDial operators and service providers for the purposes described here. Session replay is not used on website pages other than the demo pages and the app signup/checkout flow. Analytics are disabled in development builds and screenshot/test builds by default.

Google Analytics measurement: On our websites (veradial.com and veradial.ca), we use Google Analytics 4 to measure site traffic and marketing performance, including page views, demo funnel events, and app store click events, together with standard browser and device data. Google Analytics estimates approximate location (such as country, region, and city) from your IP address during collection; Google Analytics 4 does not log or store the IP address itself. In the Android app, Google Analytics for Firebase automatically assigns an app-instance identifier and collects app lifecycle, session, engagement, Android advertising identifier, masked-IP-derived approximate location, and standard app/device data. It may also automatically observe Google Play purchase and subscription events. VeraDial sends two additional Android events: signup method (email, Google, or Apple) and activation mode (direct use or call forwarding). We use this information for analytics and Google Ads conversion measurement. Personalized-ad signals and automatic screen reporting are disabled by default. We do not set a Firebase Analytics user ID or send Google Analytics your name, email address, phone number, Supabase user ID, contacts, messages, calls, audio, transcripts, recordings, business profile, website, goals, notes, or prompts. This mobile measurement is not used in the iOS app.

Advertising and conversion measurement: On our websites (veradial.com and veradial.ca) and our web signup and checkout pages (app.veradial.com), we use the Meta (Facebook) Pixel to measure how our advertising performs and to build and optimize ad audiences. The pixel records page views and a registration-completed event when you create an account, together with standard technical data your browser sends (IP address, user-agent, the page URL, and Meta cookie identifiers). Unless your browser sends Do Not Track or Global Privacy Control, VeraDial may store the first set of marketing campaign parameters and advertising click identifiers in browser storage and carry them across our website and signup domains so later signup, trial, and subscription outcomes can be attributed to that first visit. In the Android app, the Meta App Events SDK records first launch/app activation and registration completion, and RevenueCat may send subscription lifecycle events (including trial starts, purchases, conversions, and renewals) to Meta for advertising measurement. Android measurement uses the device advertising identifier, a Meta-generated anonymous app identifier, IP address, and standard device/network data. Automatic client-side purchase logging is disabled so RevenueCat is the only source of subscription revenue events. This integration is not used in the iOS app, and we do not configure it to add your email address, phone number, message content, call audio, transcripts, contacts, or goals/notes. You can limit or reset your Android advertising identifier through device privacy settings and control ad personalization through your Meta account settings.

Google Ads click-to-trial measurement (web): If you arrive at veradial.com or veradial.ca from a Google advertisement, Google may add a click identifier (gclid, gbraid, or wbraid) and campaign parameters to the landing-page address. Unless your browser sends Do Not Track or Global Privacy Control, VeraDial stores the first set of those advertising parameters in browser storage, including a first-party cookie on veradial.ca when needed to carry them to veradial.com, carries them to app.veradial.com when you choose to sign up, and stores them with your profile. If RevenueCat later confirms that VeraDial accepted a production trial for that account, VeraDial sends Google the original Google click identifier, the time the trial started, and the RevenueCat transaction identifier through Google's Data Manager API. This lets us measure which ads lead to real trials and deduplicate retries. We do not send Google your name, email address, phone number, VeraDial account identifier, payment-card details, contacts, messages, call audio, transcripts, recordings, business profile, website, goals, notes, or prompts through this path. Sandbox purchases, suspended accounts, and signups without a Google click identifier are not sent.

Apple Search Ads attribution (iOS): If you install or redownload VeraDial after tapping an Apple Search Ads advertisement in the App Store, Apple's AdServices framework provides the app with a short-lived attribution token once purchases are set up. VeraDial passes that token to RevenueCat, which exchanges it with Apple for standard attribution details — whether the install was ad-attributed, and the campaign, ad group, keyword, ad, conversion type, claim type, and country or region Apple reports — so we can measure which advertising leads to trials and paid subscriptions. This uses Apple's Standard attribution data, which does not require the App Tracking Transparency prompt: VeraDial does not ask for tracking permission, does not collect the Advertising Identifier (IDFA) for this purpose, and does not link the Meta advertising SDK into the iOS app. This path does not add your email address, phone number, contacts, message content, call audio, transcripts, or goals/notes. You can limit Apple's ad personalization and attribution in iOS Settings under Privacy & Security.

Demo callers (/demo and /demo/live): When you call our public demo line to try the AI receptionist, we store the normalized caller phone number with the demo inquiry for prospect follow-up, demo analytics, fraud prevention, and conversion attribution. We also store the source IP address associated with a demo-builder or live-demo request, the generated business profile, website address if supplied, the demo channel, timestamps, and related call identifiers. The four-digit demo code expires and is retired, but expiration does not delete the inquiry record. This applies only to public and in-app demo sessions — calls to your own VeraDial number(s) are covered by the call sections above.

Demo transcripts and post-call summary: During a live demo, we store the conversation transcript so we can review demo quality, diagnose failures, improve the receptionist, follow up on inquiries, and investigate misuse. The transcript contains what the caller and receptionist said, including any personal information the caller chooses to say. It is also sent to Google's Gemini API to produce a short “here's what Vera captured” summary (outcome, caller name, request, timing). Raw phone numbers, email addresses, and contact digits are automatically removed from the stored summary, but the retained transcript remains a complete record of the conversation. The transcript, summary, and demo inquiry record are retained as internal operational and business inquiry records.

Optional demo recap text: If Vera offers to text a one-time recap after an in-app demo, she names only the last four digits of the phone you just verified and waits for a separate, clear verbal yes. Declining does not affect the demo, signup, or service. A clear yes sends the recap immediately; no SMS reply is required. The text is generated from the same short summary shown in the app and contains the request, preferred timing (if captured), and next step; it is not marketing. The full destination is held only inside a short-lived encrypted capability and is decrypted by our server when sending through Twilio. Our database retains a keyed phone hash, last four digits, the consent question and time, a fingerprint of the message rather than its body, and delivery status; it does not retain the full destination or text body in the demo-recap record. Reply STOP to opt out or HELP for help.

For a dial-in website demo, we may attach a separate random analytics identifier to the demo inquiry so a server-confirmed conversation can be joined to the earlier website journey. That identifier contains no contact or conversation content, is retained with the inquiry, and is omitted when Do Not Track or Global Privacy Control is active.

We share data with the following third-party services as necessary to provide VeraDial's features. Each service processes only the data required for its specific function. We require service providers that process personal data for VeraDial to protect that data under privacy and security obligations that provide the same or equal protection required by this Privacy Policy.

Twilio: Voice calls, SMS delivery, phone number provisioning, number-porting eligibility checks and transfers, call recording, voicemail recording, phone-number carrier Lookup when you request carrier detection for forwarding, toll-free verification, and A2P 10DLC business identity, Brand, Campaign, and sender registration. Twilio processes call audio and message content. When you request number porting, Twilio also processes the number, current-carrier account and service-address information, authorized-representative details, supporting document, Letter of Authorization, transfer instructions, and provider status needed to administer the port. When you request carrier registration, Twilio processes the business identity, messaging use case, public consent evidence, and verification information required for that registration. Twilio Privacy Policy

Supabase: Authentication, database hosting (US-West-2 region), and private file storage for voicemail greeting audio, custom training uploads, message media, and customer file requests. Supabase Privacy Policy

Google Cloud: Hosting for VeraDial's API and its dedicated ClamAV malware scanner. For a customer file request, the original quarantined image is sent over an authenticated connection from VeraDial's API to that scanner for an allow-or-reject verdict. The scanner does not retain the image after the request finishes and does not send its contents to ClamAV or Cisco Talos. Google Cloud Privacy Notice

RevenueCat: In-app and web purchase management, subscription tracking, and any one-time or recurring carrier-registration fee offered by VeraDial. RevenueCat returns transaction identifiers and purchase metadata that VeraDial uses to authorize only the matching registration action. On Android, RevenueCat also processes advertising identifiers and sends selected subscription lifecycle events to Meta for advertising attribution and measurement. On iOS, RevenueCat processes the Apple AdServices attribution token and exchanges it with Apple for the standard Apple Search Ads campaign details described in Section 1, so ad-attributed installs can be measured against subscription outcomes. RevenueCat Privacy Policy

Intercom: Signed-in customer support messaging and AI-generated support answers in our account dashboard and mobile app. Intercom processes your support messages through its Fin AI Agent using the support content and guidance VeraDial configures, together with your account identifier and email when you are signed in and the technical and cookie data described in Section 1. Intercom hosts this data in the United States. Deleting your VeraDial account ends your access to the signed-in messenger but does not delete your Intercom contact or support conversation history. VeraDial retains that full history for the purposes described above unless you ask us to delete it. You can request access to or deletion of this information by emailing privacy@veradial.com. Intercom Privacy Policy

ElevenLabs: AI voice processing for AI Call, ElevenLabs-backed Call Screening, and Voicemail Greetings. For AI calls and ElevenLabs screening, call audio and your instructions or screening prompts are processed to generate the AI agent's responses. For voicemail greetings, your greeting text is converted to speech audio. ElevenLabs Privacy Policy

Cartesia: Voice cloning and cloned voice text-to-speech for voicemail greetings. When you create a cloned voice, your recorded sample is sent to Cartesia to create the voice model. When you generate a greeting with that clone, your greeting text and selected voice identifier are sent to Cartesia to generate audio. Cartesia Privacy Policy

OpenAI: AI voice processing for AI Call, Call Screening when selected through LiveKit screening, and real-time Call Translation. When OpenAI is selected as the AI provider, call audio and your instructions or screening prompts are processed in real-time by OpenAI's Realtime API to generate the AI agent's responses. When you enable call translation, both parties' call audio is processed in real-time by OpenAI to generate the translated speech. OpenAI Privacy Policy

Connected AI assistant providers (including OpenAI/ChatGPT and Anthropic/Claude): When you explicitly connect and authorize an AI assistant, VeraDial sends only the account data returned by the read-only tool you ask that assistant to use. The assistant provider receives that data over an encrypted connection and may retain or use it under its own privacy policy, retention settings, and account controls. Disconnecting VeraDial in the assistant stops that assistant from making future connector requests, but it may not delete data the provider already retained; use the provider's controls for those copies. OpenAI Privacy Policy · Anthropic Privacy Policy

Google (Gemini): AI processing, including for AI Call, LiveKit-routed Call Screening when Gemini is selected, Contact Memory, the AI SMS receptionist, website chat, custom training sources, the in-app account assistant, the demo receptionist builder, the demo post-call summary, and screening-quality evaluation. For the AI SMS receptionist, the inbound message text, recent conversation history, any attached MMS media, and your line's receptionist instructions are sent to Gemini to draft a reply. For website chat, the visitor's messages and recent chat history, together with the business's receptionist profile, hours, booking link, and distilled custom-training facts, are sent to Gemini to draft a reply. Contact details submitted through the separate follow-up form are not added to the model prompt. For custom training sources, the text extracted from the document or web page you provide is sent to Gemini to produce the distilled summary. For AI calls and screening, call audio and your instructions or screening prompts are processed in real-time by Google's Gemini API to generate the AI agent's responses. For Contact Memory, text from your call transcripts, voicemail transcriptions, AI call summaries, and SMS messages is sent to Google's Gemini API to generate per-contact summaries. When you use the in-app account assistant, your latest question and a bounded set of your recent questions are sent to Gemini only to select a permitted intent, help entry, and at most one read-only account tool. Account facts returned by that tool are formatted inside VeraDial and are not sent to Gemini; this assistant does not create proposed call drafts. For the demo builder, the business details we extract are sent to Gemini to draft your demo receptionist's profile. For the demo post-call summary, the demo call transcript is sent to Gemini to produce a short summary of what the receptionist captured (with raw phone numbers and contact digits removed before storage). For screening-quality evaluation, stored screening transcripts may be sent to Gemini to rate conversation quality (relevance, task completion, coherence, safety). Only the transcript already retained on your account is processed, and the ratings are used internally. Google receives this content only when the corresponding feature is used. Google Privacy Policy

xAI (Grok): AI voice processing for AI Call and, when selected through LiveKit screening, Call Screening. When xAI is selected as the AI provider, call audio and your instructions or screening prompts are processed by xAI's Grok API to generate the AI agent's responses. xAI Privacy Policy

LiveKit: Real-time audio routing and SIP connectivity for AI calls and LiveKit-backed call screening, plus real-time browser audio routing when you start an assistant preview. When LiveKit transport is used, call or preview audio is routed through LiveKit's infrastructure to connect you or the phone call with the AI agent. LiveKit processes audio in transit but does not store it. LiveKit Privacy Policy

Google Calendar: Appointment booking during call screening, if you choose to connect it. VeraDial requests free/busy time ranges from your main Google calendar and from the separate “VeraDial Bookings” calendar it creates in your Google account, and creates and manages events only on that Bookings calendar. The authorization VeraDial requests does not permit reading event titles, descriptions, or attendees on your other calendars, or modifying those calendars. You can revoke access at any time from within VeraDial or from your Google Account security settings. Google Privacy Policy

Google Maps: The Call Map feature uses Google Maps to display your call locations. When you use Call Map, Google receives map tile requests and your viewport region. Google Maps is subject to Google's Privacy Policy.

Google Ads / Data Manager API: Advertising attribution and conversion measurement for web signups that originated from a Google ad. For an accepted production trial, Google receives the original Google click identifier, the trial time, and a RevenueCat transaction identifier, as described in Section 1. This path does not include your VeraDial account identifier or the personal and conversation data listed there. Google Privacy Policy

Google Analytics / Firebase: Website traffic and marketing measurement for veradial.com and veradial.ca, plus Android app acquisition and activation measurement. Google processes website page views and events, Android app-instance and advertising identifiers, lifecycle/session/engagement data, standard browser/app/device data, masked-IP-derived approximate location, and possible Google Play purchase/subscription events. VeraDial also sends signup method and activation mode from Android. We do not configure a Firebase Analytics user ID or send account identity, contact, message, call, audio, transcript, recording, business-profile, website, goal, note, or prompt data. Google Analytics for Firebase is not linked into the iOS app. Google Privacy Policy

Deepgram: Speech-to-text transcription for recorded calls, voicemails, and message dictation. When you record a call, when a caller leaves a voicemail on your VeraDial number, or when you use the in-app microphone button to dictate a message, the audio is sent to Deepgram for automatic transcription. Dictation clips are processed to produce the text and are not stored by VeraDial. Deepgram Privacy Policy

Sentry: Error tracking and crash reporting. We send error reports and diagnostic data to Sentry to identify and fix technical issues. Sentry does not receive message content or call audio. Sentry Privacy Policy

PostHog: Product analytics for the app and website. We send event data (screen views, feature usage, paywall and purchase events, website page views, demo funnel events, and app store click events) to PostHog to understand how VeraDial is used and improve the product. Mobile events also include a random per-install identifier and an operator-device Boolean for the device-level measurement and exclusion purposes described in Section 1; neither is a hardware or advertising identifier. Sensitive event properties are stripped before analytics events are sent. Approximate location (country, region, and city) is estimated from the network (IP) address an event arrives from, and PostHog is configured to discard the IP address itself after that step. Session replay covers /demo and /demo/live on the website, the signup and checkout pages on app.veradial.com, and the full iOS and Android apps; it is not used on other website pages. Website replay masks the fields described above. In the iOS app, input text and images are masked while other static on-screen text may be visible, including the account, line, contact, communications, assistant, support, and settings content described in Section 1. In the Android app, screenshot masks cover all displayed text, input values, and bitmap-backed image content before upload; screenshots whose mask alignment cannot be verified are discarded. PostHog does not receive call or microphone audio, application logs, network requests or responses, authentication secrets, one-time codes, payment credentials, encryption keys, provider secrets, or unmasked form input values through replay. Captured page addresses on the signup and checkout pages keep marketing campaign parameters and the anonymous demo-journey context described above, with tokens and other secrets removed, and analytics events elsewhere strip raw website URLs with query strings. PostHog Privacy Policy

Expo: Push notification delivery. Device push tokens are sent through Expo's push notification service, which routes them to Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) for delivery to your device. Expo Privacy Policy

Vercel: Website hosting and analytics. We use Vercel Analytics and Speed Insights to understand website performance. These tools collect anonymous usage data and do not use cookies for tracking. Vercel Privacy Policy

Meta (Facebook): Advertising and conversion measurement on our website, web signup flow, and Android app. We use the Meta Pixel for website page views and registrations; the Android Meta App Events SDK for first launch/app activation and registration completion; and RevenueCat's Meta integration for selected subscription lifecycle events. Meta receives these events with relevant browser or Android advertising identifiers, IP address, and standard device/network data. The integration is not used in the iOS app, and we do not configure it to add your email address, phone number, message content, call audio, transcripts, contacts, or goals/notes. Meta Privacy Policy

Firecrawl: Website content extraction for the demo receptionist builder and for custom training sources you add by web address. Firecrawl fetches the public web page and returns extracted text and metadata, so the demo can be tailored to your business or the page can be distilled into receptionist facts. Firecrawl receives the URL you submit and the page content it extracts. Firecrawl Privacy Policy

Resend: Delivery of account and lifecycle email, plus receipt and reply delivery for the optional AI email receptionist. Resend receives the relevant email addresses and message content and returns delivery outcomes (such as delivered, bounced, or complained) that we use to operate the service, honor unsubscribes, and stop mailing bad addresses. Resend Privacy Policy

Cloudflare: Bot protection on our public demo builder and web signup pages through Cloudflare Turnstile. Cloudflare receives the challenge token and your IP address to verify the request is not automated. Cloudflare Privacy Policy

Automation endpoints you connect (such as Zapier, Make, or n8n): If you connect an automation tool or register your own webhook endpoint, VeraDial delivers the receptionist events you subscribed to — including the caller's number and name, event summaries, and, only if you turn on full content for that endpoint, transcripts and voicemail transcriptions. These destinations are chosen and controlled by you, not by VeraDial: once an event is delivered, the receiving service handles that data under its own terms and privacy policy and under any onward automations you build. Removing the endpoint in VeraDial stops future deliveries but does not delete data the destination already received. Zapier Privacy Policy

Apple / Google: App distribution and payment processing via the App Store and Google Play Store. During mobile account creation, Apple App Attest and DeviceCheck or Google Play Integrity may also process a one-time cryptographic challenge and return the app/device-integrity signals described in Section 1 for fraud prevention. If you install VeraDial from an Apple Search Ads advertisement, Apple additionally provides standard ad attribution details for that install through its AdServices framework, which we receive through RevenueCat. Apple Privacy Policy · Google Privacy Policy

VeraDial sends push notifications for incoming messages, new voicemails, missed calls, AI call completions, website-chat follow-up requests, and low credit balance alerts.

For your privacy, notifications display only the sender or caller number — no message content, voicemail transcriptions, or AI summaries appear on your lock screen.

You can disable notifications at any time through your device's system settings. Push tokens are stored on our server and are automatically deleted when you sign out or your session expires.

We use industry-standard measures to protect your data, including encryption in transit (TLS/HTTPS), authenticated API access, and secure credential storage. Authentication tokens are validated using public-key cryptography (ES256 via JWKS).

While we take reasonable steps to protect your information, no method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security.

Your data is stored and processed in the United States (US-West-2 region, Oregon). If you are located outside the United States, your data will be transferred to and processed in the United States. By using VeraDial, you consent to this transfer.

Our third-party service providers may process data in their own data centers, which may be located in different regions. See Section 3 for details on each provider.

California residents (CCPA): You have the right to know what data we collect, request deletion, and opt out of the sale or sharing of personal information for cross-context behavioral advertising. We do not sell your personal data. Our use of Meta for audience optimization and Google Ads for conversion measurement may be considered sharing under California law; you can limit it through Do Not Track / Global Privacy Control, your browser or device settings, and your Meta or Google ad settings, or contact us to exercise your rights.

Canadian residents (PIPEDA): You have the right to access your personal information held by VeraDial, challenge its accuracy, and withdraw consent for its collection, use, or disclosure. We collect and use personal information only for purposes that a reasonable person would consider appropriate.

EU/EEA residents (GDPR): You have the right to access, rectify, erase, and port your data.

To exercise your rights, email support@veradial.com.