This guide creates a verified data-flow inventory and drafting outline. It is not a legal template and cannot determine obligations, lawful basis, required rights language, or jurisdiction-specific notices.
Finish with
Outcome
A scoped inventory of site features, providers, data, purposes, recipients, retention evidence, controls, owners, and unknowns, followed by a plain drafting outline.
What you need
- Access to the deployed pages, source or tag configuration, hosting settings, forms, embeds, and account features.
- Current first-party records and provider documentation for data use and retention facts.
- People responsible for hosting, site features, privacy decisions, and legal review where required.
- A place to record unknowns without converting them into reassuring assumptions.
The observable problem
A site can add no analytics or forms while its host and network still process request data to deliver and protect pages. Conversely, a short privacy template can list tools that the site no longer uses. Both errors come from drafting before inventory.
Keep scope explicit. “No project-added analytics scripts were found in this reviewed build” is a bounded observation. “We collect no data” is an absolute claim about systems, providers, and future states that a page inspection cannot establish. Recommendations should point to verification owners and evidence, not guessed retention periods.
Invented for instruction
Fictional worked example
Fictional worked example: Cedar Room is an invented static information site. The project adds no form, account, analytics script, advertisement, payment, or media embed. Its host still receives requests needed to send pages, and the project team has not yet verified the provider’s available logs or retention controls.
Before: “We collect absolutely no information about visitors.” After: “This reviewed build does not add analytics, accounts, forms, advertising, payments, or third-party media embeds. The hosting and network services process technical requests to deliver and protect the site. Their exact fields, controls, and retention remain marked for provider-level verification.”
The revision does not pretend that unknown provider behavior is harmless or unlawful. It records the boundary, assigns the hosting owner to verify configuration and primary documentation, and blocks a future contact form from release until the inventory and note are reviewed.
Procedure
Set the reviewed scope
Record the build or release, hostname, date, environments, and pages examined. Distinguish project-added features from hosting, network, email, and security services. List important areas you could not inspect. A privacy note should not silently imply control over systems outside the review.
Inventory features and providers
Check forms, accounts, analytics, advertising, embedded media, payments, comments, search, support tools, consent tools, server logs, and email links. Use source, browser network requests, and configuration where available. Record the provider and owner for each feature, including inactive but deployed code.
Verify data, purpose, recipients, and retention
For each row, name the information involved, why the feature needs it, who receives it, where retention is defined, and which settings the operator controls. Cite current primary records in the internal evidence field. Mark unresolved facts unknown rather than copying a generic period.
Draft in layers a reader can follow
Begin with scope and present features, then explain project-controlled collection, provider-level technical processing, sharing or recipients, retention boundaries, choices, changes, and a real contact only when one is monitored. Use absolute claims only when evidence supports the entire scope.
Review before feature changes ship
Make privacy review a release condition for a new form, embed, analytics tool, account, payment feature, provider, or host. Compare the note against the live network and configuration, obtain appropriate legal review, and preserve the evidence and review date.
Reusable worksheet
| Feature and provider | Data involved | Purpose and recipient | Retention source | Operator control | Evidence | Owner and verified date |
|---|---|---|---|---|---|---|
| Static page delivery; hosting provider | Technical request details, exact fields unknown | Deliver and protect pages; provider receives request | Unknown pending documentation review | Configuration controls unknown | Network and host configuration review needed | Hosting owner; not yet verified |
| Future contact form | Not deployed | Not applicable | Not applicable | Release is blocked pending review | Feature proposal | Product owner; review before release |
Decision rules
- If a material fact is unknown, write unknown in the inventory and assign verification rather than filling the gap with a promise.
- If a provider controls retention, use current provider documentation and verified configuration instead of inventing a period.
- If a form, embed, analytics tool, account, payment feature, provider, or host changes, stop release until the inventory and note are reviewed.
- If the project cannot monitor a contact route, do not publish invented or unattended contact details.
- If legal obligations are uncertain, seek qualified review rather than treating this editorial outline as a legal conclusion.
Limitations and escalation
- The worksheet cannot determine which law applies, legal roles, lawful bases, consent requirements, rights procedures, transfer rules, or required retention.
- Browser inspection can miss server-side processing, dormant code, provider sub-processors, administrative exports, email handling, backups, and access outside the site.
- Provider documentation may describe options rather than the project’s actual configuration. Both documentation and configuration need verification.
Review list
Check the work
- The note identifies the exact build, host, date, and limits reviewed.
- Project-added features and provider-level processing are distinguished.
- Each material data flow has a purpose, recipient, retention source, evidence, and owner or is marked unknown.
- No absolute zero-data claim exceeds the evidence.
- Feature changes trigger review before release and legal questions are escalated.
Review again when
- A new form, embed, analytics tool, account, payment feature, provider, or host
- A provider changes documentation or settings
- The production hostname is connected
- A monitored contact route is added
- A legal or operational owner identifies a new requirement