Keep audience eligibility, preference and permission basis distinct

Answers Taxonomy · Semantics · Deontics

Audience Segment identifies an addressable eligibility group; Preference records a communication or content choice; Permission Basis records the governed permission or other lawful-basis condition. Consumer State remains relationship context. None of these assertions substitutes for a consumer-level receipt or proves activation is permitted. A Permission Basis rests on exactly one lawful ground and names at least one purpose, because a ground is always a ground for something. A Preference is typed by the kind of choice it states.

What goes wrong without it

These answer three different questions — can this person be reached, how do they want to be reached, and are we permitted to reach them — and collapsing them is how an organisation comes to treat membership of a segment as a consent. Eligibility is an addressing fact, preference is a stated choice, and a permission basis is a condition with a purpose and a jurisdiction. Only the last has anything to say about whether an activation is allowed.

What proves it — 3

Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.

• registry integrityadmission and shape
  Every kind has a valid shape and evidence class, and every row keeps the admission its kind allows: a record names its source, an exemplar names none, and a world record states the public reference it stands on.
• registry integritysemantic distinction
  Vocabulary, constructs, world records, and source-backed records cannot be substituted for one another.
• registry integritydistinct definitions
  No two rows of different kinds are defined in the same words, and no definition restates a field the row already carries, so a distinction the model commits to is carried where a reader meets it and nothing the model knows is stored in two places at once.

Derived from — 8

• European UnionRegulation (EU) 2016/679, Article 6
• IAB Tech LabAudience Taxonomy
• IAB Tech LabGlobal Privacy Protocol
• W3C Data Privacy Vocabularies and Controls Community GroupData Privacy Vocabulary
• European UnionRegulation (EU) 2016/679, Article 7: Conditions for consent
• Kantara InitiativeConsent Receipt Specification 1.1
• IAB EuropeTransparency and Consent Framework v2.2
• Internet Engineering Task Force, 2017RFC 8058: Signaling One-Click Functionality for List Email Headers

Kinds it licenses

Relationships it licenses

targets audience · respects preference · requires permission basis · targets state · rests on · permits purpose · is of type · typically rests on · changes permission · selects state · concerns

Where this model stands

Audience Segment, Preference and Permission Basis are three kinds with separate contracts on Campaign and Tactic, each holding one exemplar: Lapsed customers, Email frequency, Email marketing consent.

Campaign·targets state remains behavioral relevance only, not audience membership or permission.

The six lawful grounds are a closed vocabulary, so a permission basis names the ground it rests on instead of asserting permission as a bare word.

A purpose is named apart from the ground it rests on, because agreement to one purpose is not agreement to another.

In marketing, consent and legitimate interests are the two grounds that usually carry the work, and which of them applies changes what a person may afterwards demand.

Which grounds usually carry which purposes is asserted, hedged as typically, so a reader can walk from a purpose to the ground it tends to rest on rather than take a sentence's word for it.

Consent is a fact before it is a basis. A person grants or withdraws a permission for a purpose on a channel; that is an event at the person grain, captured where it happened, observed by the consent record and counted as the opt-out rate of the channel it governs. So the permission a campaign requires reaches the evidence that it was given, and withdrawing it is shown to be as easy as giving it, which is what the regulation asks the controller to be able to show. No receipt for any one person enters the public graph; the fact's kind does, and the instrument that keeps the receipts.

What it does not claim

No Audience Segment, Preference or Permission Basis record is asserted without a governed source, jurisdiction, purpose and durable identifier.

No Consent Receipt kind is introduced: individual consent evidence belongs in a protected operational system, not this public semantic graph.

Jurisdiction stays unmodelled. Which grounds are even available is a fact about where a record sits, and this model holds one exemplar per kind rather than records, so a jurisdiction edge would have nothing true to point at.

RUL-006