Preview how Auditzo documents observable cookies, browser storage, third-party requests, trackers, pixels and privacy-review signals in a structured technical report.
This sample focuses on website privacy and tracking observations. It is not a WCAG accessibility report, legal advice or compliance certification.
A practical privacy report should explain what was observed, where it appeared, what the tested scope included and what still requires deeper review.
The sample shows how cookies, storage, scripts and third-party requests can be documented from a recorded website session.
Report wording separates the tested environment and observed page state from untested pages, journeys or consent interactions.
Findings can connect observed activity with affected pages, domains, technologies and practical review notes.
Auditzo reports technical observations for business, privacy and counsel review without certifying legal compliance.
The sample demonstrates how automated initial-state observations can be organized for business, privacy, engineering and counsel review.
Review cookies and storage signals observed during the recorded automated session.
See external domains and request activity observed during page loading.
Identify analytics, advertising and marketing technologies visible in the tested session.
Understand what the automated scanner observed before any consent-banner interaction.
Compare observed technologies with visible privacy and cookie disclosures where relevant.
Use the report to identify what requires technical remediation, internal review or deeper manual testing.
The report is structured to help readers move from recorded scope and observed website activity into clear technical findings and practical next steps.
It does not claim that every cookie, tracker or legal issue has been identified. It documents what was visible in the tested automated session.
Download Sample Report| Report section | What it helps review |
|---|---|
| Report scope and environment | The tested URL, browser session, location or environment details, scan state and important limitations. |
| Executive summary | A high-level overview of the most important observed cookies, trackers, third-party requests and review signals. |
| Cookie and storage observations | Observed cookie names, source domains, duration context and relevant browser-storage activity. |
| Third-party domains and requests | External services, request destinations and third-party technologies visible during the recorded session. |
| Tracker and pixel observations | Analytics, advertising, retargeting or marketing technologies identified in the tested state. |
| Consent and disclosure review notes | Initial-state observations and areas where deeper consent-state or privacy-disclosure review may be appropriate. |
| Findings and next steps | Technical observations, review priority, remediation direction, escalation options and documented limitations. |
The sample report demonstrates structured automated reporting. Consent-state interaction and downloadable supporting evidence belong to a separately scoped manual audit.
A completely automated, no-interaction review of the initial website state. It provides expanded structured observations beyond the free scan.
A separately scoped human-reviewed engagement for teams that need consent-state comparisons, selected journeys and supporting evidence files.
Need to understand how Auditzo defines scope, separates review paths and verifies findings?
Review Auditzo's audit methodologyA useful report should provide more context than a cookie name alone. It should help the reader understand the source, observed technology, possible purpose and next review step.
The examples are illustrative. Actual findings depend on the tested website, environment, page state and selected audit service.
Explore Cookie Audit Tool| Cookie or signal | Provider | Type | Possible purpose | Review note |
|---|---|---|---|---|
| analytics_id | analytics.example.com | Third-party cookie | Analytics / measurement | Review timing, purpose and disclosure context. |
| ad_pixel | ads.example.com | Third-party request | Advertising / retargeting | May require deeper consent or opt-out review depending on implementation and context. |
| session_id | yourdomain.com | First-party cookie | Session / functionality | Usually reviewed differently from advertising or analytics technologies. |
| marketing_tag | tag.example.net | Third-party script | Marketing automation | Review against implementation purpose, consent configuration and visible disclosures. |
Deliverables depend on the selected plan and supported scan path. The Automated Detailed Review provides a structured report, not a downloadable raw evidence package.
A concise overview of the automated review scope, key observations and recommended follow-up.
Observed cookies with source, duration and possible purpose context where available.
Browser-storage activity visible to the automated review during the initial website state.
External domains, services and request activity observed during the recorded session.
Analytics, advertising and marketing technologies identified in the tested environment.
Areas where observed technology and visible privacy or cookie disclosures may require review.
Structured observations that help teams decide which items require deeper investigation first.
Practical follow-up suggestions for website, marketing, privacy or engineering teams.
Clear boundaries explaining the tested state and what the automated report does not establish.
Findings should describe observable behavior and why it may require technical, privacy or counsel review. They should not be presented as automatic legal violations.
An analytics or marketing request was visible before any consent-banner interaction. This is an initial-state technical observation that may require deeper review.
The tested page sent a request to an external domain. The report can document the domain, affected page and observed request context.
A cookie appears related to analytics, advertising or personalization, but its exact purpose and consent treatment require implementation context.
A third-party technology was observed, but it may not be clearly described in the visible privacy or cookie disclosures.
Observed advertising or sharing-related technology may require CCPA/CPRA review depending on the business, data use and opt-out implementation.
Certain website requests may require review where CIPA-related theories are relevant. Auditzo documents technical behavior and does not make legal determinations.
Auditzo records the tested state, observes technical activity, organizes findings and documents the limitations of the automated review path.
Document the public page, environment and initial/no-interaction condition used by the automated review.
Identify visible cookies, storage, third-party requests, trackers, pixels and embedded services.
Group observations by technology, affected area, technical context and recommended review priority.
Explain that the report reflects a point-in-time automated session and does not include manual interaction testing.
A manual audit can compare initial, Accept and Decline behavior across selected pages and journeys, with screenshots, HAR/request evidence, cookie and storage comparisons and other agreed supporting files.
Explore the manual evidence auditThe report format supports teams that need clearer technical observations before making privacy, remediation, engineering or legal decisions.
Need a clearer view of cookies, trackers and third-party services before planning remediation or deeper review.
Need a structured report format for client conversations, technical handoff and follow-up recommendations.
Need visibility into analytics, advertising pixels, retargeting scripts and marketing-tag behavior.
Need affected pages, technologies and technical context to prioritize investigation and implementation changes.
Need structured technical observations as input to privacy review, vendor assessment and remediation planning.
Need documented technical behavior that can support legal analysis without replacing legal judgment.
These boundaries protect buyers from confusing automated technical observations with human-reviewed evidence or legal conclusions.
Review Audit MethodologyStart with an automated privacy scan or choose a manual evidence audit when you need consent-state interaction, selected journeys and supporting evidence files.
Move from sample-report review into automated testing, manual evidence collection, remediation, methodology or a separate accessibility review.
Generate an expanded automated initial-state report without manual banner interaction or downloadable raw evidence files.
Add human-reviewed consent states, selected journeys and supporting technical evidence files.
See how Auditzo separates automated observations, manual evidence review and accessibility verification.
Review the separate format used for human-verified WCAG accessibility findings and remediation guidance.
Move from observed tracking concerns into implementation review, technical fixes and relevant retesting.
See how initial, Accept and Decline states were compared across product, cart and checkout journeys.
Start with an automated scan, compare review options or discuss a deeper manual evidence scope with Auditzo.
Auditzo provides technical findings and evidence-oriented observations. It does not provide legal advice or certify compliance.