Privacy

Fullsweep is operated by an individual, not a company. There is one person behind this product, the same one the footer on every page already tells you about.

• Your email address. When you sign in, so we know it is you and can send you your sign-in link. If you sign in with a Google account instead, we only ever receive the email address that account gives us, nothing else about it.
• The sites you ask us to check, and everything we find. The addresses, the pages, the problems. This is the product itself, and we keep it so you can come back and read your reports.
• A cookie that remembers you before you sign up. The first time you check a site with no account, we set a cookie in your browser, signed so we can tell it has not been tampered with, so we can show you your own report and count how many free checks you have used. It carries no name and no email, just a random id, and it lasts 30 days.
• A scrambled version of your IP address. To stop one visitor running far more than the free limit of checks an hour, we turn your IP address into a one-way hash, a scrambled code that cannot be turned back into the original address, and count that instead. We never store your actual IP address.
• The full page-by-page results of a crawl, as a downloadable file. For a crawl of any size, we also save the complete list of every page checked as a CSV file, held in file storage, that you can download from your report.
• A record of your purchase, if you buy lifetime access. So we know your account is entitled to it, and so a refund can find its way back to the right account.

We host Fullsweep on other people's infrastructure, the way almost every small product does. Each of the following sees some part of what is listed above, only as much as its job requires:

• Resend sends the emails Fullsweep sends you, like your sign-in link, and briefly holds your email address and the email's content to do that.
• Neon hosts our database. Nearly everything on this page, your account, your sites, your crawl results, lives there.
• Railway runs the part of Fullsweep that actually crawls websites, so it sees the sites you ask us to check while a crawl is running.
• Vercel hosts the website and app you are using right now, so it sees your requests to it the way any web host does.
• Cloudflare stores the downloadable CSV files a crawl produces.

A report from a check you ran with no account stops being reachable after 7 days, and the underlying record, along with any downloadable file it produced, is permanently deleted 7 days after that, 14 days from when you ran the check. That deletion runs on an hourly check, so it may take up to an hour past the 14-day mark, never longer. If you want the report kept, sign in and save it before the 7 days are up.

Everything tied to an account is kept until you delete the account. There is currently no way to delete a single site or a single report on its own, only the whole account at once.

A purchase record is kept indefinitely, including after you delete your account. See the next section for why.

Delete your account from the account page and this happens right away, with no way to undo it: every site you added, every crawl and its report, every finding and the full list of pages a crawl found, and the account itself along with the way you sign in.

Two things are deliberately not touched by that delete:

• A check you ran before signing up, and never claimed by signing in, is not linked to your account, so deleting the account does not reach it. It disappears on its own 14-day schedule instead, per the caveat above.
• If you redeemed a lifetime licence through AppSumo, the record of that purchase, including the email AppSumo told us, stays on file. It is AppSumo's own record of the sale as well as ours, so we keep it, but we clear the link to you: after deletion, nothing in that record points back at your account.

Any downloadable CSV file a crawl of yours produced is deleted from Cloudflare storage too, on the same hourly check mentioned above, so it may take up to an hour after you delete the account, never longer.

Fullsweep uses a small number of cookies, all required for the product to work, none of them for advertising:

• A sign-in cookie, once you have an account, so you do not have to sign in again on every page.
• The anonymous cookie described above, if you check a site before signing up.
• A cookie that remembers whether you prefer light or dark, nothing personal.

We do not run any advertising or analytics trackers on this site.

One thing is optional: crash reports. If a page breaks in your browser, it can send us a report about the error so we can fix it. That only happens if you allow it in the cookie notice, and you can change your answer any time with the Cookie choices link in the footer. Our own servers keep their error logs either way; those are about our machines, not about you, and no cookie is involved.

Fullsweep is UK based, so UK GDPR is the law that mainly applies to what is on this page; if you are in the EU, the EU version of the same rules applies too. In plain terms, you can ask us what we hold about you, ask us to correct it if it is wrong, ask us to delete it (deleting your account does most of this yourself, immediately), or ask us to hand it over in a format you can take elsewhere.

We collect your account data because you asked us to run this service for you, that is a contract between us, not a favour. We collect the IP hash and the anonymous cookie on a different basis, a legitimate interest in stopping one visitor from draining a free service meant for everyone.

We will update this page as the product changes, and we will change the date at the top when we do. It is a draft today, so treat anything it does not yet answer as a gap, not a refusal.

Fullsweep does not yet have a published privacy contact address separate from the rest of the product. Until that exists, reach out the same way you would about anything else on Fullsweep, it reaches the one person who runs it.