Skip to the content

Privacy

Aback Audit has no accounts, sets no tracking cookies and asks for no personal data. This page says exactly what is stored and why.

Last updated October 2026

What is stored

  • The address that was audited, the report, the time of the run and the region it ran in.
  • The address of the client that asked for the audit, so the rate limits can be enforced.
  • A hash of the delete token of a report, never the token itself.
  • The email address and the license key of a customer who bought the Pro plan.

How long it is kept

Reports are deleted after 30 days. Rate limit counters are removed after a day. A report can also be deleted at any time with the delete token that was shown when the audit was created.

What is sent to the audited site

Only ordinary GET and HEAD requests, with the user agentAbackAuditBot/2.0. No cookies, no credentials, no personal data. The crawler never modifies the site it reads.

Cookies and tracking

The API and the MCP server set no cookies and load no third party scripts. The website sets no cookie unless you add a Pro license key: the key is then kept in a first party cookie namedaback_pro so the api can read it. Your theme, the history of your audits and your monitor links stay in the local storage of your browser and are never sent anywhere.

Payments

Payments are handled by Dodo Payments, who act as the merchant of record. They receive the email address and the amount, and they issue the invoice. Aback Audit never sees the card details.

Questions

Write tocontact@abackaudit.com.

↑ ↓ to move↵ to openesc to close