Privacy in the V1 product
AuditCloser is intentionally lightweight and stateless. This page describes the behaviour of the current V1 software; a buyer operating a commercial deployment should adapt this policy to their business, jurisdiction and configured integrations.
Public website audits
When an audit is requested, the server fetches the submitted public webpage to analyse its HTML and response headers. AuditCloser V1 does not require a database and does not persist audit reports by default.
Agency branding
White-label agency settings are stored in the current browser using local storage. They are not written to an AuditCloser database.
Embed lead submissions
The optional embed widget can collect a lead email address after an audit. If a deployment configures a lead webhook, that information can be forwarded to the operator's chosen service. Without a webhook, V1 does not persist the submission.
Network safety
The scanner is limited to public HTTP(S) pages and blocks obvious localhost, private-network and link-local targets. It also limits redirects, response size and request duration.
Operator responsibility
A buyer who enables analytics, CRM, email, authentication or other integrations is responsible for updating disclosures and data-handling practices accordingly.