Retention exists to keep reports reproducible, support billing and dispute evidence, monitor regressions and let customers audit what happened.
Retention questions should start from the record category and product reason: report reproducibility, retest comparison, monitoring, billing, dispute evidence or audit history.
Export and deletion handling is not a promise to remove operational, billing, security, audit or legal-retention records immediately.
Screenshots, HTML snapshots, issue fingerprints and scan metadata support reports, retests and monitoring.
Billing, credit, refund, service-credit and dispute records support eligibility and provider workflows.
Request routing, blocked states and quality-gate decisions are retained to explain product actions.
Retention categories include public leads, accounts, projects, scan pages, screenshots, HTML snapshots, issue fingerprints, reports, messages, billing records, credits, disputes, monitoring history and audit logs.
Records are retained to reproduce reports, compare retests, manage monitoring, prove authorization, route customer requests, enforce billing eligibility and inspect blocked workflows.
Screenshots, HTML snapshots, issue fingerprints, report state, and scan metadata are retained while they support active customer workflows.
Billing eligibility, credits, refund evidence, dispute evidence, and request-routing records are retained for operational traceability.
Customer-facing export and deletion workflows must respect operational, billing, security, and legal-retention requirements.
Secrets, credentials, private keys, payment method details, and provider tokens should not be exposed in public pages, exported reports, screenshots, HTML snapshots, or ordinary support records.