Privacy

What is stored

Almost nothing. The site is static files. No cookies, no analytics, and the web server keeps no access logs.

Your browser’s localStorage holds three things: a via=card marker if you arrived via the QR code on the printed business card (the /c address); Daemon’s memory — the number of visits, the time of the last one and up to eight cases you have opened; and the ids of your requests (up to three, for at most 30 days), so the site can show Alexander’s answer on your next visit; once shown, they are forgotten. The marker and the memory let Daemon greet a card holder or a returning guest differently. All of it goes away when you clear the site’s data.

On the server there is only the history of the current conversation with Daemon, under a random identifier, not tied to a person. It is erased no later than a day after the last message (cleanup runs every ten minutes) and whenever the service restarts; IP addresses are not logged. The service only counts turns, money spent and the number of “miss” messages sent per day; per-address turn counters live in process memory until the end of the day and are never written to disk.

Daemon can guess who it is talking to — only if you ask, and only as a role from a short list. For that the service notes which rules fired (for example, “word ‘vacanc’” or “called about”), not your text; these notes live as long as the conversation.

Requests to Alexander for a call or a question (through Daemon or over MCP) are kept separately: the name, e-mail, the question or the call times and topic, and Alexander’s reply stay on the server for 30 days and are then erased. Only Alexander sees them, in Telegram. The name, e-mail and request text are never returned; status shows whoever holds the id only the decision, the call time and link, and Alexander’s reply. A copy of the notification stays in Alexander’s Telegram chat; he deletes it on request. To have a request erased sooner, write to the e-mail on the cover with its id or e-mail address: Alexander will delete it both on the server and in Telegram.

What goes to third parties

The text of a conversation with Daemon goes to the Anthropic API (USA), together with the card marker, your visit count, the list of cases you opened, today’s date and your browser’s time zone (the time of your last visit stays in the browser), and only from the moment you send your first message. Until you type something, nothing leaves: you can open the device and read the first line without that. A reminder sits above the input field until the first message. A name and e-mail you give in the conversation for a request go there too, like the rest of the text. If you ask Daemon about a request’s status, Alexander’s reply goes to the model too.

A request from the conversation enters the request queue, and from there Telegram (a service outside Russia; only Alexander sees it), only after you press “send” on the card yourself. Until then the draft is part of the conversation: it is dropped on “cancel” or after 10 minutes, and the conversation itself is erased within a day. A request over MCP is queued as soon as book_call or ask_alex is called.

The “miss” button on the guess card sends Alexander an anonymous Telegram message: the role Daemon named, its scores and signals, the role you picked (or “won’t say”) and up to 200 characters of your text — links are replaced with “[link]”, and there are no conversation identifiers or IP addresses in it. The role you pick also goes to Daemon — to Anthropic, like the rest of the conversation. It can be sent once per conversation; on the server it waits until it is delivered and no longer than 7 days, and a copy stays in Alexander’s Telegram chat.

Guestbook

There is no guestbook yet; when there is, its entries will live in a public repository and be removed at the author’s request.

Contact

Questions go to the e-mail on the cover page.