Privacy Policy

Last updated 2026-09-06. FairSquare is operated by Qavren Solutions LLC.

This policy describes what FairSquare actually does today, not what it may do later. Where a thing is not built yet, this page says so.

What we collect

The free eligibility check. You do not need an account for it. Your answers are sealed into a signed cookie on your own browser (fs_check) and sent back to us with each step so the next question can be worked out. We do not keep them. Our server log records only the state, the kind of claim, whether the check came out eligible, and whether a time limit could be computed. It records no amount, no date, no name, and nothing that identifies you.

Your account. When you sign in we hold your email address, your display name if your sign-in provider supplies one, and the account identifier that provider gives us. Each account gets one organization, which holds a display name and, for a business account, the business details you enter.

Your case. For each case you create we hold the title you give it, the kind of claim, the amount claimed, the dates you enter (when the thing happened, the contract date, the last payment, when you posted the demand letter, when you filed, when you delivered the papers, the hearing date), the state, county and courthouse, the case number the clerk gave you, how the papers were delivered and who delivered them.

The parties. For you and for the other side: the name, any trading name, the address for service, an agent for service if there is one, a phone number and an email address, and which side is yours.

Your evidence record. Each entry holds the date the thing happened, your summary, any longer note you write, the labels you attach, and the exhibit number once the record is locked.

Files you attach. We store the file itself, its original filename, its type, its size, a checksum, its page count, and the text read out of it. Where a field is read out of a file — a date, an amount — we store that value, the exact passage it came from, its position in the text, which reader produced it, and whether you confirmed or corrected it.

Documents FairSquare assembles. Every version of every draft, each section of it, whether that section is template text, drafted text or your own edit, the references the engine chose for it, the rendered PDF and its checksum.

Your consents. Each time you agree to something, we record which agreement, the exact version of the wording you were shown, when, and on which case.

Purchases. What you bought, whether it is paid, the amount, the currency, and the identifiers our payment processor gives us for the checkout, the customer and the subscription. Card numbers never reach FairSquare. You type those on the processor's own page.

Dates we compute. The deadlines worked out from your dates, each stored with the anchor it was counted from, that anchor's date, the window, one plain sentence explaining how the date was reached, the rules pack version, the rule it came from, and whether you have marked it as seen or met.

The outcome, if you record one. The date a judgment was entered, the amount, which side it went to, any costs awarded, the date notice was served, and the date you say it was paid in full.

Which reminders have gone out. For each reminder message: the case, the deadline, how many days out it was, and when it was sent. Not the message itself. This record exists so the same reminder cannot be sent twice.

Whether each case wants reminders. One setting per case.

An audit record. An insert-only log of the things that matter: consents given, files processed, documents assembled and downloaded, entries deleted, purchases settled. It cannot be edited or removed, by us or by anyone.

We do not collect health information and the product is not designed to hold any. We do not use advertising identifiers, and we do not build profiles.

Why we hold it

We hold your account details, your case, your evidence and your documents because that is the service you asked us to provide; without them there is nothing to assemble. We hold the audit record because we need to be able to show what the product did and what you agreed to. We send file contents and case facts for automated processing only where you have given consent for that case, and that consent is recorded with the wording you saw. We do not sell your data, we do not share it for advertising, and we do not use it to train anyone's model.

Who else handles it

Amazon Web Services hosts the application and the database. Everything above lives there unless this list says otherwise.

Cloudflare sits in front of the site as its network edge, and Cloudflare R2 is the object store that holds your uploaded files and your rendered PDFs where a bucket is configured for the deployment. Where no bucket is configured, a file cannot be attached at all and a rendered PDF is held in our own database instead. Links to a stored file are signed and expire ten minutes after they are issued.

Cloudflare Web Analytics counts page views where it is switched on. It sets no cookie, and it does not fingerprint your browser.

Keycloak, run by Qavren Solutions, handles sign-in. It holds your email address and the credentials or provider link you sign in with. FairSquare never sees your password.

Anthropic receives document text and case facts, and only in two places: when you have recorded the automated-processing consent on a case and a file on that case is read, and when a section of a document is drafted. It receives the text of that file, or the facts and labels for that one section — never your whole account. This only happens where the deployment has a model key configured. Where it has none, the same work is done by a local, rule-based reader on our own server and nothing about your case leaves it.

Stripe processes payments. You enter your card details on Stripe's own page, under Stripe's own privacy terms. We receive back only the identifiers and the paid-or-not answer.

Amazon SES carries the reminder emails, and those are the only email FairSquare sends. This is worth setting out in full, because a reminder takes content out of your case and puts it in a mailbox.

What is in one. The title you gave your own case, in your words. Plain words for which window it is. The date. The one sentence explaining how that date was reached from the date you entered. The short reference for the rule behind it, and a link to the official page that rule is published on. A line telling you to check the date with your court. A signed link that stops reminders for that one case. Nothing else — no amount, no party name, no address, no evidence, and no document.

Where it goes. To the email address on the account of the person who owns the case, which is the address your sign-in provider gave us. Once a message reaches a mailbox it is held by whoever runs that mailbox, under their terms, not ours. The subject line carries the case title, so it is visible in a notification and in an inbox list. If that matters to you, name your case accordingly, or turn reminders off.

When. At most one message per deadline, at 14, 7, 3 and 1 days before it falls due, for deadlines that are still open. FairSquare never emails the other side of your case, and never emails anyone about a case that is not their own.

Whether anything is sent at all. Reminders are on by default for each case. You can turn them off on the case itself, or with the link at the bottom of any reminder, which needs no sign-in and carries a signed token that can do nothing except turn that one case's reminders off. It expires after 90 days. Separately, no message is sent by any deployment that has no sending identity configured — the mail sender defaults to disabled, the DNS and identity records are written but not yet applied, and the account has not been granted production sending. So the capability is built and nothing is being sent today. When that changes, what is described above is what will go out.

Amazon SES receives the recipient address and the message. We log only the identifier SES hands back, never the recipient or the body.

How long we keep it

While your account exists, your cases stay as you left them. That is deliberate: a claim can run for months and a deleted record cannot be got back.

You can delete an evidence entry yourself at any time before its exhibit number is fixed, and the file attached to it is deleted from the object store with it.

Deleting a whole case, deleting your account, and exporting your data are not yet buttons in the product. Until they are, email [email protected] and we will do it by hand and confirm within 30 days.

The record of which reminders have been sent is kept for as long as the case is, because it is what stops the same reminder going out twice. It holds no message content.

The audit record is insert-only and is kept after the data it describes is gone. It holds event names, timestamps, identifiers and counts, not the content of your case.

Your choices

You can read and correct everything in your case inside the product. For a copy of your data, or to have your case or your account deleted, email [email protected]. Depending on where you live, you may have a right to access, correct, delete, or object to our handling of your data, and to complain to your data protection authority. We answer every request the same way whether or not a law gives you that right where you live.

You can refuse automated processing of your files. Every case asks before the first file is read, and declining is a real answer: the file is still stored and simply never read.

You can stop the reminder emails for a case at any time, either on the case itself or with the link at the bottom of any reminder. That link needs no sign-in, so you never have to get back into an account to stop mail you did not want.

Children

FairSquare is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has given us data, email [email protected] and we will remove it.

Where your data is

FairSquare runs on servers in the United States, and our processors handle your data there. If you use FairSquare from outside the United States, your data is transferred to and processed in the United States.

Cookies

FairSquare sets only the cookies and browser storage it needs to run the parts of the site you asked for. Every one of them is listed, with its purpose and its lifetime, on the cookie notice.

Changes

We may update this policy. The date at the top changes when we do, and a change that affects what we collect or who receives it is announced in the product before it takes effect.

Contact

Qavren Solutions LLC. Email: [email protected]