Beta

Crawlwise is in beta

Tell us what you think

Crawlwise is in beta. A wrong recommendation, a missing check, a confusing screen — anything helps.

0 / 2000

Stored to improve Crawlwise. How we handle it

Crawlwise

Privacy policy

Crawlwise needs no account to run a technical audit, and sets cookies only when you sign in: two, described under Your account. This page lists the little it does collect, why, and for how long.

Last updated 2026-10-23

Who is responsible

Maxime Baudin, who publishes Crawlwise, is responsible for the data described here. For any question or request about it, write to lightning.pixel.dev@gmail.com.

The site you audit and its report

When you run an audit, Crawlwise stores the address you entered and the report it produces: the pages crawled, the issues found, the score and, for a full audit, the AI reading and the action plan. This is what the service exists to do, and it is kept for as long as the service runs.

Reports are public. Anyone who opens the report page for a domain sees its latest report. They describe public websites, never who asked for them.

The context you add

You can describe what your site is for before a full audit. That text is stored with the report, sent to the AI model to guide its reading, and shown on the public report page. Leave out anything you would not publish.

Your IP address

Full audits call a paid AI service. Accounts are limited by their credits, not by their address. When you run an audit without an account, your IP address is stored with it for abuse prevention, on the basis of our legitimate interest in preventing abuse. It is erased 24 hours later, within the following hour, and never shown on a report. Audits run while signed in carry no IP address.

The audit service's request logs record the path, status and timing of each request, not your address.

Your account

Signing in uses Firebase Authentication (Google). It stores your email address and, for password accounts, a hashed password, in the United States, under the EU–US Data Privacy Framework.

Signing in sets the only two cookies this site uses. The first, cw_session, is an httpOnly sign-in cookie: it holds your sign-in and lasts up to 30 days, until you sign out. The second, cw_signed_in, can be read by the page and only marks that you are signed in, so the header can say "Dashboard"; it holds no identifier. Neither is used to track you. While you are signed in, the Firebase sign-in library also keeps its own sign-in state in your browser's storage (IndexedDB).

Account emails (verification, password reset) are sent through Resend, in the EU.

Audits you run while signed in are private to you and kept until you delete your account; deleting it deletes them. No IP address is stored with them.

Payments

Subscriptions and credit packs are paid through Stripe. Stripe collects your card details, name, email and billing address on its own payment page; Crawlwise never sees or stores your card number. The audit service keeps your Stripe customer reference, your plan and its renewal date, to give your account what it paid for.

Invoices and payment records are kept for 10 years, as French accounting law requires (Code de commerce, article L123-22), even after you delete your account.

Feedback

While Crawlwise is in beta, you can send us a message or tell us whether a report was useful. We store what you write, your vote, the report it concerns and the page you sent it from, to improve the service. Your email is optional and only used to reply to you.

Your IP address is stored with it to limit how much one visitor can send, and erased 24 hours later. The feedback itself is deleted after 365 days. It is never published, and only the publisher reads it.

Analytics

The site counts page views and a handful of product events, such as an audit being started or a prompt being copied, with Vercel Web Analytics. Vercel Analytics itself uses no cookies and does not identify individual visitors.

Who else receives data

  • OpenAI (United States) receives the public text of the audited pages and your context, only for full audits. Under OpenAI's API terms, this data is not used to train its models.
  • Cloudflare (United States) runs Turnstile, the automatic check that a full audit is started by a person. It sees your browser and IP address when you start one, sets no tracking cookies, and does not use the data for advertising.
  • Firebase Authentication (Google, United States) handles sign-in. It stores your email address and, for password accounts, a hashed password, under the EU–US Data Privacy Framework.
  • Stripe (Stripe Payments Europe, Ireland) processes payments and issues invoices. It may transfer data to Stripe, Inc. in the United States under the EU–US Data Privacy Framework.
  • Resend (European Union) sends the account emails: verification and password reset.
  • Vercel (United States) hosts the website and runs the analytics.
  • OVH (France) hosts the audit service and its database.

Transfers to the United States rely on the safeguards these providers offer, such as the EU–US Data Privacy Framework and the European Commission's standard contractual clauses. Nothing is sold or shared for advertising.

Sites we crawl

The crawler reads public pages only, obeys robots.txt and identifies itself. How it works and how to block it is explained on the crawler page.

Your rights

You can ask to access, correct or erase data about you, object to its use or restrict it, including the removal of a report on your own site. Write to lightning.pixel.dev@gmail.com; we answer within a month. You can also complain to the CNIL, the French data-protection authority, at cnil.fr.