Data Processing Addendum
This Data Processing Addendum ("DPA") forms part of the SonicFront Master Services Agreement (the "Agreement") between SonicFront and Customer. Capitalized terms not defined here have the meanings in the Agreement.
1. Scope and roles
1.1 This DPA applies to personal information in Customer Data that SonicFront processes on Customer's behalf ("Customer Personal Information").
1.2 Customer is responsible for the personal information it controls. Under the applicable law, Customer is the "organization", "controller", "business" or "covered entity". SonicFront is Customer's "service provider", "processor" or "contractor". SonicFront processes Customer Personal Information only:
- to provide the Service under the Agreement;
- on Customer's documented instructions;
- as required by law.
SonicFront will tell Customer if it believes an instruction breaks the law.
1.3 Applicable laws may include:
- Canada: PIPEDA, Quebec's Act respecting the protection of personal information in the private sector (Law 25), Alberta and British Columbia PIPA, and provincial health-privacy laws.
- United States: the CCPA/CPRA and other state consumer privacy laws, and HIPAA (only under a signed Business Associate Agreement).
Together these are "Privacy Laws".
2. Details of processing
| Item | Description |
|---|---|
| Subject matter | Answering and handling calls and texts for Customer; booking; message taking; dashboard |
| Duration | The Subscription Term plus the deletion period in Section 9 |
| Data subjects | Customer's Callers; Customer's personnel who use the dashboard |
| Personal information | Phone numbers; names; call date, time and duration; call transcripts and summaries; message content; appointment details; any information Callers volunteer; dashboard user emails, roles and audit logs |
| Sensitive information | Not intended. Health, financial-account, government-ID and payment-card data are excluded unless a signed addendum enables them (Agreement §7.6–7.7) |
| Audio | Calls are processed in real time for speech recognition. SonicFront does not keep audio recordings unless the Order Form enables recording |
3. Customer obligations
3.1 Customer will give Callers all notices required by Privacy Laws and obtain any consents they require. This includes notice that calls are answered by an automated system and may be transcribed, and consent for text messages.
3.2 Customer will ensure its instructions comply with Privacy Laws and that it has a lawful basis for all Customer Personal Information it asks SonicFront to process.
3.3 Customer is responsible for responding to requests from Callers to exercise their privacy rights. SonicFront will assist as described in Section 7.
4. SonicFront obligations
4.1 Confidentiality. SonicFront ensures that personnel with access to Customer Personal Information are bound by confidentiality obligations and are trained appropriately.
4.2 Security. SonicFront maintains the safeguards in Annex A and keeps them appropriate to the sensitivity of the information. It may update Annex A, provided updates do not materially reduce overall protection.
4.3 No sale or sharing. SonicFront will not:
- sell or "share" (for cross-context behavioural advertising) Customer Personal Information;
- retain, use or disclose it outside the direct business relationship with Customer, or for any purpose other than the business purposes in the Agreement;
- combine it with personal information from other sources, except as Privacy Laws permit for service providers.
SonicFront certifies that it understands these restrictions.
4.4 De-identified data. SonicFront may create de-identified, aggregated data from Customer Personal Information and use it to operate and improve the Service. It will not attempt to re-identify such data.
5. Sub-processors
5.1 Customer authorizes SonicFront to engage the sub-processors listed in Annex B and future sub-processors under this Section. SonicFront will:
- bind each sub-processor by written terms that protect Customer Personal Information at least as strongly as this DPA in all material respects;
- remain responsible for its sub-processors' performance.
5.2 SonicFront will give at least 30 days' notice of a new sub-processor, by email or by updating its published list with a notification mechanism. Customer may object on reasonable data-protection grounds within that period. If the parties cannot resolve the objection, Customer may terminate the affected Service and receive a refund of prepaid fees for the unused term, as its sole remedy.
6. Cross-border processing
6.1 Customer acknowledges that SonicFront and its sub-processors may process Customer Personal Information outside Customer's province, state or country, including in the United States and Canada, where it may be accessible to authorities under local law.
6.2 Customer is responsible for informing Callers about such processing where Privacy Laws require it. Where Law 25 applies, this includes completing any privacy impact assessment Customer must perform. SonicFront will provide reasonable information to support that assessment.
7. Assistance
7.1 Taking into account the nature of the processing, SonicFront will provide reasonable assistance, through the dashboard's export and deletion tools or on request, with:
- requests from Callers to access, correct or delete their information;
- privacy impact assessments;
- consultations with regulators.
7.2 If SonicFront receives a request directly from a Caller, it will refer the Caller to Customer and will not respond itself unless required by law.
8. Security incidents
8.1 SonicFront will notify Customer without undue delay, and within 72 hours where feasible, after confirming a breach of security safeguards involving Customer Personal Information in SonicFront's or its sub-processors' control (an "Incident").
8.2 The notice will describe, as far as then known:
- the nature of the Incident;
- the categories and approximate number of individuals and records affected;
- the likely consequences;
- the steps taken or proposed.
SonicFront will update Customer as more information becomes available.
8.3 SonicFront will take reasonable steps to contain and remediate the Incident. Customer is responsible for deciding whether to notify regulators and individuals, and for doing so, unless the law requires SonicFront to notify directly. SonicFront will keep records of Incidents as Privacy Laws require.
8.4 Notifying an Incident is not an admission of fault or liability.
9. Return and deletion
9.1 For 30 days after termination, Customer may export Customer Personal Information through the dashboard.
9.2 Within 60 days after that period, SonicFront will delete Customer Personal Information from production systems. Backups expire on their normal cycle (currently 14 days). Exceptions:
- information SonicFront must keep by law, which it will keep protected and use only for that purpose;
- de-identified data under Section 4.4.
10. Audits
10.1 On written request no more than once a year, SonicFront will provide information reasonably needed to show compliance with this DPA. This may be in the form of security documentation, completed questionnaires or third-party reports where available.
10.2 Where Privacy Laws require an on-site audit, the parties will agree the scope, timing and confidentiality in advance. Customer will bear the costs.
11. Liability
11.1 Each party's liability under this DPA is subject to the limitations and exclusions in the Agreement.
Annex A: Security measures (summary)
- Encryption: in transit (TLS) for all connections to the Service and between SonicFront and its sub-processors. Encryption at rest is provided by the database and cloud providers.
- Access control:
- per-customer tenant isolation, with database row-level security;
- role-based dashboard access;
- multi-factor authentication for SonicFront operators;
- least-privilege access for personnel.
- Logging: audit logging of sensitive actions; monitoring and error alerting.
- Backups: nightly backups, kept for 14 days. Credentials are stored in restricted files or secret stores, never in source code.
- Data minimization: no audio recordings stored by default. Starter scripts avoid asking for sensitive information. Callers are told the system is automated.
- Vendors: sub-processors are chosen for their security posture, and their API data-use terms are configured so that customer content is not used to train their general models.
- Incident response: a documented procedure: triage, containment, notification and review.
Annex B: Sub-processors (as of October 2026)
| Sub-processor | Purpose | Location |
|---|---|---|
| Vapi | Voice conversation platform | United States |
| Deepgram | Speech recognition | United States |
| Cartesia | Speech synthesis (voice) | United States |
| OpenAI | Language model | United States |
| Twilio | Phone numbers, calls, SMS | United States |
| Supabase | Database and authentication | United States (us-east-1) |
| Calendar integration (Customer's own account) | United States / global | |
| HostArmada | Website, dashboard and application hosting | Canada / United States |
| Stripe | Billing and payments (Customer billing data only) | United States / Canada |
| Resend | Transactional email (alerts, sign-in) | United States |
| Sentry, Langfuse | Error monitoring and call-quality traces | United States |