Security and data handling

This page describes how we handle data in our services. Specific terms for each customer are set in the service agreement and, where applicable, a business associate agreement (BAA).

Test calls use fictional data

Canary Calls use fictional callers and fictional patient details. We never use real caller or patient information in a test script. Test calls go to CanaryTel-owned test on-call numbers or inboxes, so we never contact real on-call staff or clinicians.

Real call data

Canary Watch, in early access, reads real call records and transcripts. We do this only under an agreement with the customer, and under a BAA where the data includes patient health information. Any plan that handles patient health information includes a BAA, and we flow the same obligations down to every provider that touches the data.

Access

• Least-privilege access: our staff can reach only the data they need for the work.
• Read-only access to customer exports and APIs. We ask for a read-only credential, scoped to the records scoring needs.

Encryption

Data is encrypted in transit.

Data minimization and retention

We collect only what scoring and reporting need. Retention is agreed with each customer in the service agreement.

Sub-processors

We list the sub-processors that handle customer data on request.

Certifications

We do not currently hold SOC 2 or HITRUST certification. We share our controls during evaluation.

Questions and reports

To ask about our controls or report a security concern, use the contact form. For the website itself, see the privacy policy.