Roles
The customer is the controller and Operon is the processor. Where the customer is itself a processor for another controller, Operon acts as a subprocessor and the same obligations apply.
Scope of processing
Operon processes personal data only on documented instructions from the customer, which the agreement and the customer's platform configuration constitute. We tell the customer if we believe an instruction violates applicable data protection law.
- Subject matter: provision of AI communication agents and supporting services
- Duration: for as long as the customer's workspace exists, within the retention limits the customer sets
- Categories of data subjects: the customer's customers, prospects, patients, clients, and staff
- Categories of personal data: contact details, call recordings, transcripts, and summaries, message content, appointment records, and anything else a caller or customer chooses to say
Confidentiality and personnel
Operon's own admin console, the one place in the product that can open any workspace's records, is limited to staff on an allowlist set in Operon's deploy settings, who use it only to deliver and support the service. Operon ensures that everyone it allows to process personal data is bound to keep it confidential.
Security measures
Operon maintains technical and organizational measures appropriate to the risk, including:
- Encryption in transit with TLS on every connection to the console and API, with HSTS on
- Integration credentials encrypted with AES-256-GCM before they are stored
- A workspace per customer, which only ever sees its own data
- Four user roles, owner, admin, operator, and viewer, and an audit log of who changed what, and when
- Call recording that the customer can switch off, and retention limits the customer sets
- Notice to the customer within 24 hours of confirming a breach of its personal data
Subprocessors
The customer authorizes the use of the subprocessors listed on our subprocessors page. We impose data protection obligations on each subprocessor no less protective than those in this DPA, and we remain liable for their performance.
We give 30 days notice before adding or replacing a subprocessor. The customer may object on reasonable data protection grounds, and if we cannot resolve the objection the customer may terminate the affected service without penalty.
Model providers and training
Operon does not use personal data to train any model. Operon sends conversation content to the AI model providers named on our subprocessors page only to produce the agent's replies and run the service for the customer.
Data subject requests
The console lets the customer correct and delete a contact, delete its conversation history, and export its contacts, conversations, calls, appointments, and knowledge as a file. Where a data subject contacts us instead of the customer, we route the request to the customer and assist in responding, without additional charge.
Where data is processed
Operon is a US service. It processes personal data in the United States, and so do its subprocessors, with the one exception named on our subprocessors page.
Audit
Operon answers the customer's reasonable written questions about the security measures described in this DPA. Where the customer requires further assurance, the parties will agree on the scope and timing of an audit, no more than once per year absent a security incident.
Deletion and return
The customer can export its records, and delete its conversation history or its whole workspace, from the console at any time, including while the workspace is paused after its subscription ends. Deleting removes those records from Operon's database straight away, and Operon asks Vapi to delete its copies of the calls, asking again if Vapi does not complete it.
Operon does not delete a workspace on its own. Until the customer deletes it, the customer's retention limits keep applying: call recordings and transcripts, including Vapi's copies, are deleted after 90 days and conversations after 365 days unless the customer set other limits.
