privacy policy

updated October 11, 2026

This policy covers vocavi at vocavi.org, our phone-calling service, and our connected tools, including the vocavi plugin in ChatGPT. Contact support@vocavi.org with privacy questions or requests.

What we collect and why

Account and sign-in information. We store your email, account identifier, and information supplied by your sign-in provider, such as your name and profile image. We store sign-in sessions, authorization grants and tokens, and a password hash for accounts that use password sign-in. This lets us identify you, protect your account, and authorize the clients you connect. Security records can include IP addresses, browser information, and request times.
Call requests and history. We store the destination number, business and task details you or your agent provide, scheduling information, answers you give during a call, call status, timing and charges, outcomes, text transcripts, and recording references. If you join a call or receive a callback, we also process your phone number and your part of the conversation. We use this information to make and manage the requested calls, return results, maintain your history, resolve problems, and prevent abuse.
Saved calling profile. If you choose to save details, we store fields such as your name, date of birth, phone number, address, and vehicle details so they can be reused for relevant calls. Some integrations outside the ChatGPT plugin also support health or dental insurance fields. Saving a profile is separate from giving details for one call; you can remove saved fields.
Payments. We store your balance, purchases, charges, and payment-provider references for billing and reconciliation. Stripe handles card payments; vocavi does not receive your full card number or security code.
Support and email. We process the messages and contact details you send us to answer requests, plus delivery and subscription records for account emails and newsletters. Blog comments store the name, email, comment, IP address and posting time; your name and comment are public, but your email is not displayed. Blog likes use a browser identifier.
Website information. Our hosting provider processes IP addresses, browser information and request logs to serve the site and keep it secure.

Data used by the ChatGPT plugin

Connecting the plugin links it to your vocavi account. We receive the inputs sent with a tool request, not your entire ChatGPT conversation. These inputs can include the business to call, the task, necessary contact or booking details, and answers you authorize your agent to pass along.

The tools return information to your connected client, including the requested call status, outcome, transcript, recording links, saved profile fields, or balance. Your client processes those results under its own privacy settings and policy. Only send information needed for the task and information you have permission to share about another person.

The ChatGPT plugin excludes medical and dental appointment categories and health-insurance profile fields. Do not send protected health information, government identifiers, payment-card details, passwords, API keys, or one-time authentication codes in call briefs, profiles, or tool inputs. Sign in through the dedicated authorization flow, not by putting credentials into a chat or call request.

Who receives information

The people and businesses you call receive the information shared during the conversation to carry out your task. They may keep their own records. Anyone you share a recording link with may be able to use it while it remains valid.
Cloudflare hosts our application, databases, call-session state, and operational logs. Telnyx carries calls and processes phone numbers, call metadata, and recorded audio.
OpenAI processes call instructions, relevant calling details, live audio, transcripts, and generated responses for the voice agent, its supporting reasoning, and call summaries. This API processing is separate from your use of ChatGPT as the connected client.
Raindrop, when monitoring is enabled, receives diagnostic information about voice sessions and summaries, including account and call identifiers, model activity, and conversation content. We enable its personal-information redaction and apply additional redaction to supported fields; this is not a guarantee that every personal detail is removed.
Stripe processes payments. Google handles Google sign-in. Cloudflare also delivers our email, processing message addresses and content to deliver account, support, and newsletter emails.
Your connected client receives tool results as described above. Our service providers may process information outside your country. Their separate retention and legal obligations can apply to information they receive.

Analytics and cookies

We do not use third-party analytics or advertising pixels. Our cookies keep you signed in and remember blog likes; none of them tracks you across other sites.

Text alerts

vocavi alerts is operated by Vocavi LLC. If you choose optional SMS alerts, we store your verified phone number, the consent wording you accepted, the time of your choice, and any later withdrawal. We use these records to manage call attention and phone number renewal notifications and honor your preferences.

Mobile information, SMS consent, and SMS subscription records are not sold or shared with third parties or affiliates for marketing or promotional purposes. They are shared only with service providers, including Telnyx and mobile carriers, as necessary to operate the messaging service, honor your preferences, or comply with legal requirements. SMS consent does not authorize advertising use of your phone number.

You can withdraw consent at text alert preferences or, once messages are available, by replying STOP. We retain consent and withdrawal records to document your choices and prevent unwanted messages. Contact support@vocavi.org for questions or deletion requests.

How long information is kept

Account records and text call history: there is currently no automatic age-based deletion. Account details, call briefs, transcripts, outcomes, schedules, and balance history remain stored until removed through an account or data-deletion request. Disconnecting a plugin or not using the service does not delete these records.
Saved profiles: fields remain until you remove them or request account deletion. Removing a profile field does not erase a copy already used in an earlier call or shared with a business.
Call recordings: Telnyx stores the audio. Its published recording policy currently states that recordings are stored for one year unless deleted earlier, and that this maximum may change. We do not guarantee availability for that whole period. An expiring download link is not deletion of the underlying audio. Contact us to request earlier removal of a recording.
Sign-in and authorization: our browser sessions are configured for up to 400 days and renew with active use. OAuth access tokens last seven days; refresh tokens can last ten years and rotate when used. Tokens can be revoked before expiry. These are access lifetimes, not promises to erase the associated account, authorization records, or call history when a token expires.
Our cookies: the blog reader cookie lasts up to 365 days and the blog database bookmark cookie up to ten minutes. Browsers may remove cookies earlier.
Blog, email, and support records: stored comments, subscription and delivery records, and support correspondence do not currently have a fixed automatic deletion period. Unsubscribing stops the relevant emails but keeps the subscription record, including its unsubscribed status, so we can honor that choice. Ask us about removing these records.
Provider logs and copies: providers may retain security logs, backups, payment records, and diagnostic data on their own schedules. For example, OpenAI's API data controls describe default abuse-monitoring retention of up to 30 days, with legal and safety exceptions and separate rules for stored application data. We do not promise immediate erasure of every provider copy when data is removed from vocavi. Contact us for help with provider-held data related to your account.

Your choices and deletion requests

View and correct: use my account or the connected tools to review your calls and available recordings. Your saved calling profile is on that page too, where you can edit or delete any field or the whole profile; connected tools can do the same with vocavi_get_profile and vocavi_save_profile (an empty string removes a field). Only save details you want reused.
Disconnect: remove the plugin or connection in your client's settings to stop using it there. Contact us if you also need help revoking access. Disconnecting, signing out, and deleting an account are different actions.
Email choices: use the unsubscribe link in the relevant newsletter or promotional email. This does not stop essential account or support messages, or automatically delete subscription records.
Browser controls: your browser can block or clear cookies. This can affect sign-in and preferences.
Access, deletion, and other privacy requests: email support@vocavi.org from the address associated with your account. Say whether the request concerns your account, particular calls or recordings, profile, comments, or newsletter. We may need to verify account ownership before acting. Account and call-history deletion is handled by support, not by a plugin tool.

Some records may need to be retained for applicable legal, payment, fraud-prevention, or dispute obligations; ask us about the reason and applicable period for your request. Deletion from vocavi does not recall information already shared with a business, exported by you, or stored in your connected client's conversation. Those recipients have their own controls.

We may update this policy as the service changes; the date above identifies this version. Privacy questions and requests always go to support@vocavi.org.

Help me review what vocavi stores about me (see https://vocavi.org/privacy).

If you don't have the vocavi tools (vocavi_*) yet, add the vocavi MCP server first and sign me in:
   - Claude Code:  claude mcp add --scope user --transport http vocavi https://vocavi.org/mcp  (then I run /mcp, pick vocavi, and choose authenticate)
   - Codex:        codex mcp add vocavi --url https://vocavi.org/mcp  then  codex mcp login vocavi
   - Claude Desktop, claude.ai, or ChatGPT: add a custom connector with the URL https://vocavi.org/mcp and sign in when it asks.
   - Muse: build a custom integration to the vocavi remote MCP server at https://vocavi.org/mcp (streamable HTTP) with the official MCP SDK. Ask me for my vocavi API key (it's at https://vocavi.org/account) through your secure credential flow, never in chat, store it in your Secure Credentials Store, and send it as Authorization: Bearer <key>. List the tools, test vocavi_get_balance, and save it as a reusable skill.
   - Grok Bot: add a custom MCP server called vocavi (remote HTTPS, no headers, no auth) at my personal server URL, which I copy from https://vocavi.org/account. You add it from this chat; no separate approval is needed. If you offer sign-in instead, use https://vocavi.org/mcp and I sign in.
   - grok.com: you can't add connectors from the chat, so I do it: grok.com/connectors, New Connector, Custom, with the URL https://vocavi.org/mcp, then I sign in.
   - If you can't sign me in, I copy my personal server URL from https://vocavi.org/account and you use that instead.
   I sign in with Google or an emailed link.

- My saved calling profile: vocavi_get_profile. To remove anything, vocavi_save_profile with that field set to an empty string; confirm with me first.
- My calls, each with the brief you sent, the outcome, and a transcript: vocavi_list_calls, then vocavi_get_call for any one.
- Deleting the whole account and its call history is done by email, as the privacy page says; there is no tool for it. Tell me that, and don't try to delete anything else on my behalf.