Data Processing Agreement
The data processing agreement that applies automatically to every Bridgeside AI customer that puts personal data into the Service, with the SCCs, security measures and sub-processor terms.
Effective date: 10 November 2026. Last updated: 22 November 2026.
This Data Processing Agreement ("DPA") is between PILOTLAB LLC, a Wyoming limited liability company, doing business as Bridgeside AI ("Bridgeside AI", "we", "us"), 1309 Coffeen Ave Ste 1200, Sheridan, WY 82801, United States, and the customer that has accepted the Terms of Service ("Customer", "you").
This DPA applies automatically. It forms part of the Terms of Service and applies whenever the Customer, as a controller, submits personal data to the Service. No signature is needed. If this DPA and the Terms of Service conflict on the protection of personal data, this DPA prevails.
1. Definitions
"Data Protection Law" means the GDPR (Regulation (EU) 2016/679), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and US state privacy laws, to the extent each applies. "Personal Data", "Processing", "Controller", "Processor", "Data Subject", "Personal Data Breach" and "Supervisory Authority" have the meanings given in the GDPR. "Customer Personal Data" means Personal Data the Customer submits to the Service or that the Service collects on the Customer's behalf, as described in Annex I. "Sub-processor" means a third party we engage to Process Customer Personal Data. "SCCs" means the standard contractual clauses approved by the European Commission in Implementing Decision (EU) 2021/914.
2. Roles and scope
The Customer is the controller of Customer Personal Data and Bridgeside AI is its processor. Where the Customer is itself a processor for another controller, Bridgeside AI is its sub-processor and the Customer confirms it has that controller's authority. Annex I describes the Processing. Bridgeside AI is the controller of its own account, billing, website and security data, which the Privacy Policy covers.
3. Customer obligations
The Customer decides the purposes and legal basis for Processing Customer Personal Data, gives Data Subjects any information the law requires, obtains any consent needed (including for calls, recording and AI disclosure), and ensures its instructions comply with Data Protection Law and the Acceptable Use Policy. The Customer chooses the retention period for call content in the portal.
4. Our obligations
Instructions. We Process Customer Personal Data only on the Customer's documented instructions, which are this DPA, the Terms of Service, the Customer's configuration of the Service (campaigns, retention, webhooks, integrations) and any further written instructions we agree. We tell the Customer if we believe an instruction breaks Data Protection Law, unless the law prohibits it.
Confidentiality. Everyone we authorise to Process Customer Personal Data is bound by a duty of confidentiality.
Security. We implement the technical and organisational measures in Annex II and keep them appropriate to the risk.
No training and no sale. We do not use Customer Personal Data to train AI models and we do not sell it.
5. Sub-processors
General authorisation. The Customer gives general authorisation for us to engage Sub-processors. Annex III lists them by category and country. We impose data protection obligations on each Sub-processor that are no less protective than this DPA, and we remain responsible for their performance.
The current list. We give the Customer the current list of Sub-processors, with names, on written request to hello@bridgeside.ai. The list is our confidential information and the Customer may not share it with third parties, except its own advisers and regulators under a duty of confidence.
Changes. We give at least 30 days' notice of a new or replaced Sub-processor by email to every Customer that has asked us, in writing, to be notified. The Customer may object on reasonable data protection grounds within that period. We will then discuss a reasonable alternative in good faith; if none is available, the Customer may end the affected part of the Service and receive a refund of unused prepaid credit.
6. Assistance
Taking into account the nature of the Processing, we help the Customer:
- respond to requests from Data Subjects to exercise their rights. We forward any request we receive about Customer Personal Data to the Customer and do not answer it ourselves unless the Customer asks us to;
- carry out data protection impact assessments and prior consultations with Supervisory Authorities;
- meet its security and breach notification obligations.
The portal also lets the Customer view, export (CSV and JSON) and delete call data itself.
7. Personal data breaches
We notify the Customer of a Personal Data Breach affecting Customer Personal Data without undue delay and in any case within 48 hours of becoming aware of it. The notice describes, as far as we know at the time, the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, and the measures taken or proposed. We give further information as it becomes available and take reasonable steps to contain the breach.
8. Return and deletion
During the term the Customer can export its call data from the portal at any time. Call content is also deleted or redacted automatically under the retention period the Customer sets (1 to 90 days). Within 30 days after termination, we delete Customer Personal Data, except where the law requires us to keep it; in that case we keep only what is required, protect it under this DPA and delete it when the obligation ends. A billing record of each call (call id, date, duration, campaign, status, disposition and billable minutes) is kept for tax and accounting purposes. Database backups are overwritten on their regular cycle (see Annex II).
9. Audits
We make available to the Customer the information reasonably necessary to demonstrate compliance with this DPA. The Customer, or an independent auditor bound by confidentiality, may audit our compliance on at least 30 days' written notice, no more than once in any 12-month period (unless a Supervisory Authority requires it or after a Personal Data Breach), during business hours, at the Customer's cost, and in a way that does not disrupt the Service or breach our duties to other customers.
10. International transfers
Bridgeside AI and some Sub-processors are located in the United States, and our support and engineering staff include team members in Pakistan. To the extent Customer Personal Data from the EEA is transferred to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference: Module 2 (controller to processor) where the Customer is a controller, and Module 3 (processor to processor) where the Customer is a processor. For the SCCs:
- Clause 7 (docking clause) applies;
- Clause 9: option 2 (general written authorisation) applies, with the notice period in section 5;
- Clause 11: the optional language does not apply;
- Clauses 17 and 18: the SCCs are governed by the law of Ireland, and disputes are resolved by the courts of Ireland;
- Annexes I, II and III of this DPA complete the corresponding Annexes of the SCCs; the competent Supervisory Authority is the one determined under Clause 13.
For transfers from the United Kingdom, the International Data Transfer Addendum to the EU SCCs issued by the Information Commissioner applies, with the information above completing its tables. For transfers from Switzerland, the SCCs apply with the amendments required by the Swiss Federal Data Protection and Information Commissioner, references to the GDPR read as references to the Swiss Federal Act on Data Protection. Where a US Sub-processor is certified under the EU-U.S. Data Privacy Framework, we may rely on that certification for transfers to it.
11. US state privacy laws
Where US state privacy laws apply, Bridgeside AI acts as a service provider or processor. We Process Customer Personal Data only for the business purposes in Annex I, do not sell or share it, do not retain, use or disclose it outside our direct business relationship with the Customer, and do not combine it with personal data from other sources except as those laws allow.
12. Duration and precedence
This DPA lasts as long as we Process Customer Personal Data for the Customer. The limitations of liability in the Terms of Service apply to this DPA, except where Data Protection Law or the SCCs do not allow it. If this DPA and the SCCs conflict, the SCCs prevail. If this DPA and the Terms of Service conflict on data protection, this DPA prevails.
Annex I: Description of the Processing
| Item | Description |
|---|---|
| Subject matter | Providing AI voice agents that answer and place phone calls for the Customer through its dialer or carrier, and the related portal. |
| Duration | The term of the Customer's use of the Service, plus the deletion period in section 8. |
| Nature of the Processing | Receiving live call audio and streaming it for transcription; generating the agent's replies and speaking them; storing transcripts, summaries and collected answers; booking appointments; writing dispositions and do-not-call requests to the Customer's dialer; sending events to the Customer's webhooks; deleting or redacting data on the Customer's retention schedule. |
| Purpose | To run the Customer's call campaigns and give the Customer the results. |
| Categories of Data Subjects | People the Customer's campaigns call or who call the Customer (callers and leads); the Customer's staff using the portal. |
| Categories of Personal Data | Phone numbers, lead ids, names given for appointments, voice (live audio only, not stored), the content of calls as transcripts and summaries, answers collected during calls, appointment times and calendar links, call metadata (times, duration, outcome, disposition); for portal users, names, email addresses, roles and sign-in records. |
| Special categories | Not intended. The Acceptable Use Policy forbids using agents to collect health information, government ID numbers or financial account details. If a caller volunteers such data, it appears in the transcript until the retention period ends. |
| Frequency | Continuous, for each call the Customer routes to an agent. |
| Retention | Call content: the Customer's retention setting, 1 to 90 days. Per-call billing records: for the life of the account and then 7 years. Account data: until 30 days after termination. |
Annex II: Technical and organisational measures
- Encryption in transit. TLS for the website, the portal, the API, WebSocket media streams and all calls to Sub-processors. RTP call audio between a customer's dialer and the Service travels over the network path the customer configures.
- Encryption of secrets. Dialer credentials, API keys, provider keys and Google tokens are encrypted in the database with AES-256-GCM. Passwords are hashed with bcrypt.
- No audio storage. Call audio is streamed for transcription and voice and is not stored by Bridgeside AI.
- Minimal logs. Server logs never contain what callers or agents say; they are kept for 30 days.
- Retention controls. An hourly job redacts or deletes call content after the Customer's retention period (1 to 90 days).
- Network. The databases accept connections only from the same server and are not reachable from the internet. A host firewall admits only the ports the Service uses.
- Access control. Each organization's data is separated in the portal, and each portal user sees only the sections their administrator grants. Production access is limited to the PILOTLAB LLC personnel who need it.
- Abuse protection. Bot protection and rate limits on sign-in, sign-up and password reset, and per-plan limits on concurrent calls.
- Backups. Nightly database backups kept for 14 days.
- Personnel. Staff with access are bound by confidentiality.
Annex III: Sub-processors (by category and country)
| Category | Purpose | Country |
|---|---|---|
| Cloud hosting provider (dedicated server) | Hosting the Service and its databases | United States |
| Speech-recognition provider | Transcribing live call audio | United States |
| Voice providers | Speaking the agent's replies (Basic and Premium voices) | United States |
| Language-model hosting provider | Generating replies, dispositions and summaries | United States |
| Weather data provider | Weather for a place a caller mentions (no phone number or name) | Switzerland |
| Email delivery provider | Account and notification email | United States |
| Bot-protection provider | Telling people from automated scripts on sign-in, sign-up and password forms | United States |
| Calendar booking (if connected), sign-in | United States and other countries | |
| PILOTLAB LLC personnel | Support and engineering | United States and Pakistan |
The named list is available to Customers on written request, as described in section 5.