Where your data sits, and who can reach it.

Your data is separated at the database, not by our code

Every record carries a client identity and the separation is enforced by the database itself rather than by application logic remembering to filter. A mistake in our code cannot show your data to another client, because the database refuses the query rather than trusting the request.

We never hold your passwords or your tokens

Access is granted through each provider's own permission system, scoped to the minimum needed, and we store a reference to a secret rather than the secret. You revoke it from your own account settings without asking us, and everything stops.

Everything an agent does is recorded

Every action is written to a log that can be added to but never edited or deleted, including which agent acted, when, and whether a person approved it. That is what makes "what happened on the fourteenth" a question with an answer.

Health information is not collected at all

For clinics we do not record calls. The agent refuses every clinical, symptom and medication question, and does not write down or repeat anything medical a caller volunteers. We keep only categories: booked, estimate asked for, transferred, reason for calling. Not becoming a holder of health data is safer than becoming a compliant one.

Who else touches your data

You are entitled to know this rather than having to ask.

Vercel

Hosting for this website and the client console.

Supabase

Database, including the Lead Ledger and reporting data.

Anthropic

The model the agents run on.

Retell

The voice platform, where a phone department is running.

Google

Analytics, Search Console and Business Profile, where connected.

If something goes wrong

PIPEDA requires us to report a breach that poses a real risk of significant harm, to the Privacy Commissioner and to you. We will tell you what happened, what was affected and what we did, without waiting to be asked.