DO TODAY

Privacy

What we hold about you, why, and what you can make us do about it. This is the binding version.

⚖️ Formal📄 Clearbinding version💬 Human

1. Who is responsible

Do Today is operated by We make AI work s.r.o., ID No. (IČO) 29697115, registered office Nové sady 988/2, Staré Brno, 602 00 Brno, Czech Republic, registered in the Commercial Register kept by the Regional Court in Brno, Section C, Insert 152497. Contact: service@dotoday.eu. We are the data controller for everything described below. We have not appointed a data protection officer; service@dotoday.eu reaches the person accountable.

2. What we collect

Without an account: nothing that identifies you. We count calendar views as a daily total per country — no cookie, no IP address, no per-visitor record. With an account: your email address, your password stored only as a salted PBKDF2 hash (we cannot read it), optionally a separate "calendar email" you choose for invites, the events you favourite, and a session token. If you suggest a town we store your suggestion and, if you give one, an email to reply to. If something breaks we log the error message, the page path and a request id; email addresses and long digit strings are stripped from those logs automatically. If you buy paid access: a record of each payment you start — Mollie's payment id, the amount and currency, its status (open, paid, failed, refunded and so on), when it was started and paid, and the coupon if you used one — linked to your account. For every paid payment we also issue a numbered receipt holding the receipt number, the email address you paid with, the amount, the date, the language and the coupon code. Your card or bank details go to Mollie and never to us. If you pay with just an email address, we create an account for that address. We also keep a log of changes to accounts and payments (what happened, when, to which account); it holds no email address. We also count views of each town page, weekend page, event page, widget and town calendar feed, as a daily total per town and page — again no cookie, no IP address, no per-visitor record. If you switch on the weekly mail, we store that you did, when, and the language you chose for it.

3. Why, and on what legal basis

We use your email and password to run your account and let you log in — that is performance of our contract with you (Art. 6(1)(b) GDPR). We send calendar invites to the address you chose, because you asked us to, each time you favourite an event — also contract. We keep aggregate view counts and error logs to keep the service working and secure, which is our legitimate interest (Art. 6(1)(f)); neither identifies you. Payment records exist so that your paid year switches on and a payment can be traced or refunded — contract (Art. 6(1)(b)). Receipts are the seller's record of the sale that Czech accounting law requires us to keep — legal obligation (Art. 6(1)(c); Act No. 563/1991 Coll., on Accounting). The change log lets us show who changed what in accounts and payments — our legitimate interest in accountability and security (Art. 6(1)(f)). We do not profile you, we do not advertise to you, and we never sell or share your data for anyone else's marketing. If your bank or card issuer reverses a payment (a chargeback): which payment, Mollie's chargeback reference, the amount reversed, the fee Mollie charged us (and the Czech National Bank rate if we converted it), when your access paused and what it had left then, the payment link and the payment that settled it, when we mailed you about it, and how it ended - paid, reversed by your bank, or waived, with support's reason. To pause and restore your access exactly as the terms say (Reversed payments), to ask only what is owed and never more than Mollie charged us, and to record why a justified reversal cost you nothing - contract (Art. 6(1)(b)) and our accounting duty (Art. 6(1)(c)). As long as the payment record it belongs to (accounting law). Deleting your account unlinks it from you; the money history itself stays. Your passkeys: public key, credential id, signature counter, transports, device type, backup flag, an optional label, when added and last used. The private key never leaves your device; no fingerprint or face data ever reaches us. Why (purpose): prove it is you; notice a cloned key. Legal basis: contract · legitimate interest (security). Kept for: until you remove it or are erased. Sign-in challenges (random, single use). Why (purpose): one passkey ceremony. Legal basis: contract. Kept for: valid 5 minutes; deleted a day after it expires. The per-town counts show us which calendars people use — legitimate interest (Art. 6(1)(f)); they identify no one. When your paid year is about to end we email you twice, 14 and 3 days before, so you can renew if you want — contract (Art. 6(1)(b)); nothing renews by itself. The weekly mail about the coming weekend in your favourite towns goes out only because you switched it on — consent (Art. 6(1)(a)); every mail has a one-click unsubscribe link, and you can switch it off on your account page at any time. If you sign in with an email link: a hash of the one-time link we mail you (never the link itself), the address it went to, a hash of a random marker your browser holds so the link signs you in at once only there, and when it was made, used and expires. Why (purpose): sign you in, or create your account on its first use, without a password. Legal basis: contract (Art. 6(1)(b)). Kept for: valid 15 minutes and used once; deleted a day after it expires. If you choose to sign in with Google: the account id Google gives us for you and your email address. We never receive your Google password. Google itself learns that you signed in to Do Today - under Google's own privacy terms, which you accept at Google. Why (purpose): let you sign in with the account you chose. Legal basis: contract (Art. 6(1)(b)). Kept for: until you remove the connection or your account is erased. Google is an independent controller (USA, EU-US Data Privacy Framework). When you confirm a purchase, we record the sentence you confirmed (what you get, the price, any code, when it starts), its language, the date of the terms in force, the version of the site that showed it, when you confirmed, and the payment it belongs to. Why (purpose): to be able to prove what was agreed. Legal basis: contract and our legal duty to keep accounting records (Art. 6(1)(b) and (c)). Kept for: as long as the payment record; if you delete your account, it stays without any link to you.

4. How long we keep it

Account data stays until you delete your account or ask us to delete it. You can do it yourself from the account page: that removes, at once, your account and your email address — from the account and from the change log, which then keeps only what happened and when — together with your favourites, your sessions and any password-reset links. Records of payments that did not go through are deleted too. All that stays is what Czech accounting law makes us keep: the records of payments that went through and their receipts (a receipt shows the email address you paid with), for as long as that law requires. Session tokens expire after 30 days, are deleted when you log out, and expired ones are swept hourly. Error logs are kept for 90 days and then deleted automatically. Aggregate view counts contain no personal data and are kept indefinitely. Your weekly-mail choice is deleted with your account.

5. Who else touches it

Scaleway hosts the site and stores the database. Scaleway TEM delivers the emails we send you. Bunny (BunnyWay d.o.o., Slovenia) is the content delivery network in front of the site and runs our DNS — your browser talks to its edge first, so it sees your IP address and the page you request, nothing more, and EU visitors are served from EU nodes. DeepL translates event titles — it receives event titles only, never anything about you. OpenStreetMap serves the map tiles — when you open the map view your browser fetches them directly, so they see your IP address and the area you are looking at, and nothing else about you; open no map and they are never contacted. If you click a partner link (accommodation or ticketing) you leave our site and that company's own privacy policy applies from that click on. These providers act on our instructions under data processing agreements; where processing happens outside the EEA it is covered by the European Commission's standard contractual clauses. Mollie B.V. (the Netherlands) handles payments: you enter your card or bank details on Mollie's own checkout page, and from us Mollie receives only the amount, a description of the purchase and our internal number for your account — not your name or email address. Mollie is not one of the providers above: for the payment itself it is an independent controller under its own privacy policy, and it keeps its own record of the payment.

6. Your rights

You can ask us for a copy of your data, correct it, have it deleted, restrict or object to how we use it, and receive it in a portable format. Write to service@dotoday.eu; we answer within one month. If you are not satisfied you can complain to your local data protection authority, or in our case to Úřad pro ochranu osobních údajů, Pplk. Sochora 27, 170 00 Praha 7 (uoou.gov.cz).

7. Cookies and what stays on your device

One essential cookie when you log in, plus a few preferences stored locally in your browser (your language, your country, your consent choices). No advertising cookies, no analytics cookies, no third-party trackers. The Cookies page lists every single one and lets you change your choices.

8. Security, changes and contact

Traffic is encrypted in transit, passwords are hashed and never stored in readable form, and the session cookie is HttpOnly, Secure and SameSite-restricted. If a breach ever puts you at risk we will tell you and the authority within the deadlines the law sets. We update this notice whenever what we collect changes, in the same release as the change itself. Questions: service@dotoday.eu.

Last updated: 2026-10-27 · We make AI work s.r.o., IČO 29697115