Zendesk

www.zendesk.comunclaimedrecord 151 · read 2026-09-05 · rules/v1evidence pack ↗
Zendesk did not let our reader in: privacy policy (HTTP 403). Facts below come only from what was readable; anything marked "not stated" may simply be behind that block. We retry daily and rebuild the record the moment the documents open. Work for Zendesk? Claim the profile and send us the text.
Trains on customer data
unclear
Not stated in the documents we could read. An absence here is an unknown, not a no.
Opt-out mechanism
You may manage your email preferences and opt out of marketing communications here or by clicking the “unsubscribe” link at the bottom of our marketing communications.
You may manage your email preferences and opt out of marketing communications here or by clicking the “unsubscribe” link at the bottom of our marketing communications.
privacy policysource ↗confidence 0.50
AI features
none stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Model providers named
none named
Not stated in the documents we could read. An absence here is an unknown, not a no.
Retention
45 days
We will respond to Requests to Delete and Requests to Know within forty-five days unless we need more time, in which case we will notify you, and it may take up to ninety days to respond to your request.
privacy policysource ↗confidence 0.50
Hosting regions
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Subprocessor notice
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.

Downstream

Who's behind Zendesk, as listed in its own subprocessor documents. 0 listed.

Model providers

  • none listed

Hyperscalers

  • none listed

Other subprocessors

  • none listed

Reviewer notes

Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'. no training clause matched

Documents read

Document changes

No document changes yet. These appear when a later reading of a page differs from the previous one; no model involved.

Fact changes

No changes recorded yet. Changes appear here when a later reading differs from an earlier one.

Corrections

No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.

Facts are as stated in Zendesk's public documents on the date read. This is a record, not legal advice. Work for Zendesk? Claim this profile · Something wrong? Request a correction.