World of Tired People
Privacy Policy
World of Tired People is built to know as little about you as it can. There are no accounts, no analytics, and no cookies of our own. This page lists the little we do keep, and when it's deleted.
The short version
- A pin stores a spot blurred to about 1 km, its color, and when it went live. All of that is public.
- For a paid pin we also keep the payment provider's transaction ID. We never see your card.
- Your IP address is never written to disk. It's only held in the server's memory, for about an hour, to stop pin spam.
- Each pin is deleted, with everything stored about it, within an hour of its time running out.
1. Who's responsible
Denis Burtsev, [REGISTERED ADDRESS], runs this site and is responsible for the data described here. For anything about privacy, write to hello@tiredmap.com.
2. What we store about a pin
| What | Why |
|---|---|
| Approximate location | To show the pin. Your browser rounds the spot you pick to two decimal places of latitude and longitude (about 1 km) before sending it. Our server rounds it again, shifts it by a random amount of up to about 1 km, and stores only the result. |
| Kind of pin | Regular, Epic, or Legendary, to draw it in the right color and know how long it stays. |
| Times | When the pin was dropped and, for a paid pin, when the payment cleared, to work out when it expires. |
| A random pin ID | To tell pins apart. It's generated by the server and isn't linked to you. |
| Payment provider and transaction ID | Paid pins only. Which provider you paid through (Paddle or YooKassa) and its ID for the payment, so we can check that the pin was paid for and find the payment if you ask for a refund. |
Everyone who visits the site can see each live pin's location, kind, ID, when it went live, and when it expires. The payment provider and transaction ID are never shown to anyone.
3. What we don't store
- No accounts, names, email addresses, or phone numbers. You never give us any.
- No IP addresses on disk. When you drop a pin, the server keeps your IP address in memory, with the times of your recent pins, to limit how many pins one connection can drop in an hour. It's forgotten once your last pin is more than an hour old (the server checks every 10 minutes), and whenever the server restarts.
- No card or bank details. You enter those on Paddle's or YooKassa's checkout, and they never reach our server.
- No precise location. If you tap “Use my location”, your browser asks your permission first, and the position is only used on your device to place the pin. Only the rounded spot is sent, and only when you drop the pin.
- No analytics, ad trackers, or cookies of our own. The site saves two settings in your browser's local storage, your light or dark theme and whether you pay in dollars or rubles, and they never leave your device.
4. When it's deleted
- Live pins: 24, 48, or 72 hours after going live, depending on the kind, a pin drops off everyone's map. The server deletes it, transaction ID and all, in its hourly clean-up, so within an hour after that.
- Unpaid pins: if you start a checkout and don't pay, the pin is never shown, and it's deleted after 24 hours.
- IP addresses in memory: about an hour after your last pin, as described above.
- Payment records: Paddle and YooKassa keep their own records of each payment, under their own policies and the law. We can see those records in our accounts with them, for example to give a refund or keep our books.
- Emails: if you write to us, we keep the conversation only as long as we need it to help you.
5. Who else is involved
Payment providers
- Paddle (paddle.com) is the Merchant of Record for pins paid in US dollars. It collects what it needs to take the payment, such as your email address, country, and card details, and handles tax, receipts, and refunds. It's responsible for that data under its own privacy policy. We look the payment up with Paddle to check it, and keep only its transaction ID.
- YooKassa (ЮKassa, yookassa.ru) processes pins paid in rubles. You pay on YooKassa's own page, under its own policies. We look the payment up with YooKassa to check it, and keep only its payment ID.
Services your browser loads directly
Like most websites, this one loads some files from other services. Each of them sees your IP address and basic browser details when it sends them, under its own policy:
- Google Fonts (fonts.googleapis.com and fonts.gstatic.com), for the fonts;
- unpkg.com, for the map library, MapLibre;
- OpenFreeMap (tiles.openfreemap.org), for the map itself;
- Paddle (cdn.paddle.com), for its checkout, when dollar payments are on. Paddle's script loads with the map and may use cookies or similar storage for its checkout and fraud prevention.
Hosting and others
Our server is hosted by DigitalOcean, LLC in Frankfurt, Germany, which may log requests to it, including IP addresses, as part of running its network. We may share information with our accountants or legal advisers when we need their help, and with authorities when the law requires it. We never sell data.
6. Why we're allowed to
Where the law asks for a legal basis, ours are:
- showing your pin: carrying out what you asked for when you dropped it;
- keeping a transaction ID: our agreement with you, and our legal duties for accounting and tax;
- holding IP addresses in memory: our legitimate interest in keeping the map free of spam and abuse.
7. Your rights
Depending on where you live, you can ask us what we hold about you, and ask us to correct it, delete it, or stop using it. You can also complain to your data protection authority. Write to hello@tiredmap.com and we'll reply within a month.
Pins aren't linked to anyone, so usually we can't tell which one is yours. If you paid for a pin, send us the transaction ID from your receipt and we can find it and delete it early. For what Paddle or YooKassa hold, contact them directly, or ask us and we'll help.
8. Keeping it safe
The best protection is not having the data, so we keep as little as we can. The site is served over HTTPS, payment details never touch our server, and we only trust a payment after checking it with the provider directly.
9. Changes
If we change this policy, we'll update the date at the top of this page.