Zero-Party Data vs Zero Data Protocol
Zero-party data is information a person intentionally provides to an organization—often preferences, intentions or personal context used for personalization. Zero Data Protocol asks a different question: should that information be collected, retained or exploited at all?
Zero-party data and Zero Data Protocol are not equivalent. Zero-party data improves transparency by replacing hidden inference with information knowingly supplied by a person. But it is still collected data. ZDP goes further through Zero Collection, Zero Retention and Zero Exploitation.
What is zero-party data?
Forrester defines zero-party data as information that a customer intentionally and proactively shares with a brand. It can include preference-center choices, purchase intentions, personal context and instructions about how the customer wants to be recognized.
The term is mainly used in marketing and customer-experience systems. Instead of silently inferring that someone prefers a particular product, a company can ask the person directly through a survey, quiz, preference center or onboarding question.
The word “zero” does not mean zero collection. It refers to the direct relationship between the person and the organization receiving the declared information.
Common zero-party data examples
How organizations collect and activate it
Zero-, first-, second- and third-party data
| Data type | How it is obtained | Typical examples | Main concern |
|---|---|---|---|
| Zero-party data | Intentionally supplied by the person | Preferences, intentions, context, survey answers | Purpose, retention and downstream activation |
| First-party data | Observed through the organization’s own channels | Clicks, purchases, app activity, service history | Tracking, profiling and inference |
| Second-party data | Another organization’s first-party data is shared | Partner audience or transaction information | Transparency, provenance and compatible purpose |
| Third-party data | Acquired from outside brokers or aggregators | Demographics, interests, intent signals | Accuracy, consent, legality and uncontrolled circulation |
The categories describe provenance, not automatic privacy quality. Directly supplied information can be sensitive, persist for years, spread across many systems and support intensive profiling.
What zero-party data improves
These benefits depend on restraint. Forrester recommends short, simple experiences with a clear value exchange. Asking too many questions turns a transparent interaction into another form of data extraction.
What zero-party data does not guarantee
Zero-party data can also reveal sensitive traits. Health goals, political interests, financial concerns, family circumstances or religious preferences do not become low-risk merely because the individual typed them into a quiz.
What Zero Data Protocol adds
Zero Data Protocol evaluates whether a system can provide its function without creating an enduring personal-data dependency:
A ZDP-oriented service can still ask a question. The difference is that it prefers an immediate, local or session-bound answer over an ever-growing centralized customer profile.
Zero-party data vs ZDP
| Dimension | Zero-party data | Zero Data Protocol |
|---|---|---|
| Primary objective | Obtain accurate declared information for personalization and engagement | Remove unnecessary personal-data dependence from system design |
| Meaning of “zero” | Information comes directly from the customer rather than another data party | Zero unnecessary collection, retention and exploitation |
| Starting point | Ask the customer for useful information | Ask whether the information is necessary at all |
| Collection | Intentional and proactive disclosure | Avoid collection unless functionally required |
| Identity | Frequently linked to a known customer or prospect | Prefer anonymous, local or unlinkable operation where possible |
| Retention | Often stored in profiles, preference centers and customer-data platforms | Persistent retention challenged at every layer |
| Use | Personalization, recommendations, segmentation and marketing | Use restricted to the declared and necessary function |
| Secondary exploitation | Possible unless purpose and governance controls prevent it | Unrelated exploitation is structurally rejected |
| Type | Marketing and customer-data category | Independent architectural framework |
| Relationship | Zero-party data can reduce covert inference, but it supports ZDP only when collection, retention and use remain strictly minimized | |
The decisive difference: permission to share versus necessity to know
Zero-party data emphasizes how information is obtained: the person knowingly provides it rather than having it inferred or purchased from elsewhere.
ZDP emphasizes whether the system needs the information, how long it must exist and whether it can be used beyond the immediate purpose. A transparent question can still create an unnecessary permanent record.
In one sentence: zero-party data replaces guessing with asking; Zero Data Protocol asks whether the system needs to remember the answer.
Three more structural ways to use a preference
A ZDP-oriented zero-party data checklist
- Justify every question. Remove questions that are merely interesting rather than necessary for the promised result.
- Explain the immediate value. State what the person receives in return and avoid manipulative incentives.
- Separate optional from required. Do not make personalization questions a hidden condition for basic service access.
- Minimize identity linkage. Use anonymous, session-bound or local preferences whenever a named profile is unnecessary.
- Limit recipients. Prevent automatic distribution to every CRM, CDP, analytics platform and advertising partner.
- Set expiration dates. Preferences and intentions should be refreshed or deleted when they are no longer reliable.
- Provide control. Let people inspect, change, withdraw and delete what they intentionally shared.
- Block secondary exploitation. Do not turn a useful answer into unrelated training data, behavioral scoring or cross-context profiling.
Frequently asked questions
What is zero-party data?
It is information a person intentionally and proactively gives to an organization, such as preferences, intentions, personal context or instructions about the desired experience.
Why is it called zero-party data?
The term distinguishes directly declared information from first-party behavioral observations and data received from second or third parties. It does not mean that zero data is collected.
Is zero-party data always anonymous?
No. It is frequently stored inside an identified customer, loyalty, CRM or marketing profile.
Is voluntarily supplied data the same as legal consent?
Not automatically. Valid consent and other legal bases depend on applicable law, purpose, information provided, freedom of choice, withdrawal and the specific processing involved.
Can zero-party data support ZDP?
Yes, when asking directly replaces hidden surveillance and when the answer is minimized, narrowly used and quickly deleted. It is not sufficient by itself.
Is zero-party data the same as Zero Data Protocol?
No. Zero-party data is a data-source category. ZDP is a structural framework based on Zero Collection, Zero Retention and Zero Exploitation.
Editorial notice: Forrester, Salesforce, Tealium and their terminology or products are cited for identification and independent comparative analysis only. No affiliation, endorsement or equivalence with Zero Data Protocol is claimed. Privacy obligations depend on the actual data, purposes, jurisdiction and implementation; obtain appropriate professional advice where required.