Privacy Policy — Audit Lens (WCAG Quick Scan)
Effective date: 2026-08-13
Audit Lens is built so there is very little to say in a privacy policy — that's deliberate. This page explains, in plain language, everything the extension does and does not do with data.
Scan results never leave your browser
When you click "Scan," Audit Lens reads the current page's DOM in memory, runs the vendored axe-core engine against it, and displays the results in the popup or in a locally generated report. That scan data — page content, element selectors, violation details, the page's URL or title — is never transmitted anywhere. It is not sent to us, not sent to any third party, and not sent to any analytics or crash-reporting service, because Audit Lens contains none. This is asserted directly by an automated test that inspects every network request the extension makes during a scan.
No analytics, no tracking, no sale of data
Audit Lens does not use analytics SDKs, does not set tracking identifiers tied to your identity, does not build advertising profiles, and does not sell, rent, or share any data with anyone. There is no "anonymous usage statistics" toggle because there is no usage-statistics collection to toggle.
The one network request the extension makes
The only request Audit Lens ever sends over the network is a license verification call, and it only happens when you actively enter or refresh a Pro license key:
POST /v1/license/verify
Body: { key: "<your license key>", installId: "<random UUID>" }
That request contains exactly two pieces of information:
- The license key you typed in.
- A randomly generated install identifier (a UUID, generated locally, with no personal information encoded in it — it identifies a browser installation, not a person).
It never contains a URL, page content, a page title, scan results, or any other data. This is the only origin the extension ever contacts, whether you're on the Free tier (which makes zero network requests) or the Pro tier.
Buying a Pro license
Purchases happen outside the extension, on a Stripe-hosted checkout page — the extension itself never collects or transmits your payment details or email address. Stripe handles the payment under its own privacy policy.
When a purchase completes, Stripe notifies our license server directly (not through the extension, and not through the request described above) and shares the email address you gave Stripe at checkout. Our license server then:
- generates a new license key,
- stores that key together with your email address in a short-lived internal queue whose only purpose is getting the key into your inbox,
- sends your email address and the license key to Resend (resend.com), the third-party email-delivery service that puts the message in your inbox, and
- removes that queue entry once the key has been sent to you.
That email address is used for nothing except delivering your license key. It is never linked to any scan you run and never used for marketing. It is shared only with the two parties strictly needed to get a purchased key into your inbox: Stripe, which already collected it to process your payment, and Resend, which sends the delivery email on our behalf and handles it under its own privacy policy. None of this changes the boundary described above: scan data still never leaves your browser, and is never sent to us, Stripe, Resend, or anyone else.
What's stored, and where
Everything the Audit Lens extension stores lives locally in your browser, using Chrome's extension storage APIs:
| Data | Storage | Purpose | Lifetime |
|---|---|---|---|
License record (key, valid, plan, seats, checkedAt) | chrome.storage.local | Remembers your Pro status so you don't re-enter your key every time | Until you deactivate or remove the extension |
| Install ID (random UUID) | chrome.storage.local | Identifies this browser installation to the license server for seat counting | Until you remove the extension |
| Generated report HTML | chrome.storage.session | Transiently hands a report from the popup to the tab that displays it | Cleared automatically once the report tab reads it, and whenever the browser session ends |
Separately, our license server (which never sees scan data — see above) stores:
| Data | Purpose | Lifetime |
|---|---|---|
| License key, plan, seat count, and the install IDs that have claimed a seat | Enforces the 3-seat limit per key | Kept for the life of the license |
| Your email address, paired with a freshly generated key | Delivering a purchased key to you — forwarded to Resend, our third-party email-delivery processor, to send that email (see "Buying a Pro license" above) | Removed once the key is delivered |
None of this is shared, sold, or used for anything beyond the two purposes in that table — except that, as described above, the email row is necessarily forwarded to Resend for delivery.
Your control over your data
Because everything the extension itself stores lives locally, you have full control:
- Deactivating your license (in the extension popup) clears the stored license record immediately.
- Removing the extension from Chrome deletes all locally stored data — the license record, the install id, and any transient report payload — permanently and immediately.
If you would like your email address removed from the license-delivery queue before it is processed, or have any other privacy question, use the contact channel below.
Automated testing is partial — a note on the reports themselves
Reports generated by Audit Lens include a footer disclaimer stating that automated testing detects roughly 30–40% of WCAG success criteria, that manual review with assistive technology is required, and that the results are not a legal compliance certification. That framing is part of what the extension produces, and we hold ourselves to the same honesty in this policy: we are not making claims about your data's security beyond the technical facts stated above, verifiable directly in the source and bundle.
Changes to this policy
If this policy changes, the effective date at the top of this document will be updated and the new version will ship with the corresponding extension release.
Contact
Questions about this policy, or requests regarding your data, can be sent through the developer contact channel listed on the Audit Lens Chrome Web Store listing.