Cookie and similar-technology notice — launch draft
[NEEDS HUMAN CHECK] This notice must match an actual audit. A template cannot establish which cookies an eventual embed, host, analytics product or advertising tool will use.
The intended local preview contains no operational signup embed, advertising tracker or analytics pixel and collects no signup data. Hosting on a real service later may involve logs and security technologies. Confirm the exact setup before publication.
Initial launch preference: avoid non-essential tracking. Do not load optional marketing/analytics technologies merely because a visitor opened the site. Where PECR requires consent, obtain it before storage/access, with clear choices, easy refusal and withdrawal. Do not treat continuing to browse as consent. Apply current exemptions only after checking the actual purpose and conditions, not the vendor's label.
Before launch record: technology name; provider; purpose; information accessed/stored; expiry; first/third-party role; essential/exemption assessment; consent requirement; and how to withdraw. Audit newsletter forms, email tracking pixels and affiliate plugins, not just traditional browser cookies.
A plain outbound affiliate link and an on-site tracking plugin are different implementations. Check what the chosen link method does; do not assume every affiliate link automatically means a cookie was stored by this site. The merchant's own technologies apply after visiting its site, subject to its policies.
[NEEDS HUMAN CHECK] Insert the real audit inventory or a verified statement of no such technologies; remove conditional wording once implementation is known. Add a working preference-control route only if implemented. No fake “all cookies rejected” badge or non-functional consent control.