Last updated: November 2026
In short: we only store what the meetups need. Other users never see your email address or your minimum group size, only how many people have signed up. We use no advertising cookies and no third-party analytics tools. We set a single cookie of our own to recognise returning visitors only if you allow it in the banner; the site works the same without it.
1. Controller
Simon Schillinger (MapShot), Armenhöfestraße 80, 77871 Renchen-Ulm, Germany
Email: info@mapshot.io
2. Account and login
For an account we only need your email address. It and your name are stored in our database only encrypted (AES-256); the key is kept separately on our server, so the database alone, for example in a data leak, contains no readable addresses or names. Instead of a password we send you a 6-digit code, which we store only as a hash and delete after one day at the latest. After logging in we set a session cookie (see section 8). Legal basis: performance of the user agreement (Art. 6(1)(b) GDPR). To prevent abuse we limit how often codes can be requested (Art. 6(1)(f) GDPR).
Alternatively you can log in with Google. We then send you to Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland), and after your consent Google passes us only your verified email address. It is stored, encrypted as above, as the address of your account; we receive and store no other data from your Google account. For this flow we set a cookie for at most ten minutes (see section 8). What Google processes is described in Google’s privacy policy. Legal basis: performance of the user agreement (Art. 6(1)(b) GDPR).
3. Profile
To take part we store your first name or nickname and the age group (18–29, 30–44 or 45+) you pick when signing up, and whether other age groups are fine for you too; we don’t ask for a year of birth or a gender. We keep the age group so it is preselected at your next sign-up; which group you pick is up to you. That you are at least 18 is what you confirm when creating your account. Your name is only visible to people who said yes to the same meetup, and only once it is certain to take place (about a day before): on the meetup page, in the meeting point chat under “Who can read this” and next to your messages (see section 4). Legal basis: Art. 6(1)(b) GDPR.
4. Sign-ups and groups
When you sign up for a meetup we store the place, date, age group, the time of sign-up, from how many confirmations you are in, and which meeting point you are assigned to. We also keep this minimum in your profile as a preset; others don't see it. For the Thursday series we store place, age group (or that any age group is fine) and minimum, a skipped week, how many invitations in a row went unanswered and whether the series is paused because of that, until you leave the series. Only the number of sign-ups per place and meetup is public.
The confirmation email contains the meeting point, time and group size, but no data about other participants. What you tell others at the meetup is up to you.
Meeting point chat: On Thursday from 6:45 to 7:30 pm (local time) the meetup page has a chat, in case you can’t find each other at the meeting point. Only people who said yes to the same meetup and are logged in see it (the link from the email alone is not enough); the chat shows their names so it is clear who reads along. When you write, they see your message, your name and the time. We don’t ask for your location for this. Messages are only kept in our server’s memory, not in the database and not in backups, and are deleted as soon as the chat closes. If someone reports a message, we store it encrypted together with its author, the person reporting it and the time, so we can review it (Art. 6(1)(f) GDPR, legitimate interest in safe meetups, and our obligation under Art. 16 DSA), and delete it after 7 days. Legal basis for the chat itself: Art. 6(1)(b) GDPR.
Confirmations
We store whether you said yes or no and whether your group met, until 90 days after the meetup. We do not record who actually showed up. Legal basis is Art. 6(1)(b) GDPR; we keep them for a while after the meetup to answer questions (such as why no invitation came) and to understand how groups come about (Art. 6(1)(f) GDPR).
5. Emails
We only send emails that belong to the service: login codes, the confirmation of your sign-up, invitations to confirm, a one-time note when no group comes together in a week, the confirmation or cancellation of a meetup, a reminder on the day of the meetup and a note when we pause a Thursday series after unanswered invitations. They are sent via our own mail server (mail.mapshot.io) and the delivery service SMTP2GO (SMTP2GO Ltd, New Zealand), which processes your email address and the message content for delivery in its EU data centre (Amsterdam). A data processing agreement is in place with SMTP2GO; insofar as access from New Zealand is possible, an EU adequacy decision exists for New Zealand. We keep a record of which of these emails went to which account and when, without the content, for 90 days, so that we can sort out delivery problems (Art. 6(1)(f) GDPR). We send no newsletters or advertising.
6. Hosting and database
When you open the site, our server processes technically necessary data such as IP address, time and requested address to deliver the page and keep it secure (Art. 6(1)(f) GDPR). The server is hosted by Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany) in a data centre in Germany; a data processing agreement is in place with Hetzner.
Account, profile and sign-up data are stored in a database at Neon (Neon Inc., USA) in a data centre in Frankfurt am Main, Germany (Amazon Web Services, region eu-central-1). A data processing agreement is in place with Neon. Where access from the USA is possible, we rely on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
7. Place search, meeting points and maps
The place search runs on our own server (Photon with data from OpenStreetMap). For new places we also request place data, public squares and bars on our own server (Photon and the Overpass API). The height of the meeting points also comes from our own server (elevation models EU-DEM and Copernicus). No data about you is transmitted.
Your browser loads the map (map data from OpenStreetMap and OpenMapTiles) from our own map server tiles.mapshot.io, which is also hosted by Hetzner Online GmbH in Germany. Your IP address is transmitted so that the server can respond; it is not stored there, the access log contains no IP addresses. Legal basis: our legitimate interest in a working map (Art. 6(1)(f) GDPR).
Fonts and all other parts of the site are served by us.
Places near you
Only when you tap “Near me” and allow your browser’s location request does our server receive your location, already rounded in the browser to about a kilometre (two decimals). We use it to find the town you are in and known places within 30 km. The name of the town for the rounded coordinates is looked up on Photon on our own server; only the rounded coordinates go to that server, not your IP address. The location is not stored, not logged and discarded after the answer. Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) of the German TDDDG), which you give with the permission in your browser and can withdraw there at any time; the site works just as well without it, you then type the place.
Visitor counting
We count page views per day and page, but only once the page has loaded in your browser (your browser briefly reports this to our server, without a cookie). Visits from data centres, mostly automated programs, are recognised by the network operator of the IP address (also via the local DB-IP database) and not counted. To count unique visitors per day, we create a hash from IP address and browser identifier using a
secret key that changes every day. We do not store IP addresses; the hash cannot be reversed or linked across days and is deleted when
the day is over, leaving only the daily total. With the same daily hash we count how many visitors per day reach each step towards a sign-up (saw a place page, pressed “I’m in”, login page, requested a code, logged in, signed up), each step once per visitor and day; these hashes are deleted when the day is over, too. We also count which website visitors come from (only its domain, e.g. “instagram.com”) or
which identifier is in the link (e.g. ?ref=…). We also derive a rough country and city from the IP address using a database on our own server (IP Geolocation by DB-IP, CC BY 4.0); the IP address is neither passed on nor stored, only “country/city: +1” is counted. Likewise, we count the first language your browser prefers (only the language code, e.g. “de”) and, from the user-agent string your browser sends anyway, the device class (phone, tablet, desktop) and operating system, without model or version. Finally, we count how often our own buttons are pressed (such as “WhatsApp”, “Copy link” or “Near me”), as a plain daily number. None of this sets a cookie, reads anything from your device or passes data to third parties (Art. 6(1)(f)
GDPR, interest in simple reach measurement and in seeing where people drop off).
Recognising you with your consent (cookie banner)
Only if you tap “Accept” in the banner do we set our own cookie tnm_vid with a random identifier (12 months). It tells us whether someone is here for the first time or again, on how many days, whether someone returns within a week, which source brought visitors who later signed up, and the width band of your browser window (e.g. “360–599 px”, no exact size). With this identifier we store neither your IP address nor your email address or account, only: first and last visit day, the individual visit days (90 days), the number of visit days, the first source and first page, the width band, and whether a sign-up happened from this browser (yes/no). The data stays on our server and is not passed to third parties. Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). You can withdraw it at any time via the “Cookies” link at the bottom of the page: we then delete the cookie and everything stored under the identifier; the daily totals counted until then remain, they no longer relate to you. If you tap “Decline”, none of this happens and the site works just the same. We remember your answer itself for 12 months in the cookie tnm_consent, so the banner does not come back on every page.
8. Cookies
Five cookies are technically necessary and therefore set without consent (§ 25(2) no. 2 TDDDG): tnm_session keeps you logged in until 90 days after your last visit, pending_join remembers for at most one hour which meetup you are signing up for while you log in, tnm_oauth secures the login with Google for at most ten minutes, tnm_known remembers for 12 months that you have logged in with this browser before (as a hash of your address), so that nobody can lock your login by entering wrong codes for your address, and tnm_consent remembers your answer in the cookie banner for 12 months. Only with your consent is tnm_vid added (section 7, “Recognising you with your consent”). All cookies are our own; there are no advertising or third-party cookies.
9. Retention
- Login codes: at most 1 day
- Sessions: 90 days after your last visit or until you log out
- Sign-ups and yes/no answers: until 90 days after the meetup
- Recognition (only with consent): identifier and its data until you withdraw, at the latest 12 months after the last visit; the individual visit days 90 days
- Account and profile: until you delete your account (possible at any time under “My meetups”), at the latest 12 months after your last login or visit while logged in; all sign-ups are deleted with it. If you delete it yourself, we keep for 90 days, without your name or address, only since when you took part, which places and age groups you were signed up for and how many invitations you got and answered in the last 90 days, so we understand why people leave (Art. 6(1)(f) GDPR). After that only the day an account was deleted and whether by the person or for inactivity remain, with no link to anyone.
10. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). Write to us at info@mapshot.io.
You can also lodge a complaint with a data protection authority, for example the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg (baden-wuerttemberg.datenschutz.de).
11. Minimum age
The service is only intended for people aged 18 and over.