We are an honesty brand, and that includes this page. Here is exactly what AuditLamp collects, why, and what we never do. No dark patterns, no buried clauses.
What we collect
- Account details. Your email address and a password. Passwords are never stored in plain text. We store a one-way PBKDF2 hash you cannot reverse.
- The sites you scan. The URLs you submit, the results of those audits, and your score history over time, so you can track changes. These are tied to your account.
- Billing details. If you subscribe, payment is handled entirely by Stripe. We never see or store your card number. We keep a Stripe customer reference and your plan tier.
- Basic technical data. A login token stored in your browser's localStorage so you stay signed in. When we are running ads, our pages also load Meta's advertising pixel. See "Advertising measurement" below for exactly what it does and how to opt out.
How we use it
- To run your audits and show your results and history.
- To sign you in and keep your scans private to your account.
- To bill you for a paid plan, if you choose one.
That's it. We do not sell your data. The one exception to keeping it to ourselves is the Meta advertising pixel described next, which we use only to measure our own ads, and only while those ads are running.
Advertising measurement (Meta pixel)
When we are running ads, the homepage and the audit app load Meta's advertising pixel. It tells Meta that a page was viewed, that a scan was started, or that a purchase completed. That signal is tied to Meta's own cookies, not to your AuditLamp account, so Meta does not learn your account email or your scan history from us.
You can opt out through your browser's tracking settings or your Meta ad preferences. The pixel loads only while we are running ads. The rest of the time it is off entirely, and no Meta code loads on the page at all.
When we audit a site
AuditLamp fetches the publicly available pages of a URL you submit, the same pages a search crawler or an AI engine would read. We only request public content, the way any browser does. Audit only sites you own or have permission to analyze.
Third parties we rely on
We use a small set of providers, and only for the feature you actually use:
- Stripe: payment processing (paid plans only).
- Google PageSpeed Insights / Search Console: real performance and ranking data, only if you connect them.
- Third-party data providers: backlink, competitor, and ranking data, only on the paid tiers that use them. They receive the domain being audited, never your account data.
- An AI analysis provider: the entity/citability analysis, only when that feature is run. It receives the page's public text, never your account data.
Your choices
- You can request a copy of your data or its deletion at any time; email us below.
- You can delete your account, which removes your scans and history.
- You can cancel a paid plan at any time through the Stripe billing portal.
The browser extension
The AuditLamp Chrome extension audits the page you are on, only when you click it. Here is everything it does with data:
- What it sends. When you click the extension, it sends the current tab's URL to our audit engine at auditlamp.com, the same as pasting that URL into the site. Nothing is sent until you click.
- What it stores. Nothing. No browsing history, no analytics, no identifiers. The extension has no background process and cannot see pages you do not run it on.
- The on-page overlay. The Machine's Eye overlay runs entirely in your browser. It reads the page's own markup locally and sends nothing anywhere.
- What we keep. The audited URL and its results are handled exactly like a scan run on the site, as described above. Extension scans are not tied to an account unless you are signed in on auditlamp.com.
Contact
Questions, data requests, or deletion: hello@auditlamp.com.