Zendesk · Zendesk Privacy Policy · View original document ↗

Controller vs. Processor Distinction

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time Zendesk changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Zendesk Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

Get the weekly research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.

Document Record

What it is

This notice applies only to data where Zendesk controls the purpose of processing; data processed within Zendesk's products on behalf of business customers (Subscribers) is excluded, and affected individuals are directed to contact those Subscribers directly.

This analysis describes what Zendesk's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision defines the scope of Zendesk's privacy obligations under this notice, excluding data processed on behalf of Subscribers and disclaiming responsibility for Subscriber data practices. Compliance teams engaging Zendesk as a vendor must assess Subscriber obligations separately, including reviewing the Zendesk Data Processing Agreement to understand the allocation of data controller and processor responsibilities.

Consumer impact (what this means for users)

Under this clause, individuals whose personal data is processed within a Zendesk Subscriber's support or service platform are not covered by this notice and must direct data rights requests to the Subscriber organization. The agreement states Zendesk is not responsible for the privacy or data security practices of its Subscribers.

Cross-platform context

See how other platforms handle Controller vs. Processor Distinction and similar clauses.

Compare across platforms →

Monitoring

Zendesk has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
This Notice only applies when Zendesk is the Controller of personal data (example: Zendesk website visitors' personal data and business-to-business contact data). Zendesk is a Processor, not a Controller, of personal data that we process on behalf of our Subscribers when they use Zendesk products and Services. For clarity, this means that this Notice does not apply to where Zendesk processes personal data as a processor in its products and Services. If you have questions related to how a Zendesk Subscriber utilizes your personal data, please contact them directly. We are not responsible for the privacy or data security practices of our Subscribers.

Excerpt from Zendesk's Privacy Policy

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1. REGULATORY LANDSCAPE: The Controller versus Processor distinction directly implicates GDPR Articles 4, 24, 26, and 28, as well as equivalent provisions under UK GDPR, CCPA, and LGPD. Supervisory authorities including EU data protection authorities and the UK ICO enforce this distinction, and mischaracterization of the Processor role can result in regulatory exposure for both parties. 2. GOVERNANCE EXPOSURE: High. The disclaimer of responsibility for Subscriber data practices creates a gap in data subject rights fulfillment for individuals whose data is processed within Zendesk products. If a Subscriber lacks adequate privacy infrastructure, data subjects may be unable to exercise rights effectively, and regulators may examine whether Zendesk's DPA with Subscribers adequately addresses this. 3. JURISDICTION FLAGS: Heightened exposure in the EU and EEA, where GDPR imposes specific obligations on both controllers and processors and requires documented allocation of responsibilities. UK and Brazilian frameworks impose similar requirements. The adequacy of Subscriber DPAs for GDPR Article 28 compliance is a primary due diligence consideration. 4. CONTRACT AND VENDOR IMPLICATIONS: B2B procurement teams contracting with Zendesk must confirm the applicable DPA covers all data processing activities within the Zendesk products they use, and that Subscriber obligations for data subject rights are operationally implementable. The notice's disclaimer shifts compliance responsibility to Subscribers, which may not be acknowledged in all procurement contracts. 5. COMPLIANCE CONSIDERATIONS: Legal teams should map which data flows are governed by this notice versus the Zendesk Customer Agreement and DPA. For Subscribers, this requires confirming that their own privacy notices and data subject rights procedures account for data processed within Zendesk products. Contract amendments may be warranted to clarify responsibilities where the Controller versus Processor boundary is ambiguous.

Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Start Professional · $99/mo Start with Monitor · $29/mo

Applicable agencies

  • FTC
    The FTC has jurisdiction over Zendesk's DPF compliance and consumer protection obligations related to privacy disclosures, including the accuracy of the Controller versus Processor characterization.
    File a complaint →

Provision details

Document information
Document
Zendesk Privacy Policy
Entity
Zendesk
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-016066
Document ID
CA-D-00639
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
61bead77ffc0694e673595ad8660fbe7d6a546799b687496b3755d40d3acc968
Analysis generated
July 9, 2026 09:29 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Zendesk
Document: Zendesk Privacy Policy
Record ID: CA-P-016066
Captured: 2026-07-09 09:29:52 UTC
SHA-256: 61bead77ffc0694e…
URL: https://conductatlas.com/platform/zendesk/zendesk-privacy-policy/provision/CA-P-016066/controller-vs-processor-distinction/
Accessed: July 23, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
Start Professional · $99/mo Start with Monitor · $29/mo

Frequently Asked Questions

What does Zendesk's Controller vs. Processor Distinction clause do?

This provision defines the scope of Zendesk's privacy obligations under this notice, excluding data processed on behalf of Subscribers and disclaiming responsibility for Subscriber data practices. Compliance teams engaging Zendesk as a vendor must assess Subscriber obligations separately, including reviewing the Zendesk Data Processing Agreement to understand the allocation of data controller and processor responsibilities.

How does this clause affect you?

Under this clause, individuals whose personal data is processed within a Zendesk Subscriber's support or service platform are not covered by this notice and must direct data rights requests to the Subscriber organization. The agreement states Zendesk is not responsible for the privacy or data security practices of its Subscribers.

Is ConductAtlas affiliated with Zendesk?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Zendesk.