Tabbly

Trust Center/Data Processing Addendum

DPA · On request

Data Processing Addendum

A Data Processing Addendum (DPA) sits beside Tabbly’s Terms and defines how personal data is processed when you use AI voice agents—available when your legal or procurement team requests it.

Legal & procurement Contractual opt-in
What you get
  • Controller / processor roles
  • Subprocessor notice
  • Security & deletion terms
Request this for my account

What the DPA is for

Most enterprise and regulated buyers need more than a public Privacy Policy. A DPA records the processor relationship in contract form: who decides purposes, what categories of data may be processed, how long data is kept, which subprocessors are used, and how deletion or return works at the end of the engagement.

Tabbly provides a DPA for customers who request one. We can also review a customer-paper DPA subject to mutual agreement.

Typical clauses customers ask us to cover

Roles

Customer as controller / data fiduciary; Tabbly as processor / service provider for in-scope personal data, as applicable under the governing law.

Security

Technical and organizational measures, confidentiality, and cooperation on incidents within agreed timelines.

Subprocessors

Disclosure of material subprocessors used for telephony, STT, LLM, hosting, and support—plus notice of material changes where required.

Deletion & return

Return or deletion of personal data at termination, subject to legal retention needs and your product configuration.

Usually in scope

  • Account user identity and workspace administration data
  • Call-related personal data you submit or generate in Tabbly
  • Transcripts / recordings if your retention settings keep them
  • Support tickets that include personal data you share with us

Usually out of Tabbly’s DPA scope

  • Your public website analytics you run independently
  • CRM systems you connect where you are the direct customer of that vendor
  • Employee HR systems unrelated to Tabbly services
  • Processing you perform after exporting data out of Tabbly

How the DPA relates to other Trust Center packs

The DPA is the contractual backbone. Many customers attach it to GDPR, DPDP, local residency, and/or zero data retention. Those packs are separate optional commitments and only bind once agreed for your account.

Relationship to Terms & Privacy

Our public Terms & Conditions and Privacy Policy continue to apply. Where a signed DPA conflicts with those documents for in-scope personal data processing, the DPA generally controls for that customer relationship, as stated in the executed agreement.

Common questions

Do you sign customer paper DPAs?

Often yes for enterprise deals, after legal review. Share your template early so we can align timelines with procurement.

Can the DPA cover multiple legal entities?

Yes—affiliate schedules or multi-entity exhibits are common. Tell us which entities will use Tabbly.

Is a DPA required to start a pilot?

Not always. Many pilots start under standard Terms; the DPA is executed before production / regulated workloads go live.

Last updated: October 2026 · Part of the Tabbly Trust Center

Next step

Request these controls for your workspace

Tell us which documents you need, your region, and your go-live timeline. We will confirm what can be enabled for your plan.