audioMCP.ai collects only the information needed to operate the site, respond to demo requests, issue platform access, secure the service, and process voice-agent activity requested by customers. Voice and call data may include call metadata, audio, transcripts, prompts, tool-call events, and routing details when those features are enabled.
Effective date and scope
Effective date: June 1, 2026. This Privacy Policy describes how audioMCP.ai handles information collected through the public website, contact forms, demo flows, API access, MCP tools, and related support channels.
When a customer uses audioMCP.ai to power calls with its own end users, the customer is responsible for its relationship with those end users, including required notices and consent.
Information we collect
Contact and account information: name, work email, company, role, authentication data, billing contact details, and support messages.
Platform and usage information: API keys, MCP client identifiers, tool-call logs, configuration settings, IP address, device/browser data, timestamps, error logs, usage volume, and security events.
Voice-agent information: prompts, agent instructions, call routing settings, phone numbers used for inbound or outbound calls, call metadata, transcripts, audio recordings if enabled, and tool-call events generated during a conversation.
How we use information
We use information to provide and secure the service, provision voice agents, route calls, process demo requests, deliver support, measure usage, debug errors, prevent abuse, and improve reliability.
We do not use customer prompts, transcripts, audio, or call data to train general-purpose AI models unless a customer separately agrees in writing.
Voice and call data
Voice and call data can be sensitive. Customers must obtain all legally required consent before recording, transcribing, placing, or receiving calls through audioMCP.ai.
The platform may process voice data through telephony, speech-to-text, text-to-speech, hosting, logging, and monitoring providers as needed to complete the requested call workflow. Retention settings should be configured to keep call data only as long as needed for the service, security, billing, legal, or customer-requested purposes.
Cookies and analytics
The public site may use basic cookies or similar technologies for session security, preferences, analytics, and performance measurement. Marketing or cross-site tracking tools should not be enabled until the company has published the required notice and opt-out controls.
Sharing and subprocessors
We may share information with service providers that help operate the platform, including cloud hosting, database, logging, analytics, email, customer support, billing, telephony, speech-to-text, text-to-speech, and abuse-prevention vendors.
We may also disclose information if required by law, to protect the service and users, during a business transfer, or with customer direction. audioMCP.ai should publish a current subprocessor list before production launch.
Retention and deletion
We retain account, billing, security, and usage records for as long as needed to operate the service and meet legal obligations. Demo submissions and support messages are retained while needed to respond and maintain business records.
Customers may request deletion of account or project data, subject to security logs, backups, fraud-prevention records, billing records, and legal obligations that require longer retention.
Your privacy rights
Depending on location, individuals may have rights to access, correct, delete, or receive a copy of personal information, and to object to or restrict certain processing.
California residents may have rights under the CCPA/CPRA, including the right to know, delete, correct, and opt out of certain sharing. audioMCP.ai does not sell personal information as that term is commonly used; if that changes, the site must provide the required notice and opt-out mechanism.
Security
We use administrative, technical, and organizational safeguards designed to protect information, including access controls, encryption in transit, least-privilege permissions, logging, monitoring, and vendor review.
No online service can guarantee perfect security. Customers should protect API keys, restrict MCP client access, and promptly report suspected unauthorized use.
International processing
Information may be processed in the United States or other countries where audioMCP.ai and its providers operate. Customers with regulated residency requirements should confirm supported regions before sending production voice or call data.
Contact
Privacy requests should be sent to privacy@audiomcpai.com. If that mailbox is not yet active, the company should replace this address before launch with the correct privacy contact and response workflow.