Privacy Policy
How Zeo Platforms, Inc. handles information in connection with Zeovoice.
1. Scope
This Privacy Policy describes how Zeo Platforms, Inc. (“Zeo,” “we,” “us”) processes personal information when people visit Zeovoice.com, create an account, configure AI employees, use calling or website-chat features, contact us, or otherwise use Zeovoice.
2. Information we may collect
Depending on how Zeovoice is configured and used, information may include account and contact details; organization and workspace information; employee configurations; business knowledge supplied by customers; call metadata, transcripts or recordings when enabled; website-chat messages, customer questions and follow-up details when the web channel is enabled; lead and outcome data; integration information; billing and transaction records; device, browser, log, security, and usage information; and communications with us.
3. How we use information
We may use information to provide and secure Zeovoice; authenticate users; configure and operate AI employees; process calls and actions; provide support; measure usage and outcomes; bill customers; prevent abuse; improve product reliability; comply with law; and communicate about the service.
4. Service providers and subprocessors
Zeovoice may rely on infrastructure and service providers for model inference, speech processing, telephony, payments, hosting, databases, monitoring, and communications. Customer data should be shared with providers only as necessary for the configured service and contractual relationship.
5. Customer responsibilities
Customers control the business information, knowledge, contact data, call and website-chat flows, retention choices, and employee configurations they provide to Zeovoice. Customers are responsible for having an appropriate legal basis for data they submit and for required notices or consent related to calls, recordings, AI use, outreach, and connected systems.
6. Retention and deletion
We retain information only as long as reasonably necessary for service delivery, security, billing, legal obligations, dispute resolution, and configured customer requirements. Retention may vary by data category and customer configuration. Account owners may request deletion through the Zeovoice contact page, subject to legal, security, and billing requirements.
7. Security
Zeovoice uses technical and organizational safeguards intended to protect data, including encrypted credentials, authenticated access, tenant scoping, policy controls, and audit evidence. No system can guarantee absolute security.
8. Your choices and rights
Depending on location, individuals may have rights related to access, correction, deletion, portability, objection, or restriction. Requests should be submitted through the Zeovoice contact page. Identity verification may be required.
9. Children
Zeovoice is a business service and is not intended for children. Customers should not knowingly use Zeovoice to collect children’s personal information without all legally required safeguards and written authorization.
10. Changes
We may update this policy as Zeovoice changes. Material updates should be reflected by a new effective date and, where appropriate, additional notice.
Operational analytics and protection
When configured, Zeovoice may use rate limiting and other abuse-prevention controls to protect public forms and account entry points, Sentry to diagnose software errors, PostHog to understand product and website usage, HubSpot to manage sales relationships, Resend to deliver transactional messages, and external uptime monitoring to monitor service availability. These services are enabled only through production configuration and should be reviewed against your deployment, consent, retention, and contractual requirements.
Privacy choices
Zeovoice separates essential operational processing from optional website analytics. Optional PostHog analytics are not loaded until the visitor chooses to allow analytics. The preference can be changed later through Privacy choices in the site footer.
Attribution data used for sales requests is limited to session-level landing, referrer, and campaign parameters and is submitted only when a visitor intentionally sends a contact, pilot, or business-case request.