Receipts

Privacy notice

Effective September 30, 2026

This notice covers Receipts on andrarchy.com, operated by Andrew Levine. It was previously called the Prediction Record and, before that, the Prediction Ledger; its addresses have not changed. Other linked services have their own privacy policies.

Reading, publishing and taking a stance

You can read the record, and any single prediction's page, without an account. Reading without an account still sends ordinary request data, such as your IP address, to our hosting providers.

To publish a prediction, or to agree or disagree with one, you sign in through Supabase with Google or, where the sign-in page offers it, with X. From Google we receive your Google account identifier, email address and basic profile information, which may include your name and profile image. From X we receive your X account identifier and the profile information X shares with a sign-in, which may include your X username, display name, profile image and the email address on your X account. We use account information to authenticate you, associate predictions and stances with your account, help limit impersonation and abuse, and operate the service.

Publishing and taking a stance both require an account with a confirmed email address. If X does not share one for your account, you can sign in but cannot publish or take a stance.

The record does not request access to your Gmail messages, contacts or Drive files, does not post to X on your behalf, and does not receive your Google or X password. Signing in with a second provider creates or uses whatever account Supabase associates with that sign-in; the record does not merge accounts itself.

What becomes public

Everything you do on the record, other than signing in, is public by default. There is no private mode and no visibility setting.

Publishing makes your prediction, its revisit date, any note you add on how to check it, any optional context URL and timestamps, such as when the entry was published, public and linked to a public name. Each prediction has its own page at its own address, which anyone can open and share. Entries published before September 28, 2026 may also keep a numeric estimate their author entered at the time; it stays in the underlying public data even though the record no longer displays it.

That public name is the username you save, if you save one; otherwise it is a number the record assigns when your first prediction is published, shown as User_ followed by that number. Any thumbnail you choose is shown with it. The number stays in the underlying public data even when a saved username is shown instead of it. The underlying public data also includes a generated handle with a persistent account identifier. These can link your entries together. The operator, and Supabase as our service provider, can associate that identifier with your sign-in email and profile information, which are stored privately.

The record does not publish your email address. Nothing is copied from your Google account into your public profile. If you sign in with X, or connect X to an existing account from the Add prediction page, your X username and X profile picture become your public username and thumbnail wherever you have not chosen your own; that is stated beside the button before you go to X. A Use my X username and picture action in your profile editor replaces your chosen ones with your X ones only when you press it. The picture is re-encoded and stored in the same public bucket as any other thumbnail. Connecting X links your X account to your account on the record, which the operator and Supabase can see; your public username then matches your X handle, so readers can associate the two. Your own submission may identify you or others: do not include private or sensitive information.

Agreeing and disagreeing

When you are signed in, you can choose Agree or Disagree on another person's prediction until the end of its revisit date. Doing so is public. The prediction's page then lists your public name, which stance you took and when, and the prediction's public counts include you. The page says this beside the buttons; there is no separate confirmation step and no way to take a stance privately.

Your public name for a stance is the username you saved or, if you have none, your User_ number if you have published. If you have neither, the page asks you to choose a username first; choosing one does not take a stance. Taking a stance does not give you a User_ number.

You can take one stance per prediction, and you cannot take one on your own prediction. A stance cannot currently be changed or withdrawn through the site. If you later clear your username and have no User_ number, the stance remains listed without a name. A prediction's page lists up to 200 participants; the counts always reflect all of them.

Anyone can read who agreed and who disagreed, and can compare that across predictions by username, number or thumbnail. Signing in does not take a stance for you, and returning from sign-in does not either.

Disagreements recorded before named stances

An earlier version of the record offered a private “I disagree” action that showed only how many people disagreed. If you used it, that remains private: which account disagreed is not shown to the public or to the prediction's author, was not converted into a public stance, and is not included in any list of participants. It continues to be counted, and the prediction's page says how many of its disagreements are of this unnamed kind. While signed in, you can see that you disagreed yourself. The operator, and Supabase as our service provider, can see which account disagreed. An account with such a disagreement cannot add a public stance to the same prediction.

The optional public profile

You can choose a username and a thumbnail image for yourself on the Add prediction page, and a username on a prediction's page when you first take a stance. Both are optional unless you want to take a stance before you have published, which needs a username. Both are public, and both are shown with every prediction you have published and every stance you have taken; a saved username is shown in place of your assigned number. You can change or clear either of them at any time; your assigned number does not change.

Nothing in that profile is taken from Google. The only provider data that can appear in it is your X username and X profile picture, as described above, and only through X sign-in or a connection you start. Otherwise the record never sets a username or thumbnail for you. A username must be 3 to 24 English letters, digits or underscores, and usernames must be unique. The site's own name is reserved and is accepted only from the account connected to the X account of that name; an X username that is too short, reserved or already taken here is not used.

A thumbnail you choose is re-encoded by your own browser into a small square WebP image before it is uploaded, which removes camera, location and other embedded file metadata. Only the re-encoded picture is stored. It is stored in a publicly readable Supabase storage bucket at an address containing your persistent account identifier, so anyone with that address can read it and link it to your predictions and your stances, including stances taken under a different username later. An upload can succeed even if the later profile save fails; in that case the picture may remain publicly reachable without appearing on your profile. A username or thumbnail can also be copied or indexed by others before you change or clear it. Choose a picture you are willing to publish, and do not use one that identifies you or anyone else if you do not want that to be public.

Sharing and link previews

Each prediction's page includes a preview image and description showing the prediction, its author's public name and its revisit date. When a link to a prediction is posted or sent, X and other services and apps may fetch that page and image and keep their own copies. We do not control those copies and cannot remove them, including after a prediction is hidden or a username is changed. Our own hosting may also serve a saved copy of a page or image for up to five minutes.

The “Draft a post on X” link opens X with suggested wording and the prediction's address. The record does not post anything for you and does not learn whether you posted. Following that link is a visit to X, which applies its own privacy policy. The “Copy link” button writes the address to your clipboard and sends nothing anywhere.

Public entries, stances, usernames and thumbnails can be copied or indexed by others.

Storage, service providers and security

Vercel hosts the website and runs the code that prepares each prediction's page and preview image. Supabase provides authentication, database storage and the file storage that holds profile thumbnails; the project's database is located in the United States, in the US East region. Google handles Google sign-in and X handles X sign-in. These providers process information needed to provide their services, including technical request information such as IP addresses and browser details. Provider processing may occur in other countries.

Your browser's local storage stores session information to keep you signed in. If you start a sign-in from a prediction's page, it also stores which prediction to return you to, for at most ten minutes. You can sign out or clear site storage; this does not delete your account, published entries or stances.

The prediction pages do not include advertising or third-party analytics scripts. We do not sell Google or X account data or use it for advertising. Access controls restrict publishing and taking a stance to signed-in accounts; no system can guarantee absolute security.

Retention and requests

The record is intended as a durable public record. Accounts, predictions, stances and the earlier private disagreements are retained indefinitely unless the operator removes them; the prototype has no automatic deletion schedule or self-service account deletion.

Published predictions, stances and earlier disagreements cannot be edited or deleted through the user interface. Your chosen username and thumbnail are the exception: you can change or clear either at any time. Clearing a thumbnail removes it from the profile, then the site attempts to delete the stored image file. If that deletion fails or the service does not confirm it, the editor warns you that the file may still be public and lets you retry. Copies others already made of a published name, picture, prediction or stance are not affected. The operator is able to hide a prediction from public view, which also stops its page, its preview image and its list of participants from being served, and is able to remove an individual stance. There is currently no verified channel for submitting removal or visibility requests; see “Prototype contact limitation” below. Hiding or removing something is not the same as deleting underlying records, logs, backups or copies held by others.

We have not completed an inventory of how long our providers keep logs and backups, so we cannot state those retention periods and do not promise erasure from all copies.

You can revoke the application's access in your Google Account settings or in your X account's connected apps. Revocation stops future authorized access, but it does not sign you out of an existing session on the record; sign out separately. Revocation does not itself erase data already stored by the record.

Depending on where you live, you may have rights to access, correct or delete personal data or object to certain processing. This notice does not limit those rights, but the record does not currently offer a reliable way to submit such requests.

Prototype contact limitation

Changes

We will update this notice when the record's data practices change and show the effective date here. Any new use of Google or X account data will be disclosed before it is introduced, with renewed consent where required.