Privacy policy

1. Who is responsible

The controller for allay.chat is Pavel Erokhin Viktorovich, in Spain. You can reach us atpersonal@mairwunnx.com about anything on this page.

“Allay” here means the hosted backend at allay.chat, this website, and the Telegram bot @AllayChatBot. The Allay plugin and Allay Server are open-source software. When you run your own backend, it sends nothing to us, and you are the controller for what it keeps.

2. At a glance

3. This website

The website sets no cookies, runs no analytics, and loads no fonts, scripts, or images from other companies. If you pick a light or dark theme, your browser remembers it in its own storage; it never reaches us.

Cloudflare delivers the pages and protects them from attacks. To do that it processes your IP address and the details of each request, as any web server does. We rely on our legitimate interest in a working, secure website (Art. 6(1)(f) GDPR). We don’t keep request logs for the pages ourselves.

The wiki pages show pictures from the Allay wikis on GitHub. When a page has one, your browser loads it from raw.githubusercontent.com, which sees your IP address.

4. Players on servers that use allay.chat

A Minecraft server’s operator decides to connect the Allay plugin to allay.chat. For the answers themselves we then work on that operator’s behalf, and the operator is responsible for telling its players. Our terms include the data processing agreement for this. We describe everything here so you know what happens either way.

What a question sends us

• The player’s Minecraft UUID and name, their language, and their time zone.
• The question, and the answers of the game tools Allay asks for: the inventory, health, surroundings, coordinates, notes, goals. Other players appear only as the asker’s locator bar shows them: a name, a distance, and a direction.
• The server’s name and a random id the plugin makes for it, and the plugin’s version.
• For a public question (/askall), the question and the answer, which every player online sees in the game.

What we keep

• The session. Whole exchanges, tool results included, so a follow-up question makes sense. It ends 24 hours after the player’s last question. Long sessions fold into a short summary. A server’s thread of public questions and each automation agent’s thread end 2 hours after their last use.
• The lasting memory. Up to 30 short facts per player, which Allay saves when it learns something useful and says so. They stay until the player deletes them with /allay forget or asks us to, and go by themselves 365 days after the player’s last question.
• The agreement. Since Allay 6.1 the plugin shows each player a short notice before their first question: what it sends, where we keep it, and that AI providers write the answers. Allay answers only once the player agrees. We keep which version of the notice they agreed to and when, for the server’s operator, until the player withdraws it with /allay privacy withdraw or their data is erased.
• Statistics. One record per answer with numbers only: when, the model, tokens, cost, duration, which tools ran and whether they worked, the error code if any. The player appears as a pseudonym, a keyed hash of their UUID that can’t be turned back without our key. Records go after 400 days; daily totals with no player in them stay.
• Traces. For 10% of answers, picked at random, a full record of the run: the prompts, the model’s output, and each tool call with its arguments and result. They help us find and fix errors and are deleted after 7 days. Keys are removed before a trace is saved.

Each server’s data is kept apart: the same Minecraft account on two servers is two players, and no server reaches another’s. Nobody sees what players asked or what Allay answered in our admin panel, whatever their role: it shows numbers and the shape of a run only. The backend’s logs carry no player’s name, id, question, or answer.

Why

To answer a question, we follow the server operator’s instructions under the data processing agreement (Art. 28 GDPR). Statistics, limits, and traces serve our legitimate interests in billing correctly, preventing abuse, and keeping the service working (Art. 6(1)(f) GDPR).

5. Server operators who pay or bring a key

Subscriptions

/allay link creates a license: a random id, a hash of its secret (never the secret itself), the server’s name, the plan, its budget, and what was spent. When you claim it in @AllayChatBot, we store your Telegram user id, the chat id, and your language, so the bot can talk to you and send renewals. For each payment we store Telegram’s charge id, the plan, the number of Stars, the date, whether it renews, and any refund.

You pay inside Telegram. We never see card details; Telegram, and Apple or Google when Stars are bought in their stores, handle the money.

We need this to provide the subscription (Art. 6(1)(b) GDPR) and keep payment records as tax law requires (Art. 6(1)(c) GDPR). License data stays while the license exists; payment records stay for six years after the payment, as the Spanish Commercial Code requires.

Your own key

With your own key, the plugin sends it with each question. We use it for that one answer and never store or log it. The requests then go to the provider you picked, under its terms. Since Allay 6.0, such a server also gets a free license that tells us which server asks; it holds no payment data until someone pays.

Addresses

The backend uses the IP address a request comes from to limit how many licenses and sign-in attempts one address may make. It keeps those counts in memory only. Our admin panel’s audit log records which staff account changed what, from which address, for 365 days.

6. Who else processes data

We use these services, each bound by a data processing agreement or its own terms:

• Hetzner Online GmbH, Germany: the server that runs the backend and its databases, in Helsinki, Finland.
• Cloudflare, Inc., USA: the website, DNS, protection from attacks, and the encrypted tunnel to our server. Requests to allay.chat pass through it.
• OpenRouter, Inc., USA: forwards each answer’s context (the question, the session, tool results, and remembered facts) to the AI model that writes the answer, and to the model that summarizes long sessions. Which company runs the model depends on the model in use.
• Perplexity AI, Inc., USA: when Allay searches the web, it receives the search query Allay wrote, not the conversation.
• Telegram: runs @AllayChatBot and Telegram Stars. Telegram processes your account and payments as a controller of its own.

Some of them are in the USA. Transfers rely on the EU–U.S. Data Privacy Framework where the company is certified, and on the European Commission’s standard contractual clauses otherwise (Art. 45 and 46 GDPR).

7. Your rights

You may ask us what we hold about you, have it corrected or deleted, restrict its use, receive it in a portable form, and object to processing based on legitimate interests (Art. 15–21 GDPR). You may also complain to a data protection authority, for example where you live, or to ours: the Agencia Española de Protección de Datos (aepd.es).

Players can do the most common things themselves in the game:

• /allay privacy says what Allay keeps about them on that server, and /allay privacy erase erases all of it (Allay 6.0 and newer).
• /allay privacy withdraw takes back their agreement to Allay’s notice, and Allay stops answering them (Allay 6.1 and newer).
• /allay memory lists what Allay remembers, and /allay forget deletes it.
• /allay new ends the current session.

A server’s admins can export or erase a player’s data for them with /allay privacy export and /allay privacy erase.

For anything else, such as a copy of everything we keep about you, write to personal@mairwunnx.com with your Minecraft name or UUID, or your Telegram user id. We may ask you to prove the account is yours. On erasure, your memories, sessions, agents’ threads, and the traces of your questions go, and your statistics lose even their pseudonym.

8. Automated answers

Allay’s answers are written by AI models and can be wrong. They make no decision about you with legal or similarly significant effects (Art. 22 GDPR). When a subscription’s limit is used up, hosted answers pause for that server until the budget refills; that follows from the plan, not from a judgment about anyone.

9. Children

Many Minecraft players are young. Allay collects the same little from everyone and asks no one for an email, a real name, or a birthday. Paying for a subscription takes an adult, or a young person with a parent’s permission where the law asks for it.

10. Security

• All traffic to allay.chat is encrypted on its way.
• Secrets saved in the admin panel are encrypted at rest; license secrets are stored only as hashes.
• Statistics use pseudonyms; traces are kept for 7 days only.
• Only our own staff have admin accounts, and the panel never shows what players asked.

11. Changes

When the backend starts storing something new or keeps it longer, this page changes first, and the date at the top moves. For a change that matters to paying servers, we also tell them through @AllayChatBot.