Understand how Auditzo handles audit reports, screenshots, HAR/network evidence, cookie and storage exports, monitoring snapshots and other supporting materials across automated and manually scoped review paths.
This page is a practical buyer-clarity page. It explains evidence expectations and boundaries, but it does not replace Auditzo’s Privacy Policy, Terms, Cookie Policy or any custom agreement.
Audit outputs can include report files, screenshots, request-level context, cookie and storage observations, accessibility reproduction notes, monitoring snapshots or remediation verification notes. Buyers should understand what may be generated, what is included by default and what requires a manually scoped engagement.
Screenshots, HAR/network files, cookies, storage exports and request logs can reveal more context than a normal report summary.
Automated reports, Manual Evidence Audits, WCAG reviews, monitoring and verification work do not create the same evidence outputs.
Auditzo aims to keep evidence only for the period needed to deliver, support, review or verify the agreed audit work.
Evidence access should be limited to authorized Auditzo reviewers, system processes and approved client recipients based on the selected path.
The most important distinction: automated reports are built for structured initial visibility. Raw evidence handoff, deeper screenshots, HAR/network evidence and cookie or storage comparisons belong to manually scoped evidence work where agreed.
Self-generated reports are designed for quick initial visibility. They do not include human verification, Accept/Decline interaction testing or raw evidence handoff by default.
Manual audits are scoped human-reviewed engagements. They can include deeper evidence files and handoff materials where agreed in scope.
Accessibility reviews focus on human-verified accessibility findings, reproduction context and remediation guidance within the agreed WCAG-oriented scope.
Monitoring and post-remediation verification create comparison records for selected signals or findings, not unlimited re-audits of the entire website.
A self-generated automated report is not the same as a manually scoped raw evidence package. This table is designed to prevent confusion before ordering or sharing results with a team.
“Where scoped” means the file or evidence type must be included in the selected plan, proposal, order or custom engagement terms.
| Artifact | Automated reports | Manual / custom scope |
|---|---|---|
| PDF / HTML report Used for review, sharing and remediation planning. |
Yes, based on selected automated plan | Yes, where part of the agreed deliverable |
| Screenshots May show banner states, page context, findings or accessibility evidence. |
Limited report visuals where available | Yes, where scoped |
| HAR / network evidence Can include request URLs, domains, timing, headers or request context depending on capture. |
Not provided as raw handoff by default | Yes, where scoped |
| Cookie and browser storage exports Used for state comparison such as initial, Accept, Decline or preference states. |
Initial-state observations may appear in report | Yes, where scoped |
| Findings register / evidence index Helps connect observations to evidence files and remediation notes. |
Automated report structure only | Yes, where scoped |
| Raw evidence package Provided only when included in the Manual Evidence Audit or custom engagement scope. |
No, not included by default | Yes, where scoped |
| Monitoring snapshots Used to compare changes over time, not to replace a manual evidence audit. |
Only if monitoring is selected | Only if included in monitoring or follow-up scope |
| Verification notes Used after remediation to document whether selected findings appear changed. |
No, unless a verification workflow is selected | Yes, where scoped |
Auditzo’s retention approach should stay tied to the product path, paid plan, manual scope, monitoring setup or custom agreement. Exact retention windows should be confirmed in the order, proposal or engagement scope before relying on them.
Retention depends on the selected report path, paid plan, manual engagement scope, monitoring setup or custom agreement.
Auditzo should not retain raw evidence longer than needed for delivery, support, verification or agreed client use.
Access should be limited to the people and systems needed to produce, deliver, support or verify the audit work.
Clients can ask about removal of report files or evidence materials, subject to operational, backup, billing, security and legal record constraints.
Manual evidence work is most useful when the testing scope is clear and the client avoids sharing unnecessary sensitive information. Use test flows wherever possible.
This page helps buyers understand audit evidence handling in practical terms. Formal legal terms should still be reviewed through Auditzo’s policy pages and any signed agreement.
If your team needs screenshots, HAR/network evidence, cookie or storage comparisons, evidence indexes or raw evidence handoff, confirm those expectations before the audit starts.
Do not assume that every report includes every evidence file. Raw evidence handoff, consent-state comparisons, screenshots and HAR/network materials should be explicitly scoped when needed.
Auditzo provides technical evidence and observations for review. It does not provide legal advice, compliance certification or guarantees.
These pages explain scope, methodology, manual evidence work, sample outputs, monitoring and verification after remediation.
Understand what each Auditzo review path includes, excludes and can support.
Review audit scopeUse scoped human-reviewed evidence work when screenshots, HAR files, cookies or storage comparisons matter.
Explore manual evidence auditsPreview how Auditzo structures privacy and tracking observations in a report.
View sample reportRecheck selected findings after fixes and document observed status changes within scope.
View verification scopeTrack meaningful changes in observed cookies, storage, scripts and third-party request signals over time.
View monitoringSee how Auditzo defines scope, observes website behavior and separates automated from manual review.
View methodologyCommon questions about automated reports, manual evidence files, HAR/network evidence, deletion requests and retention expectations.
Start with an automated scan for quick visibility, or request a Manual Evidence Audit when screenshots, network evidence, consent-state comparison or raw supporting files matter.