Know what is collecting data before writing the policy.
A privacy notice cannot be accurate if nobody knows which scripts, vendors, forms and backend services receive information. The engagement starts with an inventory and collection-point map.
Privacy & tracking implementation
Match the disclosures and controls to what the website actually loads.
We map forms, vendors, pixels, analytics, embeds, payment tools and marketing technology, then turn that inventory into practical notices and preference behavior. Applicability is validated before jurisdiction-specific controls are treated as required.
What you receive
- Vendor and tracker register
- Privacy Notice generated from actual practices
- Cookie & Tracking Notice
- Privacy Choices language and workflow
- Notice-at-collection copy when selected
- Consent/preference implementation guidance
- Form disclosure and link placement review
- Re-test against the deployed website
California & GPC
Privacy controls should follow applicability, not guesswork.
For businesses subject to California opt-out obligations, recognized opt-out preference signals such as Global Privacy Control can matter. The platform flags signals and produces implementation material, but the business facts determine whether a particular right or notice applies.
UK / EEA
Optional tracking needs jurisdiction-aware handling.
For UK/EEA audiences, storage/access technologies and consent rules can require a different implementation than a U.S.-only site. The v3 intake records that scope so generated deliverables do not blindly mix regimes.
Human implementation available
Unsure what your pixels and plugins are actually doing?
Start with the free scan, then we can inventory the live stack and build the right notices and controls.