PIPEDA-aligned handling
We collect the minimum needed to answer, book, and dispatch. Call recordings and transcripts belong to you. We do not sell them, and we do not use them to train foundation models.
Security & compliance
Right On Call is a boutique receptionist, not a consumer app that trains on whatever you type. Recordings exist so we can dispatch, book, and debug, not so we can sell a dataset.
We collect the minimum needed to answer, book, and dispatch. Call recordings and transcripts belong to you. We do not sell them, and we do not use them to train foundation models.
Ontario is one-party consent for most business calls. We still put a short recording disclosure on the line, and the agent will identify as automated if asked.
The receptionist cannot invent availability, cannot diagnose, and cannot quote a repair price. Gas, smoke, or spark reports take a bounded safety script and a human callback.
A dashboard kill switch stops the agent from answering. Tokens for third-party tools are encrypted at rest. Database access is row-level restricted per client.
Voice AI cannot live entirely inside one Canadian closet. Telephony, speech, and models run with named vendors. We keep that list short, and we do not claim a data-residency story we cannot keep.
| Vendor | Role | Region |
|---|---|---|
| Twilio | Telephony and SMS | US / CA numbers |
| Vapi | Live voice pipeline | US |
| Anthropic | Conversation and summaries | US |
| Supabase | Call log and dashboard data | configurable |
| Render | Application hosting | US / EU |
For the longer, plain-language version of this page, read PIPEDA, Recordings, and US Subprocessors.