EU GDPR
Map your processing and put data rights, safeguards and breach decisions into daily operations.
Privacy and Electronic Communications Regulations (PECR)
Test what your site stores or reads on a device, then document when consent or an exception applies.
Organizations using storage or access technologies on user devices or sending covered electronic marketing in the UK.
A tag inventory, a consent and exception decision for each purpose, and evidence that choices work.
Start with what the tag actually does. A provider’s label does not settle whether a specific storage or access purpose qualifies for a PECR exception.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
UK cookie and marketing rules kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Find what runs in a clean session · Web engineering + privacy lead [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A publisher runs a cart cookie and two analytics tags. The engineer records a fresh visit, a refusal and a withdrawal. The privacy lead checks each tag’s actual purpose and any claimed exception, then approves the release only after the network traffic matches the recorded choices.
Check the separate rules for any personal data collected when the tag runs.
Checklist, instructions and 8 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Find what runs in a clean session | Web engineering + privacy lead | Before adding or changing tags | Set a start date | Cookie inventory; Data and SDK map | Open |
| Check the rule for each purpose | Privacy counsel + product | Before enabling each use | Set a start date | Applicability matrix; Privacy notices | Open |
| Verify choices in the browser | QA + marketing engineering | Before deployment and after tag changes | Set a start date | Preference signal tests; Consent records | Open |
| Review email and text marketing separately | Marketing operations + privacy | Before sending a campaign | Set a start date | Consent and purpose record; Request log | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Capture first-load network activity and storage across pages and login states. Record who uses each identifier, purpose, lifetime and destination.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reproduce the behavior from the recorded URL, test state and destination.
Give the approved inventory and open defects to privacy, marketing and release owners.
Fictional details. Use the same fields with evidence from your work.
An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.
Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.
Work through the conditions for applicable exceptions. Record any duty to inform or offer a simple objection. Gate other covered technologies on valid consent.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Test first visit, accept, reject, fine-grained choices and withdrawal. Inspect storage, network requests and server-side forwarding. Log the exact pages and browser used.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
You can demonstrate what the person saw, how they acted and how the decision was honored.
Provide the consent log and tested withdrawal flow to privacy operations and downstream system owners.
Classify recipients and messages. Document applicable consent or soft opt-in conditions, test unsubscribe and keep suppression lists current.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.