Tracking technologies
Identify analytics, advertising, CMP and other third-party technologies present in the tested website journeys.
Technical facts for your privacy policy
Privacy Policy Technical Inventory
When a privacy policy is being updated, the difficult technical question is often not how to phrase the document. It is determining what the website actually does. PlainPrivacy documents the observable technologies, tracking behavior and consent controls so your lawyer or privacy adviser has better technical evidence to work from.
Technical assessment and implementation support. PlainPrivacy does not provide legal advice.
Audit method
01
Observe the live implementation
02
Compare consent states
03
Document evidence and priorities
04
Implement and retest when requested
Scope
Technical evidence for policy work
PlainPrivacy does not decide what the law requires your policy to say. We establish the technical facts behind the website and flag mismatches between the published documentation and the implementation we can observe.
Cookie & storage inventory
Document observed cookies and browser storage and compare them with the site’s current disclosures.
Third-party destinations
Record third-party domains and visible network activity that can help identify vendors receiving browser-side data.
Consent behavior
Verify what happens before a choice, after accept/reject and when consent is later changed.
Regional configuration
Where relevant, document technical differences in regional banners, opt-outs and consent behavior.
Documentation mismatch
Highlight technologies or behaviors observed on the site that are missing, stale or inconsistent in current cookie/privacy documentation.
Evidence
What the review is based on
Findings are grounded in observable website behavior and the configuration available within the agreed scope.
- Observed technologies and vendors
- Cookie/storage inventory
- Third-party request evidence
- Consent-state comparisons
- Regional behavior notes where scoped
- Clear separation between technical findings and legal conclusions
Deliverables
What you receive
The output is designed to be usable by business owners, developers, agencies and privacy advisers.
- Technical data/vendor inventory
- Cookie and tracker evidence
- Documentation mismatch list
- Questions to take to privacy counsel
- Implementation recommendations
- Optional remediation and retest
How it works
Investigate first. Change only what the evidence supports.
The initial review establishes the current behavior. Recommended changes are then scoped, implemented only when agreed, and retested afterward.
Review
Confirm the platforms, regions, consent system and tracking stack that need to be tested.
Test
Run controlled browser journeys and inspect consent, storage, requests and tracking behavior.
Prioritize
Separate working controls from technical issues and identify the fixes that matter most.
Fix & verify
When implementation support is requested, apply agreed changes and repeat the relevant tests.
Related technical services
Go deeper where your stack needs it.
Request a technical review
Need evidence of what your website is actually doing?
Tell us about the website, platform, consent setup and current concern. We will suggest an appropriate technical scope.
Request Your Technical Audit