Privacy

From signing in. Privy gives this site your decentralised identifier — the account id it issues — and the method you signed in with. Privy holds the email address or social account behind that; this site stores the identifier, your wallet address and where your latest request came from (below), and nothing else about you.

From where you are. Netlify, which hosts the site, tells it the country and region each request comes from. When you sign in and when you submit an entry, the site keeps the codes of that request on your profile — two letters for the country and a short code for the region — to screen payouts against sanctions law, as the terms describe. Nothing finer is kept: not the city, not a postcode, not coordinates, and not your IP address, which this site does not store. The next request’s codes replace them, and they are kept until your account is deleted. Screening downloads the U.S. Treasury’s sanctions list; nothing about you is sent to it.

From the site. Your byline, like quiet-lantern-4821, is assigned by the site from a word list and a random number, is derived from nothing personal — not your email, not your wallet, not your identifier — and can be re-rolled on your record until a night first credits you.

From using the site. Your entries and the scores they were given, your votes, the lines you back, the prompts you answer, and any award with the transaction that paid it.

From the moderator. The number of times you have asked it to read something today, kept as moderator_calls only to meter it against the daily limit, and reset every day.

From a share link. A link you share from a credited line carries a short code, eight characters the site gave your account at random and made from nothing about you. Only this site can follow it back to your profile; your wallet address is not in the link, and nobody given it can learn your address from it. If you first arrived by a link somebody shared, the site follows that code and keeps the sharer’s wallet on your profile as who brought you. Your record shows them by their byline and never by their address, and they see a count and not yours. It is a credit and never cash: nothing is paid for it and nothing unlocks. It is recorded once, when your account is created, and never changed.

From reading. While you are signed in, the number of the furthest night you have opened, kept so the front page can offer to pick up where you left off. One number and nothing else: not when you read, not which other pages you opened. It only moves forward, and it is deleted with the rest when your account is closed. Signed out, nothing about your reading is kept.

From writing to the operator. A message you send from your record and the operator’s reply. It is private: the two of you see it and nobody else, it is never public and it is never sent to a model. It is kept until you ask for it to go, and then it goes — nothing else depends on it.

From hosting. Netlify keeps request logs, which contain IP addresses and user agents, on its own retention rather than this site’s.

There are no analytics, no advertising trackers and no cookies of this site’s own. Your light or dark preference is kept in your browser’s local storage and never leaves it, and so is a plain note that this browser was signed in last time, so a returning reader is not shown the welcome first; it says nothing about who you are, and signing out removes it. A share link’s ?by= code is held in the tab you opened it in until you sign in, and sent once if you do. Privy sets what it needs to keep you signed in, and one route reads its identity cookie to know who is asking. The fonts are served by this site, built into it rather than fetched from Google, so reading a page tells Google nothing. If any of that stops being true, this page changes first.

Beside a used entry or a credited line: your byline, and the sentence the night made of your idea. Your wallet address is not printed beside it. One-liners are public in full — that is what they are for — and so are the one-word answers the site took until 24 October 2026. Vote counts are public; who voted for what never is.

On the treasury a payment shows the full wallet address it went to and the amount, permanently. The ledger is a public record, and the chain shows the same transfer whether or not this site does. That is the point of paying on one.

Never public: the text of a lore entry, a refused entry, any score or its reasoning, a message to the operator and its reply, and everything on your own record at /me.

• Privy — sign-in and wallets. It holds the email address or Discord account you sign in with; this site does not.
• Supabase — the database everything above is stored in.
• Netlify — hosting and request logs, and the country and region of each request.
• GitHub — the nightly pipeline runs on GitHub Actions, so your entries pass through its runners on the way to the models. The run log records which entries a night used, by their ids and how closely each matched the prose, and never their text.
• Anthropic — the narrative model that writes the nights. It receives the story so far, the entries read that night and the found material the night drew, and never anybody’s identity. After a night is published, a second Anthropic model reads it as a critic, from the published nights alone: no entry and no identity reaches it. Each night, a small Anthropic model also reads two of the ways the director has staged the night and says which reads better; what a night took from an entry can be in them, and nobody’s identity is.
• Google — the Gemini models score every entry before anything is used, checking in the same reading whether it is copied from somewhere else, and embed entries to check whether a night really used them. Your text is sent to Google for that. Google’s image model also draws the plate for each chapter of ten nights, and a Gemini model looks at each drawing before it is kept. The plate’s prompt is the house style, the description of the place written once for the book, and a description of what those ten nights changed there, both written by a Gemini model from the published nights and the readers’ decisions. Your entry is never sent for a plate, but what a night took from it can reach the nights and so a plate; the prompt never carries anybody’s identity.
• Cloudflare R2 — the illustrations and other media.
• A Solana RPC provider — wallet addresses appear in the requests that read and send on the chain. Your own browser reaches it directly as well as this site’s server does, so it sees your IP address and user agent, like any host you connect to.

Both models are used through a paid API — the Gemini key moved to a paid tier on 24 September 2026 — and each provider states its own rule for that use. Anthropic’s commercial terms, read on 24 September 2026, say it may not train its models on what customers send through its services — the terms, under Customer Content.

Google’s Gemini API terms, effective 23 March 2026 and read on 24 September 2026, say that on a paid service Google does not use your prompts or its responses to improve its products, and handles them as a data processor. It keeps prompts and responses for a limited time, and only to catch abuse of its usage policy and to meet legal requirements; that data may sit transiently in any country where Google keeps facilities. This holds while the key is on a cloud project with active billing, which it has been since 24 September 2026. On the unpaid tier the same terms say the opposite — content is used to improve Google’s products and people may read it — and that is what applied to this site before that date.

Entries are kept, because the credits in the nights and the rows on the ledger depend on them. There is no delete button, and that is a decision rather than an omission.

Ask the operator and, within thirty days, they will delete entries that were never used and never paid, delete your messages and their replies, and close your account so your Privy identifier no longer points at a profile. It is done by hand, not by a feature. Write to hello@proskoinos.ai.

Two things cannot be undone. A used entry stays credited under the byline it was credited to, because the night and the ledger are a record. And a payment that has been made stays on the chain, where nobody — including the operator — can edit it.

You can see everything held about you: your record is that page, and it is built for it. Nothing on it is a name you typed: your byline was assigned, and you can re-roll it there until your first credit. You can have what is listed above deleted, on the terms above. And if you live somewhere with a data protection authority, you can complain to it.

These are written to meet what rights of the GDPR’s and California’s kind ask for. The operator has not taken legal advice on which of them apply here, and would rather do the thing than name a statute they have not been advised on.

This site is not for anyone under the age of majority where they live. An account found to belong to a child is deleted.

A change to this page is posted here with its date, at the top. Nothing about what is collected changes without this page changing first.