Cookie Notice
Last updated 2026-09-06. FairSquare is operated by Qavren Solutions LLC.
This page lists every cookie and every piece of browser storage FairSquare uses, what each one is for, and how long it lasts. The list is checked against the code by an automated test, so a cookie cannot appear in the product without appearing here.
Why there is no cookie banner
FairSquare asks you to accept nothing, because there is nothing here to accept. Every item below is needed to deliver a part of the site you asked for: to carry your answers from one step of the free check to the next, to bring you back to the right case after payment, to keep you signed in, to protect the sign-in handshake, to remember the dark-or-light choice you made yourself, and to remember that you declined automated processing.
We run no advertising, no cross-site tracking and no profiling. We do not use Google Analytics or anything like it. Page counts come from Cloudflare Web Analytics, which sets no cookie and does not fingerprint your browser — it is why a banner is not required here, and it is a deliberate choice.
If that ever stops being true — if anything is added that is not strictly necessary — this page changes and you get asked first.
What FairSquare itself sets
| Name | What it is for | Strictly necessary | How long it lasts |
|---|---|---|---|
fs_check |
Cookie. Carries your answers through the free eligibility check so the next question can be worked out and the step URLs stay clean. Signed, and not readable by scripts. | Yes | 7 days, or until you restart the check |
fs_checkout |
Cookie. Records which case, or which plan, you went off to pay for, so the page you land back on knows what to wait for. It carries no payment state. Not readable by scripts. | Yes | 1 hour |
fs-theme |
Local storage. The dark or light setting you picked with the theme toggle. | Yes — it holds a choice you made yourself | Until you clear your browser storage |
fs_skip_model_processing:<caseId> |
Session storage. Remembers that you declined automated processing of files on this case, so you are not asked again in this tab. | Yes — it holds a choice you made yourself | Until you close the browser tab |
What signing in sets
These are set by Auth.js, the sign-in library FairSquare uses, and only once you start signing in. A
signed-out visitor gets none of them. Over HTTPS their names carry a __Secure- prefix, and the
CSRF token carries a __Host- prefix; both prefixes are browser-enforced protections, not different
cookies.
| Name | What it is for | Strictly necessary | How long it lasts |
|---|---|---|---|
authjs.session-token |
Your signed-in session, encrypted. Without it you would have to sign in on every page. | Yes | 30 days, extended while you keep using the site |
authjs.callback-url |
The page to return you to after you finish signing in. | Yes | Until you close the browser |
authjs.csrf-token |
Stops another site from submitting the sign-in form on your behalf. | Yes | Until you close the browser |
authjs.pkce.code_verifier |
Ties the sign-in redirect back to the browser that started it, so the handshake cannot be hijacked. | Yes | 15 minutes |
authjs.state |
The same protection, for the redirect itself. | Yes | 15 minutes |
authjs.nonce |
Proves the sign-in token was issued for this attempt and not replayed. | Yes | 15 minutes |
authjs.challenge |
Part of the library's hardware-key sign-in. FairSquare does not offer hardware-key sign-in, so this is never set here. It is listed because the library can set it. | Yes | 15 minutes |
Signing in also takes you to our identity service on auth.qavrensolutions.com, which sets its own
session cookies on that address. Those cookies belong to the sign-in process and to no other purpose.
What the network sets
FairSquare is served through Cloudflare. Cloudflare's network layer may set the following when it filters or challenges a request. They are security cookies; they do not identify you to us and we cannot read anything about you from them.
| Name | What it is for | Strictly necessary | How long it lasts |
|---|---|---|---|
__cf_bm |
Cloudflare's bot filtering, so automated traffic does not take the site down. | Yes | Up to 30 minutes |
cf_clearance |
Records that you passed a security challenge, so you are not shown another one. | Yes | As long as the challenge-passage setting allows; 30 minutes by default |
Stopping the reminder emails
The link at the bottom of a reminder carries a signed token in the address itself. Opening it sets no cookie and stores nothing in your browser, and it does not sign you in. That is why it is not in the tables above.
Paying
Payment happens on Stripe's own pages, not on FairSquare. Stripe sets its own cookies there, under its own terms, and FairSquare has no part in them and cannot read them.
Turning them off
Your browser can block or clear cookies and site storage, and you can use a private window. Blocking them will break parts of FairSquare: the free check will lose your answers between steps, and you will not be able to stay signed in. Nothing here is used for advertising, so blocking them removes no tracking — there is none to remove.
Changes
We may update this notice. The date at the top changes when we do. See also our privacy policy and our terms of service.
Contact
Qavren Solutions LLC. Email: [email protected]