Trust and compliance

AI calling needs clear consent, storage, and access boundaries.

AI Calls gives teams a controlled platform for outbound calls, private recordings, and ledger-owned billing. Users remain responsible for lawful calling, recipient consent, and local notice obligations.

Consent is user-owned

Users choose recipients, countries, schedules, prompts, and variables. They must have a lawful basis to call and honor opt-out, do-not-call, and local consent requirements.

Recording notice responsibility

If a call is recorded, transcribed, summarized, or analyzed, users are responsible for any required notice or consent before or during the call.

Private platform storage

Call records, transcripts, summaries, and recordings are stored as platform artifacts. Recordings are archived to private storage rather than exposed as upstream provider URLs.

Authenticated recording access

Users download recordings through authenticated platform routes for calls they own. The UI and APIs do not expose private R2 object keys.

Provider adapter boundary

Call execution connectors stay internal. Customer-facing surfaces expose platform facts, not raw connector payloads or upstream costs.

This page is an operational boundary, not a legal certification.

The platform helps preserve auditability, private artifact access, and billing consistency. It does not replace the user's obligation to review laws, industry rules, customer contracts, or country-specific calling restrictions before placing calls.