What Squire does with your text.

The text you provide is sent to Squire's own service. If the first look is set up, your text goes first to a model at Anthropic, which decides only whether this is a check Squire runs at all; a message it turns away goes no further. Your text then goes to a model at OpenAI. That model writes an answer, and is then asked again to double-check it against Squire's rules. A check sends OpenAI between two and six such requests. If the challenge is set up, the same text is also sent to a model at Google, which looks for holes in the answer but never decides it. When OpenAI's or Anthropic's model cannot be reached, that step is tried once more at a backup: a model at xAI for OpenAI's, and at Groq for Anthropic's. Which of these steps is set up is our choice. On Plus, once it is switched on for you, you may also choose the model that writes the answer and the one that looks for holes in it, and rule out companies and models, for the checks you save to your account. No AI model you rule out, by its company or by name, reads those checks, at any step or backup. Squire still asks Google about their links and asks a tracking link where it goes, as the next paragraphs say, and Squire itself runs on Google Cloud. Squire records every step that ran, with its company and model. Your receipt shows each step by its role, and your download of the check names each company and model. Your receipt says plainly when a step did not answer. When you delete a check from your account, Squire keeps, for about thirty days from when the check was made, what it needs to tell that the same text was sent again: scrambled codes made from the text and from its answer, how many different words the text had, the level of its answer, which models checked it and whether your own choice set them. These never include the text, its links, numbers or addresses, or the receipt. Deleting your account removes them too.

Squire does not browse. It reads only what you provide. It does not open links, look up a sender, or check a payment. It does ask Google about the links, and asks a tracking link where it goes, as the next two paragraphs say.

It does ask Google about the links. The web address of each link in your message and in your note, up to eight, is sent to Google Web Risk, cut short: anything after a question mark or a # sign, and any user name, is left off. Google checks it against its lists of sites it warns about, for phishing, harmful or unwanted software, and Google sees those addresses. Nothing else of the message is sent to Google for this, and it is not done for the checks Squire runs on its own test messages. Google's answer is shown on the receipt, and a link Google lists can raise Squire's answer, never lower it; a link Google does not list is not thereby genuine.

Many email links go first through the sending service's own tracking address. For a link on Squire's short list of such services, Squire sends that service one request for where the link points on, with no cookie and no sign-in, and reads only the address it answers with: it does not open the page, it never asks the site the link leads to, and it leaves alone any link that acts when opened, such as an unsubscribe or sign-in link. That service sees the request, and Squire's name on it. The name of the site the link leads to goes to the models with the rest of the message and is on the receipt. The full link is used for this and not kept: it is not written to any record or log. When you paste an email, Squire checks its links, even ones in a part you cut from the box. It shows you the list first. Nothing else from the cut part leaves your device, and of a link that would unsubscribe or confirm, only the name of its site is sent. For each of those links, the name of the site it points to goes to the models and is on the receipt.

Text you add from an email, by pasting it or by dropping or picking an email file, is read in this browser, and the file itself is never sent to Squire. A screenshot is read in this browser too. Squire receives only what is in the boxes when you press Squire it, including any changes you made, and an email's links as the paragraph above says. Each check also records how its text reached the box (typed or pasted as it was, read from a picture, pasted with its links written out, or read from an email file or a pasted message source) and whether you changed what was read or only cut it to fit the length limit. That record is kept with the check and is in your download of it, never on the receipt.

Squire stores the text you provided, any note you added, what each AI model replied, how much each model was used and what it cost, and the finished receipt. They are held on Google's cloud in the United States, where the service runs. Google and the model companies named above are the only other companies that get your text; a tracking service asked where its link goes gets that one request and nothing of your text. If you use Squire from another country, your text is sent to the United States, and to those companies under their own terms.

Squire does not store your internet address (IP address) itself. It stores a scrambled code made from it with a secret key. There are two copies, kept for different lengths of time. One sits in the counter that limits how many checks one address can run, and is deleted about a day after that address was last seen. Every check record holds one too, and it goes when the record goes: thirty days after the check finished, or, for a check in a MySquire account, when you delete it. Neither copy is ever returned to anyone reading a receipt.

The second copy is kept deliberately. Squire investigates abuse by every means available to it, and that includes this code and ordinary web server logs. Those record, for every request, the network address, the page, the time, the kind of browser and, when the browser says, the page that linked to it, as every web server's do, including every opening of a shared check, and Google Cloud keeps them for thirty days. Using this site is not anonymous, and nothing here offers you anonymity.

There is no advertising. The MySquire sign-in page loads a script from Google, which Firebase Authentication uses to sign you in with Google, as soon as the page opens on a phone or in Safari, and elsewhere when you choose Google. The other MySquire pages, and the check page while this browser is signed in, run Google's sign-in code from this site's own copy, load no script from Google, and talk to Google only to keep you signed in and to show your Google account photo.

Squire's information pages, How it works, About, the constitution, this notice and System status, can count visits with Google Analytics, and only if you say yes when a page asks. Until you do, they load nothing from Google Analytics and send it nothing. If you say yes, they load Google's script, which keeps two cookies in this browser for up to two years so that Google can tell a new visitor from one who came back. It sends Google which of these pages you opened and its title, with nothing after a question mark or a # sign except a campaign tag such as utm_source=linkedin, which says which post a link came from; how long you stay and how far down the page you scroll; which links to other sites you follow; the site that sent you there, and nothing of its page but the site, when your browser says; your browser, device type, screen size and language; and your internet address, from which Google works out a rough location. The two cookies belong to this site, so your browser also sends them to Squire with each request, and Squire does not read them. Google's advertising features, and its matching of visits to people signed in to Google, are turned off. Google keeps the detail of each visit for two months, the shortest it offers, and the totals it makes from them longer, under its own terms. The check page, the receipts, On this browser, Look up a receipt, MySquire, the sign-in and join pages and shared checks never use Google Analytics, so nothing you check reaches it. Your answer is kept in this browser's own storage, and without it the page asks again.

Squire reaches each AI company through its service for businesses. Under the terms each publishes for that service, it does not train its models on what Squire sends: OpenAI, Anthropic, xAI and Groq under their standard terms, and Google because Squire pays for its use. Each may keep what it receives for a limited time, under its own terms, to watch for abuse. A deletion at Squire does not reach those copies.

A check that is abandoned before it finishes is deleted automatically about a day after it was started. A finished check made without an account is kept for thirty days after it finishes, and then deleted, together with the key that opens it: the same clock runs both, so the record cannot outlive your access to it, and your key cannot open a record that is gone. Every check made signed out starts that way, and so does one you choose not to save to your account. A check made while you are signed in goes to your account, and a check you add to the account stops that clock: Squire keeps it until you delete it, which you can do from the account at any time, and you can download what Squire holds about it there too. Deletion runs some time after the thirty days, typically within a day, and the receipt stops being readable at the thirty days whether or not the deletion has run yet.

When a check made without an account finishes, your browser is given a random key for it. That key is kept in this tab, and is sent with each request for the receipt, never in a web address. Squire keeps only a scrambled code made from the key, never the key itself, so Squire cannot send you the key again, and a check whose key is lost cannot be opened unless it was added to a MySquire account first. Adding a check to an account retires its key: from then on the key no longer opens the check, which opens only for that account, when you are signed in. The key can still take down any share it made before the check was added.

Closing the tab removes the tab's access. It does not remove the stored record, which goes as described above.

A check made without an account is kept on this browser when it finishes, and so is a receipt you open here from its id and key. That keeps the key in this browser's own storage, not on any server, until the same thirty days close, and it keeps no copy of your message or the answer: it is a key, not a history. When the Your receipts page opens, it uses each key to read its check from Squire, and the status of each share this browser made of it, to show the check's headline, the opening of its message and the shares still up; it stores none of that, and forgets the code of any share that has ended. Ten are kept at most, and the eleventh drops the oldest. Anyone who uses this browser can open a kept check, so on a shared machine forget it when you are done, on the On this browser page. Forgetting it there first takes down any share of it made on this browser, then removes the key from this browser, and leaves the stored record of the check alone; the record still goes at thirty days. It also closes the check in any tab on this browser still showing it, and keeps the check's id, never its key, until those thirty days end, so that no tab brings it back; looking the receipt up again by its id and key reopens it. If a share cannot be reached just then, the key stays, so that Forget can try again, and the page says whether this device is offline.

Squire it again, on a check that stopped before it answered, carries its message and note to the check page inside this tab, and the check page takes them out as it opens, then starts the new check: a check of its own, with its own key, sent without saying how the message first reached the box.

A check whose answer is Very likely a scam can be shared, and only that answer, for now, including an answer Squire made more serious because Google listed a link in your message or note. Sharing makes a page on this site, with its own link, a short code and a card image, that anyone with the link or the code can open. The page shows the finding you got, the answer, the next step, the message as it was checked and the note you gave Squire with it, if you gave one. It is not listed by search engines. When Squire made the answer more serious because Google listed a link, the share's card says Text review and Google's lists. Its page dates the check by its month, and shows Google's warning only until the time Google's answer was good for, so a reader who sees it knows the check is recent. The link Google listed stays visible on the page, as the words the finding rests on do.

Before anything is shown, Squire hides your details in the message: your name, your own addresses and account numbers, references meant only for you, and tracking codes in links. The sender's name and address are hidden too, in case the message came from someone you know, and you can show them again. You can hide more words in the message and the note, except the words the finding rests on. Hidden words show as bars, and nothing can be added or changed. What you hide is hidden in the answer and the next step as well. Sharing runs no new check.

A check with any other answer can share an invitation instead: a sentence, a Squire picture and the address of this site's invitation page. Nothing about the check goes with it: no finding, no message and no code. Opening the invitation leads to this site, and nothing about it is stored or counted beyond the ordinary web server logs.

A shared check can be read for thirty days, a period Squire can change for shares made after the change, and it can be taken down at any time by whoever shared it, by the MySquire account that holds the check, from any device signed in to it, or by Squire. Deleting a check takes every share of it down. Someone can share a share again, as a new share, and it ends when the share it came from ends. When a share ends its text is deleted. A record that it existed, which share it came from and how it ended is kept for a year, without the text, so that an old link can say it has ended.

On this site, a receipt whose answer is Very likely a scam, and that check's row in the lists of your checks, offer SHARE: it shows the message with Squire's hidden words already as bars, and a tap on a word hides that word too. The codes of the shares made on this browser are kept in its own storage beside the check's key, so the receipt and the On this browser page can show them again and Forget can take them down.

Squire counts, for each share and never for each person, how often it is previewed by a messaging app, opened, and followed by a check of someone's own. The web server logs described above record each opening like any other request.

You can sign in to MySquire with a link Squire emails you through Mailgun, or with Google; to limit sign-in links, Squire counts those asked for each address under a scrambled code made from it, deleted within about a day. Sign-in is run by Google's Firebase Authentication, which holds your email address and how you sign in. Squire keeps a small record for each account: how you sign in, whether you are on Squire's team, the first and last day you were signed in, your plan with its end, the team's reason, its last 20 changes and a note for the team alone that your download leaves out, your address while the plan is Plus (it goes when the plan is made free, or at your first sign-in after it ends), and a scrambled code made from your address, so the team can find your account if you write to us. A page that shows your address still reads it from your sign-in. Deleting your account deletes the record. For about 400 days the team's own log keeps, under a scrambled code of your account, when your plan was changed or your account was looked up, and by whom. For each check in your account Squire keeps a usage line: the day, your plan, how the check ended and the level of its answer, which companies' models answered and how much text each read and wrote, and an estimate of what the check cost Squire, for its own accounting. It also keeps your account's totals for each month, made from those lines. Your download carries the lines and the monthly counts without the costs or the amounts of text. When you delete a check, its usage line goes with it and comes out of the month's totals; when you delete your account, all of them go. Squire also keeps daily counts of checks by model that name no one and no check. When your Google account has a photo, the signed-in MySquire pages show it, loaded from Google's servers; Squire does not store it. Squire also keeps the account's id on each check you add to it or make in it, and on each share your account makes from one of them. A share made with a check's key before you added the check carries no account id.

If you are invited to test Squire, we keep your address, when you were invited and when you joined, to let you run checks. Ask us and we remove it. Deleting your MySquire account removes the tester record it joined with. While Squire is invite-only, each check made here goes to the signed-in account, and Squire counts a tester's checks for the day under a scrambled code made from the account, deleted two days later.

Adding a check to your account is your consent for Squire to keep it with the account, and so is making a check from the check page while you are signed in: the page says under the box that the check goes to your account, with a switch to send it without saving it there. Such a check has a key of its own in the tab while it runs, and the key never opens it: only the account does. Squire does not need your account to link your checks: the scrambled code made from your internet address, described above, already shows that checks from one address belong together. Adding a check takes its key off this browser, with the codes of the shares this browser made of it, and the check then has no end date: it is kept until you delete it. Unlike Forget, adding a check takes none of its shares down: they stay up, and the check's page in your account lists them, and you can take each one down there. From its page in your account you can download what Squire holds about it, the full answers each model company gave included, except the record of what each company charged and how much of each it used, which Squire keeps for its own accounting; and you can delete it, which takes every share of it down and cannot be undone.

When you choose Google, the sign-in page opens Google's own window to sign you in. While a sign-in link is on its way, this browser keeps the address you typed in its own storage, so the link can finish signing you in, and removes it once you are signed in, or once the link can no longer be used. An address still kept a day after its link was sent is removed the next time the sign-in page opens on this browser. The link carries a one-time code in its address, so the web server logs described above record that code when the link is opened. Firebase Authentication keeps you signed in on this browser until you sign out. Signing out ends the sign-in here, but if someone copied this browser's sign-in pass before you signed out, it keeps opening the account's checks, and can make checks in it, for up to an hour.

Do not provide passwords, one-time login codes, card numbers, government identifiers, or anything else you would not want processed by the services named above. If the message you are checking contains such a detail, remove it first. A check works just as well without it.

If what Squire does with your text changes, this notice changes by the day the change takes effect, and so does the date at the top.

SQUIRE, a Nevada corporation trading as Sparfuchs-Pro. Privacy questions and requests: privacy@squireit.com.