Cookie Policy
The real inventory of what SiteGuardia stores in your browser, rebuilt by inspecting a browser rather than by describing intent.
Version 2026-09-22Updated 2026-09-22
This is a working draft. It describes the system as built and has not yet been reviewed by a qualified lawyer.
This document is a working draft. It has not been reviewed by a qualified lawyer and will be before SiteGuardia operates commercially. Nothing here is legal advice.
The actual inventory
SiteGuardia sets no cookies at all. It stores one value in your browser, in localStorage, and only after you change a setting.
| Name | Type | Purpose | Duration | Party |
|---|---|---|---|---|
siteguardia-theme | localStorage | Remembers whether you chose light, dark or system | Until you clear site data | First party |
scanvero-theme | localStorage | The same setting under the product's previous name. Read, never written; it disappears once you change the setting or clear site data | Until you clear site data | First party |
That is the whole list, and the second row only exists for people who set a theme before the product was renamed.
How this list was produced
This page used to be written from what the system was meant to do, and it was wrong in two ways that matter.
It declared a scanvero-session cookie for "abuse prevention and rate limiting". No code sets that cookie. The name existed as a constant nothing used. Quota and rate limiting work from a keyed pseudonymous value derived per request and never stored in your browser, which is why clearing site data does not reset a limit.
It declared __cf_bm as a third-party cookie "set by Cloudflare Turnstile when the anti-bot challenge is shown". No anti-bot challenge is shown. The frontend does not load Turnstile, so nothing from Cloudflare is requested and that cookie cannot appear. Separately, Cloudflare documents __cf_bm for Bot Management and Bot Fight Mode rather than for Turnstile, so the attribution was wrong as well as the fact.
So the list above was rebuilt by inspection rather than by description: a clean browser profile, ten scenarios, and a record of every cookie, every storage key and every request that left this origin. The scenarios were a first visit in each language, changing the theme, changing the language, entering an address for the preflight check, the example report, the legal pages, security.txt, a real report, and downloading a report as a PDF.
The result in every one of the ten: no cookies, no sessionStorage, and no request to any host other than this one. The only storage that appeared was siteguardia-theme, and only in the scenario where the theme was changed.
What is not here
No advertising cookies. No third-party analytics. No tracking pixels. No social media embeds. No cross-site identifiers. No browser fingerprinting of any kind, which means no canvas, audio or WebGL identification.
No fonts, scripts, stylesheets or images are loaded from another domain, on any page. The report you can download as a PDF carries no remote resource either, so opening it later contacts nobody.
Why there is no consent banner
There is nothing to consent to yet. The one thing stored is a theme preference you created by clicking a control, it is read only by this site, and it is not used to identify or profile anyone. In many jurisdictions storage of that kind does not require prior consent, though it does require clear information, which is what this page is.
That is a statement about what the service stores today, not a permanent exemption. If analytics, advertising or any other non-essential storage is ever added, a consent mechanism appropriate to your region goes in before it is turned on, and this page changes first.
If the anti-bot challenge is turned on
The service is built to be able to use Cloudflare Turnstile to tell a person from automated traffic, and the code to verify a challenge exists. It is not enabled, and no part of the website currently loads it.
If it is enabled, your browser will contact Cloudflare, Cloudflare will process signals about the request in order to answer the challenge, and one or more Cloudflare cookies may be set. That is a change to this inventory and to the list of who processes your data, so this page and the Privacy Policy will both be updated before it happens rather than after.
Turning it off
You can clear or block site data in your browser at any time. Clearing it loses the theme preference and nothing else. Rate limits are enforced on our servers, so clearing browser storage does not reset them.
Changes
This policy is versioned. If the inventory changes, this page changes with it, because a cookie policy that does not match the product is worse than none. This version exists because the previous one did not.