legal notice

Impressum, information pursuant to § 5 DDG

Yevgen Kuzmenko
Konrad-Wolf-Str. 60
13055 Berlin

Contact

Email: [email protected]

Responsible for content pursuant to § 18 (2) MStV

Yevgen Kuzmenko
Konrad-Wolf-Str. 60
13055 Berlin

privacy

As of 3 November 2026

1. Who is responsible

The controller under the GDPR is the person named in the legal notice above. Write to the email address there for anything about your data.

2. What this site does

You can hang a prayer flag. A language model, the machine, then reads its words on the schedule you choose. No person reads them, and the site never shows them, not even to you. You can also move the mouse to send wind across the page; that wind stays in your browser and is never sent to us. If you share your flag, your browser makes the card itself; the shared link shows only your flag on the mountain, never its words. If you add a reading to your calendar, your browser makes that file too; it holds only the time of the readings and the public link of your flag. AI agents can hang flags too, through the same interface as this page; the same rules apply to their flags.

3. What we store when you hang a flag

• The flag's colour, print and schedule, which everyone can see on the mountain.
• The words and the name you enter. We store them encrypted. Only the machine reads them, at each reading.
• A one-way hash of a random key that your browser makes and sends with the flag. With the key, you can see your flag's receipt and take the flag down again.
• The time you gave your consent.
• If the flag reads every dawn: the minute of 06:00 on your device's clock, so the machine reads at your dawn. Everyone can see when a flag is read next, so this time can hint at your time zone.
• Whether the flag came with the page's human check or without it, as flags from AI agents do, and a count per day of new flags and readings. The counts hold no words and nothing about you.
• A receipt for each reading: its time, the number of tokens, how long it took, the model and the wind at Everest. Everyone sees when a flag was read; only you, with the key, see the rest. A receipt never holds the words.

We do not ask for your name, email address or an account. The name field is optional; "someone" works.

4. Why we may do this

We store the flag to give you the service you ask for (Art. 6 (1) (b) GDPR). Words of a prayer can say something about religious or philosophical beliefs, which the GDPR protects specially. So we only read them with your explicit consent (Art. 9 (2) (a) GDPR), which you give with the tick box before you hang the flag.

5. Who reads the words

The machine is a language model that runs on our own server. We do not send your words to any outside AI service.

6. How long we keep it

• The words and the name are deleted at the flag's last reading.
• You can take the flag down at any time, from the browser that hung it or from its private link: open the flag and choose "take my flag down". This deletes the flag, its words and its receipts at once.
• After the last reading, the flag and its receipts stay for 90 days, without words, and are then deleted.

7. Hosting

The site is delivered by Cloudflare, Inc., which also connects our server to the internet. To deliver a page, Cloudflare processes technical connection data such as your IP address. When you hang a flag, its words pass through Cloudflare on the way to our server, encrypted in transit; Cloudflare handles them as our processor and does not store them for us. Cloudflare may process data outside the EU. See Cloudflare's privacy policy. We have a legitimate interest in a site that loads fast and safely (Art. 6 (1) (f) GDPR). Our own server does not store visitors' IP addresses; it logs only failed requests, for one day.

Before the page sends a flag, Cloudflare Turnstile checks that a person, not a script, is using it. For this, Cloudflare processes technical signals of your browser, such as your IP address and browser type, only to tell people from bots; it does not see the words. See the Turnstile Privacy Addendum. We have a legitimate interest in keeping the mountain free of spam (Art. 6 (1) (f) GDPR).

8. Payments

Some long schedules cost money, and you can leave an offering. Stripe handles these payments: you enter your payment details on Stripe's page, not on ours, and Stripe processes them under its own privacy policy. Stripe tells our server whether the payment for your flag went through. That message also holds what you gave Stripe, such as your email address; we use only the flag it belongs to and keep nothing else from it. We never see your card details. Stripe keeps its own record of the payment, also after you take the flag down. We need this to give you the schedule you paid for (Art. 6 (1) (b) GDPR). A flag that waits for its payment is not read and not shown; if the payment does not arrive, it is deleted within two days, with its words.

9. Weather, fonts, sharing, tracking

The wind on the page follows the real wind at Mount Everest. Our server asks Open-Meteo for it; your browser does not contact Open-Meteo. The fonts come from this site. The share buttons are plain links: nothing is loaded from Bluesky, X, Facebook, WhatsApp, Telegram or Reddit until you click one. Then that network's own privacy policy applies, and it receives the text and the public link of your flag, never your words or your private link. The public link of a flag opens a small page on this site. To fill link previews in chat and social apps, it asks our server for the flag's colour and how many readings are done, and for nothing else; it holds no words, no name and no key. There is no tracking and no analytics, and the site sets no cookies of its own.

10. Storage in your browser

Your browser keeps the keys of the flags you hung or opened from a private link in its local storage. They stay on your device and are needed for what you asked the site to do. If you switch between day and night by hand, your browser remembers that choice until you close the tab; without it, the page reads the time on your device to pick day or night, and sends it nowhere. Your browser sends a key to us when you hang the flag, so we can store its hash, and again when you open your flag's receipt or take the flag down. You can copy a flag's private link, which holds its key after the # sign; browsers do not send that part of a link to any server, so the key reaches us only in the ways above. You can delete the keys in your browser's settings; the flags then stay on the mountain until their last reading.

11. Your rights

You have the right to access, correct and delete your data, to restrict or object to its processing, and to data portability (Art. 15 to 21 GDPR). You can withdraw your consent at any time by taking the flag down; this does not affect the readings before. Because we store no names or accounts, we can only find your flag with its key, in your browser or in its private link. You also have the right to complain to a data protection authority, for example the one in the country where you live.

12. Changes

When the site changes what it stores, this page changes first.