BotPhone
BotPhone MCP for Muse
Sign inSign up free
Back to BotPhone for Muse

BotPhone MCP · BotPhone for Muse

Privacy Policy

This policy explains how BotPhone handles information for BotPhone MCP, including BotPhone for Muse. It supplements the main BotPhone Privacy Policy for this product.

Effective September 20, 2026 · Last updated October 14, 2026

1. Scope and roles

BotPhone MCP is BotPhone's AI phone line used through a connected AI assistant, such as Muse, Grok Bot, ChatGPT or Dots, Claude, OpenClaw, Hermes, or another MCP client. BotPhone for Muse is BotPhone MCP used with Muse. Where this document mentions Muse, the same applies to whichever assistant you connect, except for items about Meta and WhatsApp, which apply only to Muse.

BotPhone operates voice agents that can answer inbound business calls, place approved outbound business calls, capture messages, and send configured conversation information to a connected AI assistant. The assistant exchanges approved context and outcomes with BotPhone but does not place or carry calls. This policy applies to that beta product.

The subscribing business decides why and how customer communications are handled. In many privacy-law contexts, that business is the controller or business, and BotPhone acts as its processor or service provider. The assistant you connect and its provider (for example Meta for Muse, xAI for Grok Bot, OpenAI for ChatGPT and Dots, or Anthropic for Claude) may process information under their own terms and privacy policies.

WhatsApp (coming soon). BotPhone for Muse does not currently support WhatsApp, and today we do not collect or process WhatsApp data. When WhatsApp support launches, we expect to handle WhatsApp Business account identifiers and permissions, sender phone numbers and profile names, message content and attachments, and delivery, read, and interaction status. We would use it only to respond to conversations, create summaries, and send them to your connected Muse account, and we would share it with Meta and WhatsApp as needed to operate the feature. It would be retained on the same schedule as transcripts and messages (see Retention and deletion). We will update this policy before that feature takes effect.

2. Information we collect

Business and account information

  • Business name, contact information, billing identifiers, and account identifiers
  • Business hours, services, frequently asked questions, routing rules, and receptionist instructions
  • Identifiers and permissions for the AI assistant you connect, such as its OAuth client name (for Muse, Muse and Meta account identifiers; WhatsApp identifiers once that feature launches)
  • If the business connects Calendly: the access tokens Calendly issues when the business approves BotPhone through Calendly's sign-in, its Calendly account name, email, and time zone, and its event types and booking links

Call and message information

  • Caller or sender phone numbers, names, and message content
  • Transcripts, summaries, messages, and call metadata such as date, time, duration, and status
  • Information a caller or sender chooses to provide during a conversation
  • When a caller asks to book a meeting: the email address they give, the meeting type and time, and whether the meeting was booked or a booking link was emailed
  • Routing, delivery, read, and interaction status for supported communications

Sign-in and payment information

  • Name, email address, and account identifier received when you sign in with Google
  • Transaction identifiers, payment status, and limited billing details received from Stripe

Technical and usage information

  • Device, browser, IP address, log, diagnostic, security, and error information
  • Feature usage and beta feedback

3. How we use information

  • Provide, configure, secure, support, and troubleshoot the receptionist
  • Answer communications, follow approved instructions, and create summaries
  • Send configured information to the connected AI assistant
  • When the business connects Calendly, book callers onto its Calendly calendar or email callers its booking link
  • Prevent fraud, misuse, security incidents, and platform-policy violations
  • Comply with law and enforce our agreements
  • Evaluate and improve the beta using feedback and appropriately protected or de-identified information

We do not sell caller conversation content or use it to advertise to callers.

4. Call audio and transcripts

BotPhone does not record calls or create or store audio recordings in version 1. Live call audio is processed in real time only as needed to carry the conversation and create a transcript. We retain text transcripts, summaries, messages, and call metadata as described below.

5. Connected assistant access and control

When you connect Muse, the connection may allow Muse to access your calls, summaries, transcripts, and receptionist settings within the permissions you grant. Muse may also be used to share approved context with BotPhone or request changes to the receptionist's settings and instructions. BotPhone's voice agents, not Muse, handle inbound and outbound calls. The changes you confirm are sent to BotPhone and stored with your receptionist configuration.

You can disconnect Muse at any time through the available account or connection controls. Disconnecting stops new information from being shared through that connection, but it may also prevent connected features from working. Information already received by Meta or Muse is handled under their applicable terms and privacy policies.

6. Service providers and sharing

We use the following providers to operate the product. A provider receives only the information reasonably needed for its role, and not every provider receives every category of information:

  • Twilio for phone numbers, telephony, call routing, and supported messaging
  • LiveKit for real-time media, voice-agent infrastructure, and AI inference
  • Deepgram for live speech-to-text transcription
  • Fish Audio, through LiveKit, for text-to-speech voice generation
  • Gemma, through LiveKit, for language processing, responses, and summaries
  • OpenAI for knowledge-base search embeddings
  • Supabase for accounts, database services, settings, and conversation data
  • Render for application hosting and infrastructure
  • Stripe, including Link, for payments and billing
  • Resend for transactional and call-summary emails, and booking-link emails to callers who ask for one
  • Calendly, when the business connects its own Calendly account, for checking open times and booking meetings. Calendly receives the caller's name, email address, the meeting time, and, for phone-call meeting types, the caller's phone number
  • Google for sign-in and authentication when you choose Google sign-in
  • The AI assistant you connect and its provider (such as Meta for Muse, xAI for Grok Bot, OpenAI for ChatGPT and Dots, or Anthropic for Claude), and (once available) WhatsApp, when a business connects those services or directs us to transmit information to them
  • The subscribing business and people it authorizes
  • Professional advisers, regulators, courts, or law enforcement when legally required or reasonably necessary to protect rights and safety
  • A successor in a merger, financing, acquisition, reorganization, or sale of assets, subject to appropriate protections

7. Payments, emails, and bookings

Stripe, including its Link checkout service, handles payment-card information. BotPhone does not receive or store full card numbers or card security codes. We receive limited transaction and billing details from Stripe so we can apply credit, confirm payment, provide support, and maintain financial records.

Call-summary emails contain call content, which may include caller details, transcripts, summaries, messages, and any meetings booked during the call. Resend delivers those emails to the addresses the account owner configures. The owner is responsible for choosing authorized recipients and keeping those addresses current and secure.

If the business connects Calendly and a caller asks to book a meeting, the receptionist uses the business's Calendly account to check open times and book the meeting in the caller's name. Calendly then sends its own confirmation and calendar invitation, and the booking is held in the business's Calendly account under Calendly's terms and privacy policy. If booking is not available, the receptionist can email the caller the business's booking link through Resend, only to the address the caller gives and confirms.

8. Cookies and browser storage

We use only cookies or browser storage that are essential for sign-in, session continuity, account security, and related product operation. BotPhone MCP does not use advertising cookies or cross-site advertising trackers.

9. Retention and deletion

While an account is active, we keep transcripts, summaries, messages, and related call metadata, including records of meetings booked or booking links emailed during a call, along with account information and receptionist settings.

When a business disconnects Calendly, we ask Calendly to revoke BotPhone's access and delete its stored Calendly tokens and event-type settings right away. Meetings already booked stay in the business's Calendly account until the business removes them there.

After an account closes, or within 30 days of receiving a deletion request at info@botphone.tel, we delete or de-identify its account information, receptionist settings, transcripts, summaries, messages, and call metadata. Deletion excludes logs, backups, and copies held by subprocessors, which are removed on their own schedules. We may retain limited records longer when required for tax, accounting, payment, fraud-prevention, security, dispute, or other legal purposes. Our providers may retain limited records under their own legal obligations and retention schedules.

10. Security

We use administrative, technical, and organizational safeguards designed to protect information. Calendly access tokens are encrypted before we store them. No system is completely secure, and a beta may contain defects. Businesses should avoid configuring the service to collect information that is not needed for the receptionist's purpose.

11. International transfers

BotPhone and its providers may process information in the United States and other countries. Where required, we use lawful transfer mechanisms and contractual protections.

12. Privacy choices and rights

Depending on location, individuals may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information. Callers should usually contact the business they communicated with first because that business controls the relationship. Requests may also be sent to BotPhone at the address below.

13. Children

The beta is intended for business users who are at least 18. It is not designed for children, and businesses may not intentionally use it to solicit personal information from children without a lawful basis and appropriate protections.

14. Changes

We may update this policy as the beta, legal requirements, or platform capabilities change. We will post the updated date and provide additional notice when required by law.

15. Contact

Questions and privacy requests can be sent to info@botphone.tel.

BotPhone
Overland Park, Kansas, United States