AI Phone Genius Privacy Policy
Last updated August 6, 2026.
1. Information we collect
We collect account and workspace details, contact lists, phone numbers, consent and opt-out records, agent and campaign settings, call metadata, recordings, transcripts, summaries, analytics, audit records, and security logs when those features are used. A beta application stores the submitted name, email, company, team size, selected use case, optional message, request IP address, and browser user-agent.
2. How we use information
We use information to authenticate users, provide the beta, operate authorized calling workflows, apply workspace safeguards, produce reporting, deliver configured integrations, provide support, prevent abuse, and protect the service. We use beta-application information to review the request and contact the applicant at the submitted email address. Applying does not create a workspace, subscription, phone call, or charge.
3. When information is shared
We share information with infrastructure, database, calling, scheduling, analytics, support, and payment services as needed for the features you use. We also send information to destinations you configure, such as calendars, notifications, and webhooks. We may disclose information when required by law or to protect people, the service, and our rights.
4. Retention and deletion
Active workspace data remains in the service until an authorized operator deletes it. Security records and recovery backups are retained separately for service protection, incident response, dispute resolution, and legal obligations. Submit a request through the contact page to ask for access, correction, or deletion. We verify authority before changing workspace or call data.
5. Workspace responsibilities
Workspace owners control the contact data and calling instructions they place in the service. They must have permission to process and call each person, provide required notices, document consent, honor opt-outs, and respond to requests involving the data they supply.
6. Security and access
The service uses encrypted transport, signed session cookies, hashed passwords and API keys, role checks, tenant row isolation, signed calling-service webhooks, audit logs, and restricted outbound URL handling. Keep credentials secret and report suspected compromise promptly.
7. Requests and contact
Submit privacy questions and data requests through the public contact page.