Zero-party data is information that a customer intentionally and proactively shares with a brand, such as preferences, purchase intentions, sizes, interests or communication choices. In privacy in marketing, it is distinguished from data that is observed or inferred, because the person knows what they are giving and why.
The term emerged as marketers prepared for the decline of third-party cookies and stricter consent rules. Its appeal is accuracy and transparency: a stated preference is often more reliable than one inferred from browsing behavior. It is still personal data, however, and enjoys no special exemption under privacy law.
How zero-party data is collected
Zero-party data is gathered through explicit interactions in which the customer answers a question or sets a preference. The value exchange is usually immediate: the person shares information to receive better recommendations, relevant offers or a tailored experience.
| Method | Data typically collected | Value offered to the customer |
|---|---|---|
| Product quizzes | Skin type, style, budget, use case | Personalized product recommendations |
| Preference centers | Topics, channels, frequency | Fewer and more relevant messages |
| Onboarding questions | Goals, experience level, interests | Tailored first experience |
| Surveys and polls | Opinions, satisfaction, intentions | Influence over products and service |
| Profile fields | Sizes, birthday month, household details | Faster checkout, occasion offers |
| Wish lists and alerts | Desired products, price thresholds | Notifications when items are available |
Good collection follows progressive profiling: ask a few questions at a time, at moments when they are relevant, rather than presenting a long form at sign-up. This approach supports both conversion and data minimization.
Zero-party data compared with first-party and third-party data
The data categories differ by how the information is obtained and how much the person is aware of it. Many practitioners treat zero-party data as a subset of first-party data with a distinct origin, which is the more precise view.
| Category | Source | Customer awareness | Typical reliability |
|---|---|---|---|
| Zero-party data | Stated directly by the customer | High, actively provided | High for preferences, can age quickly |
| First-party data | Observed on own channels | Moderate | High for behavior, weaker for intent |
| Second-party data | Another company’s first-party data shared by agreement | Low | Depends on partner quality |
| Third-party data | Aggregated by data brokers | Very low | Variable, often inferred |
Stated data has its own weaknesses. People may give aspirational answers, skip questions or change their circumstances. The strongest marketing programs therefore combine stated preferences with observed behavior while respecting the boundaries the customer set.
The categories also differ in regulatory exposure. Third-party data depends on consent collected by someone else, which the marketer often cannot verify, while zero-party data is collected directly under the brand’s own notice. That direct relationship makes it easier to prove what the customer was told and to honor withdrawals and corrections promptly.
Privacy obligations for zero-party data
A common misconception is that voluntarily shared data needs no further legal basis. In fact, the GDPR and similar laws apply in full: the organization must identify a legal basis for each purpose, explain the use transparently and honor data subject rights.
| Purpose | Typical legal basis | Note |
|---|---|---|
| Showing quiz results on screen | Contract or legitimate interests | Directly requested by the user |
| Saving answers to the customer profile | Consent or legitimate interests | Must be clearly explained at collection |
| Personalized marketing emails | Consent | ePrivacy rules often require opt-in |
| Sharing with advertising partners | Consent | Must be specific and separate |
| Health or religion-related answers | Explicit consent | Special category data under Article 9 |
Quiz questions about skin conditions, diet or pregnancy can easily reveal health information. Such questions should be avoided or handled as special category data, with explicit consent and stricter retention rules.
Using zero-party data well
Zero-party data creates an implicit promise: the customer expects the information to be used for the benefit they were offered. Using it in unexpected ways damages trust faster than misuse of observed data, because the customer remembers sharing it.
- Ask only what you will use, and use answers visibly within a short time.
- Let customers view and edit their answers in a preference center.
- Set retention and refresh rules, since preferences such as sizes or goals change.
- Keep stated data separate from inferred segments so consent choices remain traceable.
- Connect it with consent mode and cookieless measurement strategies rather than using it to rebuild cross-site tracking.
Measurement also deserves attention. Because zero-party data is collected in small, deliberate interactions, its value shows up in engagement, conversion and retention of the customers who shared it rather than in reach. Teams should compare personalized journeys against a holdout group that receives generic content, so that improvements can be attributed to the stated preferences and not simply to the fact that engaged customers answer quizzes more often.
Common mistakes with zero-party data
The typical failures are over-collection, purpose drift and weak transparency. The table pairs them with practical fixes.
| Mistake | Consequence | Fix |
|---|---|---|
| Long mandatory questionnaires | Abandonment and false answers | Progressive, optional questions |
| Quiz answers sold to partners | Loss of trust and unlawful sharing | Separate consent or no sharing |
| Answers never updated | Irrelevant offers | Periodic preference prompts |
| Treating stated data as anonymous | Ignored rights requests | Include it in access and erasure processes |
Explained without jargon
Zero-party data is information you choose to tell a company yourself, such as your shoe size, favorite topics or how often you want to hear from them. The company does not guess it from your clicks; you hand it over on purpose.
It is like telling a waiter about your allergy instead of letting the restaurant work it out from your past orders. The waiter gets accurate information, and you expect it to be used only to serve you better. A company that respects that expectation earns more trust, while one that misuses what you told it loses it quickly.
A typical use case
An outdoor clothing retailer replaces part of its retargeting budget with a three-question gear finder on its website. Visitors choose their main activity, typical climate and budget range, and the site recommends jackets and footwear accordingly.
At the end, an optional checkbox offers to save the answers and send seasonal recommendations by email. The privacy notice next to it explains that answers are stored in the customer profile, used only for product suggestions and never shared with advertising partners. Customers can edit or delete their answers in the account preference center, and answers older than eighteen months trigger a short refresh prompt.
Over the following season, emails built on stated activities receive noticeably more engagement than generic newsletters, and unsubscribe requests fall, because recipients receive content matching what they actually said they wanted.