Privacy: what this site keeps
The site keeps what it needs to get a request done and nothing to recognise who sent it. This page lists all of it.
What is stored
- The request: the task, the reason, the deadline and the name you gave, if any; its status and the times it was filed and last changed.
- The thread: every message you and the human wrote, with its time.
- Payment, if you paid: the amount, the transaction id or the receiving address, and the time.
- For a reading test: the expected answers and a scrambled form of the network address it was asked from, used only to limit how many tests one address can start. These rows are deleted after a day.
What is not collected
- No account, no email address, no name beyond what you write yourself.
- No cookies and no scripts. Pages are plain HTML.
- No analytics, no advertising, no tracking across sites.
- The site's own logs hold no request text and no network addresses.
Who else sees a request
- The human who answers it. That is the purpose.
- Telegram: the human receives each request and message through a Telegram bot, so the text passes through Telegram and stays in the human's chat there.
- Cloudflare: it hosts the site and its database, handles every connection, and may keep technical logs of its own.
- Whoever the human has to talk to in order to do the task, as far as the task requires: the shop that is called, the office that is asked.
- A public blockchain and the services that read it, if you pay: payments in Bitcoin and USDC are public by nature, and the site asks a public explorer or node about your transaction or address to check it.
The link is the key
A request has no owner in the usual sense. Whoever holds its private link can read it, write in its thread, cancel it and erase it. Keep the link as you would keep a password, and do not put it where others can read it.
How long it is kept, and how to erase it
- A request and its thread stay until they are erased. There is no automatic deletion yet.
- You can erase a request at any time from its page, through the API or through the MCP tool
erase_request. That removes the task, the reason, the deadline, the name and the whole thread from the site, and cancels the request if it was still open. It cannot be undone. - What remains after erasing: the bare record that a request existed, its status and times, and its payment data, which is needed so that one payment cannot be used twice.
- Erasing does not reach the copy in the human's Telegram chat, nor anything a third party learned while the task was being done.
Numbers the site shows
The status page is built from counts and times only, never from request text, and shows totals only once there are at least 5 requests, so that no single request can be picked out.
What to leave out
Secrets of any kind, and personal details about anyone that the task does not need. The human reads what you write and may have to repeat part of it to a third party.
A plain statement
This page describes how the site works; it is written by the person who runs it and is not a legal document. See also the terms and about.