Privacy Policy
Last updated: 19 November 2026
The legally binding version is German.
This privacy policy applies to the Regional.Events website and web app at https://regional-events.de, which you can use in your browser or install on your device, to our information and sign-up pages (see 3) and to the Regional.Events app from Apple's App Store and from Google Play. Last updated: 19 November 2026.
Contents: 1. Controller · 2. Overview · 3. Information and sign-up pages · 4. Regional.Events app and platform · 5. Recipients and processors · 6. Transfers to third countries · 7. Retention · 8. Legal bases · 8a. Required information, no automated decisions · 9. Your rights · 10. Children and young people · 11. Security · 12. Changes to this policy
1. Controller
The controller responsible for processing your personal data within the meaning of the General Data Protection Regulation (GDPR) is:
Regional.Events 365 UG (haftungsbeschränkt)
represented by its managing director Jonas Schmitz
Friedrich-Mohr-Straße 1
56070 Koblenz
Germany
Phone: +49 261 13490497
Email: info@regional-events.deWe have not appointed a data protection officer because we are not legally required to do so. For any data protection question and to exercise your rights, contact us at info@regional-events.de or at the address above.
2. Overview
Regional.Events is the regional platform for events and community. On the website we provide information about Regional.Events and accept sign-ups and enquiries. In the app you find events in your region, arrange to meet and talk with others, and organisers, clubs and providers can present themselves and their events.
Our principles:
- We only process the data we need for each feature.
- We use no advertising SDKs and no third-party tracking services, build no user profiles for advertising, do not use your device's advertising ID and do not sell or pass data to data brokers. Exceptions are the measurement of our own advertising with Meta under 4.14a (it applies only while we have switched it on, only on the website and only with your consent) and the redirect of ticket links through the partner network Awin under 4.6, when you yourself tap such a link.
- Audience measurement in the app only runs with your consent and counts without identifiers that recognise you.
- We do not store your location on our servers. It stays on your device only briefly, for example for the first seconds when the app starts or for a check-in without signal (see 4.6, 4.7 and 4.9).
- You can delete your account in the app at any time and export your data there.
3. Information and sign-up pages
Since 12 November 2026, regional-events.de is home to the Regional.Events platform (see 4). Our information and sign-up pages (for example guides, press, meetups and the enquiry forms) are linked from there; until further notice they are served at launch-regional-events.vercel.app, also by Vercel. This section 3 applies to those pages.
3.1 Hosting and server logs
The website is hosted by Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA. The website's server functions (such as processing forms) run on servers in the European Union in Frankfurt am Main. Page content and images are delivered through Vercel's global delivery network, for visitors from Europe usually from European locations.
When you visit the website, Vercel automatically processes data your browser sends and stores it in server logs: IP address; date and time of access; requested address and HTTP status code; amount of data transferred; browser type and version, operating system; the previously visited page (referrer), where your browser sends it.
We need this data to deliver the website, keep it secure and running, and fend off attacks. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in the technical operation and security of the website. Logs are deleted after 30 days at the latest. We have a data processing agreement with Vercel under Art. 28 GDPR.
3.2 Cookies and browser storage
The website and web app use the same functions and browser storage (see also 4.9). Automatic language detection sets no language cookie. Only when you explicitly choose German or English on this device do we save your choice in the
NEXT_LOCALEcookie, until you close the browser. Applying the language choice already saved in your account does not set this cookie. If you choose settings in the “Accessibility” menu, we store them underre-barrierefreiuntil you reset or delete them.Local storage also contains
re:region-v1(the selected region or the region determined on opening, until you delete the entry) andre.held.v1|…(the last loaded Home, Discover and Rewards views, separated by version, language and active account; deleted on sign-out or account switch). This keeps the region and lets the last loaded view appear immediately. Messages and Profile are not stored this way. These entries are not sent to us as usage statistics; details of functional storage are in 4.9 a).While “Remember on this device” is switched on (the default, see 4.9 b), we store
re:app-opens-v1in local storage andre:app-open-counted-v1in session storage. They count openings on this device so that the “Allow location” card does not appear too early, and are not sent to our server. The local counter remains until deletion or until you switch “Remember on this device” off; the session mark ends when you close the window. While “Remember on this device” is switched off, we keep no opening counter. Instead, the location card may appear after 30 seconds on Home; the waiting time stays only in the open page’s volatile memory. Your answer or “Not now” on the location card is stored separately underre:location-ask-v1until deletion, so that the app respects your answer. You can find the “Remember on this device” switch in the menu under “Cookie settings”; the other storage purposes and deletion options are described in 4.9.3.3 Fonts, videos and links to social networks
We serve the font, the home page video and all images of the website from our own server. We do not embed content from Google Fonts, YouTube, TikTok or map services. We show an Instagram post only with an event based on that post, and only once you load it yourself (see 4.21). The offline map of your region (OpenStreetMap data, © OpenStreetMap contributors, ODbL; map style Protomaps) is loaded once as a file from our own server at Hetzner Online GmbH; your device does not connect to OpenStreetMap or any map service for it. The small map on which organisers confirm their event's location is loaded from OpenStreetMap through our own server; your device does not connect to OpenStreetMap for it, and OpenStreetMap learns neither your IP address nor who is looking at the map. We only link to our profiles on Instagram, YouTube and TikTok with simple links. Only when you click such a link are you taken to the provider, whose privacy terms then apply.
3.4 Forms and sign-ups
On the website we offer these forms: launch reminder, add an event, add a provider, Crew sign-up, sign-ups for our online meetups (for regions and networks and for the Crew) and a request for a one-to-one call. Depending on the form we process: first and last name and email address; phone number with country code (optional); region; name and date of an event (add an event); company or organisation (add a provider; optional for meetups and calls); social media profile, preferred roles, prior experience and interest in the affiliate programme (Crew sign-up); chosen meetup date and optionally area and role (meetup sign-ups); preferred date, preferred contact channel and optionally suitable times and your topic (one-to-one call).
Together with the form your browser transmits how you reached us: the landing page on regional-events.de, an external referrer and, if present, campaign parameters from the address (utm_source, utm_medium, utm_campaign). Each request also receives a random identifier so that an accidental double submission is not stored twice. We use the origin information to understand how sign-ups reach us.
We use your details to handle your enquiry or sign-up, notify you about the launch of Regional.Events, manage your meetup attendance and arrange a requested call. The legal basis is Art. 6(1)(b) GDPR where processing serves your sign-up or preparing a collaboration, and otherwise your consent under Art. 6(1)(a) GDPR, given by submitting the form (in particular for the launch reminder). For origin information the legal basis is Art. 6(1)(f) GDPR. You can withdraw your consent at any time with effect for the future, for example by email to info@regional-events.de.
If you voluntarily give your phone number, we only use it to reach you about your enquiry – by phone or, for the launch reminder, by WhatsApp if you wish. WhatsApp is a service of WhatsApp Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland; data may also be transferred to Meta Platforms, Inc. in the USA. We only send a WhatsApp message if you gave us your number for that purpose (Art. 6(1)(a) GDPR).
To protect against automated submissions each form contains a field invisible to humans. If it is filled in, we discard the submission without storing it.
3.5 Contact management in HubSpot
We store details submitted through the website forms in HubSpot, a customer and contact management system of HubSpot Ireland Limited, 1 Sir John Rogerson's Quay, Dublin 2, Ireland. Data is processed on servers within the European Union. Transfer happens only from our server; no HubSpot script is embedded on the website, and no cookies are set for it. We have a data processing agreement with HubSpot under Art. 28 GDPR.
3.6 Confirmation emails and reminders
If you sign up for an online meetup, we send you a confirmation with the meetup link and a calendar entry, plus reminders the day before and one hour before the start. If you request a call, you receive an acknowledgement with your details, and we receive an internal notification at info@regional-events.de. On the day of a meetup we also receive a participant list with name, organisation, role, email address, region and delivery status of the confirmation.
We send emails via Resend (Resend, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA); website emails are sent via Resend servers in the European Union. Resend tells us whether an email was delivered, bounced or marked as spam. We store this delivery status in HubSpot to follow up on undeliverable addresses. The legal basis is Art. 6(1)(b) GDPR. We have a data processing agreement with Resend under Art. 28 GDPR.
3.7 Online meetups via Google Meet
Our online meetups take place via Google Meet, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. When you take part, Google processes the necessary data, such as your display name, IP address, device information and – if you switch them on – video, audio and chat messages. You can keep camera and microphone off at any time. We do not record meetups. The legal basis is Art. 6(1)(b) GDPR. A transfer to the USA cannot be ruled out; Google LLC is certified under the EU-US Data Privacy Framework.
3.8 Contact by email and phone
If you contact us by email, by phone or by replying to one of our emails, we process your details to answer your request. Emails to info@regional-events.de are processed in Google Workspace, a service of Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, Ireland. We have a data processing agreement with Google under Art. 28 GDPR; a transfer to the USA cannot be ruled out, Google LLC is certified under the EU-US Data Privacy Framework. The legal basis is Art. 6(1)(b) GDPR where your request concerns a sign-up, a contract or its preparation, otherwise Art. 6(1)(f) GDPR (answering your request).
4. Regional.Events app and platform
4.1 Use in the browser, installation and app stores
You use Regional.Events in your browser or as an app from Apple's App Store or from Google Play. In the browser you can also put the app on your device using the "Add to Home Screen" or "Install" function. Your device then only stores the app files needed for display without an internet connection (see 4.9).
The app from the App Store and Google Play. The app shows the same platform as the browser, in its own app window, and this policy applies to it in the same way. Cookies and entries from 4.9 are then kept in the app's storage on your device instead of your browser's storage; if you delete the app, they are deleted with it. When you download or update it, Apple or Google process data such as your account name, email address, device identifier and time of download under their own responsibility. We have no influence on this; the store's privacy terms apply.
Permissions on your device. The app only asks for permissions a feature needs, and only when you first use that feature:
- Location, only while you are using the app: for your region, "Near you" and checking in at the place (see 4.6 and 4.7), never in the background.
- Camera: to scan QR codes and posters and to take photos (see 4.7a).
- Microphone: only when you record a video for your event yourself (see 4.7a).
- Photos: only to save, when you want to keep your Event Pass or a shared picture in your photos. The app does not read your photo library for this.
- Notifications: for push notifications (see 4.8).
You can refuse any permission; the app keeps working without that feature. You can withdraw a permission at any time in your device settings (iPhone: Settings › Regional.Events; Android: Settings › Apps › Regional.Events › Permissions). The legal basis for accessing these functions of your device is your consent (Art. 6(1)(a) GDPR in conjunction with Section 25(1) TDDDG).
4.2 Account and sign-in
You need an account for most features. You sign in with your email address or username and your password. After you register we send you a link that confirms your email address; a tap on that link signs you in on the browser you open it in. You can create a page and publish events only after confirming your e-mail address; for this we store whether and when you confirmed it. If you forget your password, we send you a link to set a new one. We process: your email address; your username and, if you set one, your password, which we never store in plain text, only as a salted hash that cannot be turned back into the password; an internal user ID; the language you use the app in (German or English) – we also write you emails and notifications in this language, on each of your devices; if you do not choose one, we take the language the app is shown to you in; you can change it at any time with the language switch, and it applies at once; details of your sign-in sessions (time of sign-in and of last activity) – confirmation links, password reset links and session keys are stored only as cryptographic hashes, never in plain text; your confirmation that you are at least 16 and – if you want to use features for 18+ – whether you are at least 18: you confirm this once, with a tick "I am at least 18", only when you first use a feature for 18+; we do not ask for a date of birth for this and store only this confirmation and when you gave it; if you gave your birthday earlier, the result from then still applies: there too we stored not the birthday itself but only the result "at least 18" or "under 18" – and, if you are not yet 18, the day you turn 18; that and when you accepted our Terms and which version. The legal basis is Art. 6(1)(b) GDPR and for proof of acceptance Art. 6(1)(f) GDPR (our interest in being able to prove the conclusion of the contract).
Several accounts on one device. You can be signed in with up to five accounts on one device at the same time ("Add account", then "Log in to an existing account") and switch between them. The accounts stay separate: points, profiles, pages and messages always belong to their own account and are never merged. So that the other accounts stay signed in, their session keys are kept in a cookie on your device (see 4.9); on our server we store them, like every session, only as a hash. "Log out" ends only the account you are in; "Log out of all accounts" ends all of them. The legal basis is Art. 6(1)(b) GDPR.
Signing in with Apple or Google. Instead of email and password you can also sign in with your Apple ID ("Continue with Apple") or your Google account ("Continue with Google"). The providers are Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland, and Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. The sign-in itself takes place at Apple or Google; we never learn your password there. We receive only what you share: an identifier of your account with the provider, your email address and whether it is verified and – if you share it – your name. With Apple you can choose "Hide My Email"; we then receive only a forwarding address created by Apple. Apple sends the name only on the first sign-in; we use it as your profile's display name, which you can change at any time. For Apple we also store an access key, encrypted, so that we can revoke the connection at Apple when you delete your account or disconnect Apple in the settings. If there is already an account with your email address, we connect Apple or Google only after you have tapped the link in our email. During sign-in we set two strictly necessary cookies:
__Secure-re_oidc_binding(at most 10 minutes) and__Secure-re_oidc_pending(at most 30 minutes). Under Settings › Sign-in you can see what your account is connected to and disconnect Apple or Google. If you delete your account, we delete the connection and revoke access at Apple. The legal basis is Art. 6(1)(b) GDPR. Apple and Google process the sign-in under their own responsibility; their privacy policies apply. A transfer to the USA cannot be ruled out.4.3 Profile
In your profile you can enter a display name, a profile picture, a short description, your interests and your home region and up to five more regions (visible only to you). With your place of residence you can also save its district. Everything except the display name is optional. You decide who can see each part of your profile. Whoever you follow – a person or a page – always sees you in their own follower list with your display name, profile picture and @name, even if your profile is private or you have limited your profile header, and can remove you there as a follower (as on Instagram). If they tap you there, they see only your profile header; the other parts of your profile stay protected under your settings. For a page this applies to the people who run it. You also appear in the follower and following lists others see, so that the number always matches the list: as an adult with your display name, profile picture and @name, even if your profile is private or you have limited your profile header; if you are under 18 or have not given your age, everyone your profile header does not include sees only “A member”, without a name, picture or link. Profiles that were “Invisible” until now were switched to “Private” with the November 2026 update; “Invisible” no longer exists. If you said you are under 18, you also appear in that list with your display name, profile picture and @name; if someone taps you there, we show only these and your counts (events, followers, following), but not your home region, not since when you have been a member and no Crew badge; the people who run a page do not see the counts either. The same applies as long as you have given no age. Everyone else still sees your profile only under the rules for under-18s. If someone removes you as a follower, we do not notify you; you can follow again. Visitors who are not signed in see no profile details. We store your profile picture in private storage (see 5) after removing embedded metadata such as location and camera data; it is delivered only to people allowed to see it under your settings and to those you follow (see above). If you replace or remove a picture, we delete the previous one. For every picture you upload (profile and page picture, cover, event picture, story), your browser and our server check, before the metadata is removed, whether the file itself states that it was made or edited with AI (the IPTC “DigitalSourceType” field or C2PA Content Credentials); no other service is used for this. If it does, or if you turn on “Add AI label”, we store with the picture that it was made with AI and where that information came from, and show the note “AI info” on event and story pictures. This serves the labelling under Art. 50 of the AI Act; the legal basis is Art. 6(1)(f) GDPR (our legitimate interest in recognisable AI content). The information is deleted with the picture. We also store your settings, such as your chosen region and display mode (light or dark). If you run pages, you can choose up to three of them to appear under your description with their picture, name and link; anyone allowed to see your profile sees them. Without your choice we show none. We store your choice until you change it or delete your account. If you change your @name, we keep the old one free for you for 14 days and store it on your profile for that time. Old @names of pages forward to the new name. You can run up to ten profiles under one login, including further private profiles. To others they are separate profiles. Each private profile has its own rewards programme. We store new reward-relevant activities and redemptions with the private profile you use for them and with your responsible account. Existing points and rewards stay in their original programme; they are not copied or transferred. Limits against duplicate rewards still apply to you as a person. Your data export includes the ownership of all your private programmes; deleting your account also deletes their personal entries. Legal basis: Art. 6(1)(b) GDPR.
When your profile is shared, by someone else or by you yourself as a link, for example via WhatsApp, "Copy link" or as a story, the preview (the picture messengers show with the link, or the story picture) shows your profile picture, your name and your @username. This applies only if you are an adult, your profile header is visible to all members and the switch “Others may share my profile with my picture” in your privacy settings is on. For a public profile it is on from the start, for a private one off; you can change it at any time. When it is off, the preview only shows “A profile on Regional.Events”, without picture or name. Anyone who has the link can see the preview, even without signing in. Messengers may keep a preview they have fetched; we have no influence on that. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is that members can recommend profiles to each other recognisably. You can object with the switch.
When you share your own personal invitation story yourself (the picture card with 'Kommst du mit?' and your QR code), that card shows your profile picture, your name and your @username — because you are sharing it yourself, regardless of whether your profile header is visible to others. This applies once you are an adult or as long as you have given no age. If you share as a minor or as a page, the card stays without a name and picture and shows only the initial of your name. The legal basis is Art. 6(1)(b) GDPR, because you share the story yourself to invite someone.
So that a business that signed up with a private profile by mistake finds the way to its own page, once a day we compare the display name and the short description of new and changed private profiles with a word list (for example “Gasthof”, “hotel”, “association”, “GmbH”). Only when the list cannot decide and the feature is switched on (it is off by default) does our service provider Anthropic (see 5) read just that name and short description, nothing else about you. If it fits, we store on your profile the mark “possibly a business” with the time and the kind of check (list or AI) and your answer to the hint. Together with the mark or a result of the AI we store a short check code of these two texts (not the texts themselves), only to tell whether they changed since the last check. You then see a calm hint on your own profile to create a page; your profile is not changed and nothing is moved without your tap. Besides you, only our team sees the mark, for example to approach you personally later; we send nothing automatically because of it. With “No, I’m private” the hint ends for good. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is that businesses find their page and guests see it under Locations. You can object at any time (Art. 21 GDPR), most simply with “No, I’m private” or by e-mail to info@regional-events.de. We delete the mark with your account; it is part of your data export.
Members per town (sums only). So that we know how many members are in which towns, we assign every member to one town for our internal statistics: first to your place of residence (“My town”) that you entered or confirmed yourself. If you have not entered one, we take the town where you checked in most often in the last 90 days (at events and at places, see 4.6). If you have chosen a home region, this applies only if the town lies in it; if you have chosen none, you count in that town’s region. For this we store, once a day, only this one town and its region: no position, no list of your check-ins and no count. Without such check-ins you count only in your region. In our administration the team only sees sums per town, Verbandsgemeinde, district and region; numbers below five are not shown there, and never who lives where. The app itself does not use this town. As soon as you set “My town”, the derived town no longer counts. It is deleted with the next daily calculation (as a rule the following day), likewise when you have not checked in anywhere for 90 days, and with your account; it is included in your data export. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is planning our offer by town. You can object to this assignment at any time (see 9); a message to info@regional-events.de is enough. We then delete the derived town, derive no new one and store for this only that and when you objected, until you delete your account.
4.3a Emergency contact
You can voluntarily add a person to your account for emergencies: name, phone number and, if you wish, how you are related (family, partner, friend or other). Only you see these details. Regional.Events is not an emergency service: we call no one, notify no one and pass the details on to no one. The legal basis is Art. 6(1)(b) GDPR; for the data of the person entered Art. 6(1)(f) GDPR (your interest in quickly reaching someone close to you in an emergency). Please tell the person that you added them and show them this policy. If you remove the entry, we delete it immediately; at the latest it is deleted with your account.
Information for the person entered (Art. 14 GDPR): the controller is named in section 1. A user has named you as their emergency contact. For this we store your name, phone number and, where given, the relationship. These details are shown only to the person who entered you; we do not use them ourselves and pass them on to no one. They are kept until that person removes the entry or deletes their account. You can object to this at any time; a message to info@regional-events.de is enough. Your other rights are in section 9.
4.4 Content you publish or share
When you create content in the app, we process it to store and display it as you wish:
- Events: title, description, picture, date, place, ticket link and other details you enter. Published events are publicly visible. This also includes the line-up (names of performers you enter as text, and invitations to artists or providers to link their own page to the event – once accepted, their page appears with the event), documents you attach to an event, who started or ended an event's live mode and when, and your answers to host calendar notices (for example the day after the event). If you enter other people's names in the line-up, make sure they agree. If you add an event as a private person, i.e. without a page for a club, business or organiser, we show only the street and the town publicly, without the house number, also in previews, calendar files and the details for search engines and AI assistants. Only signed-in members who tapped “I’m going” see the full address, in their Event Pass, and you yourself. For events of pages and for venues the full address is public.
- An event's photo link: the address of an album on another service (for example Dropbox, Google Photos or iCloud) that the organiser enters and where guests can upload or look at their photos and videos. We only store and show this link and load nothing from that service before. Only when you tap “Upload photos & videos” or “See the photos” does the other service open; whatever you upload there is processed by that service under its own privacy policy.
- Event passes (for example AAA, backstage, press): Organisers can give Team passes for their event (3 per event without Premium, unlimited with Premium), for example AAA, backstage, press or a vehicle pass. If you get a pass as a member, it shows the full name the organiser enters and you confirm or change on first opening, your @name and your profile picture or another photo you choose for this pass. That name and photo belong to this pass only; we do not change your profile. If you get it as a guest without an account, we store the name and photo the organiser entered; we keep the photo in private storage after removing embedded metadata. If the organiser gives your e-mail address, we send you exactly one e-mail with the link to your pass (sent via Resend, see 5); we use the address for nothing else and delete it with the pass. Otherwise the organiser sends you the link; we store no phone number for this. Of the link we keep only an encrypted check value. For a vehicle pass we store the licence plate and, if given, the driver's name; security sees the plate when scanning. The QR code on the pass contains only a random identifier that changes every 30 seconds. Whoever scans it sees the photo, name, pass type, event, validity and the areas the pass may enter. For every scan we store the result and the time, in security mode also "in" or "out" and which team member scanned; we do not store the device or location. Only the organiser's team and you can see the pass, photo and scans. We delete everything 30 days after the pass's last valid day, and at once when you delete your account. Legal basis: Art. 6(1)(b) GDPR towards the organiser and you; for guests without an account Art. 6(1)(f) GDPR (the organiser's legitimate interest in safe access control).
- Meet-ups: arrangements with others. Everyone can see a public meet-up. A private meet-up appears in no list; only people with its invite link can see it and its address. If a public meet-up takes place at a private address, only participants the host has confirmed see it.
- Guest photos and videos: pictures you upload to an event. We remove embedded metadata such as location and store the files in private storage. You may voluntarily allow the event's organiser to reuse your picture; we store this permission together with the version of the notice you saw. If you withdraw your contribution, the permission ends; we cannot recall copies the organiser has already downloaded.
- Song requests (RE:MIX): your music requests during an event. Only title and artist are stored as text, no audio files.
- Lost and found: reports about lost or found items.
- Deleted events: If you delete an event, other people can no longer see it. We keep it for you for 30 days so that you can restore it (booked reach, materials and on-site offers do not come back with it). If you tap “Delete for good” or the period runs out, we anonymise the personal details: title, description, place, address, contact, ticket page, hashtags and picture are deleted. Only the technical minimum stays (ID, timestamps, payment references for bookkeeping, your guests’ points and check-ins, the region and the category). An event we have hidden because of a report or a review we keep unchanged until the review is finished; during that time you can neither restore nor delete it for good. The legal basis is Art. 6(1)(b) GDPR (your wish to bring the event back) and (f) (preserving evidence for reports).
- Enquiries to artists and service providers: your enquiry with the details you provide.
- Support requests: your message to our team and our replies. To answer faster, our team may ask an AI to suggest a reply draft. For this we send our provider Anthropic (see 5) only the text of the latest messages in this thread (at most twelve); we mask email addresses, phone numbers and account numbers (IBAN) in it first, and we do not send the name from your account or the account itself. A person on our team always reads, edits and sends the draft; the AI sends nothing itself. We store the draft with the thread for as long as we keep the request. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is answering requests quickly and well. You may object; we then answer your request without an AI draft.
Please do not publish personal data of others without their consent. If photos show other people, our Community Guidelines apply. Legal basis: Art. 6(1)(b) GDPR.
People shown in a photo or named in content who are not users themselves are hereby informed under Art. 14 GDPR: we store and display such content because users post it (Art. 6(1)(f) GDPR; legitimate interest in operating the platform and exchanging information about events). You can object at any time and have the content removed via "Report" or by email to info@regional-events.de.
4.5 Direct messages and group chats
You can send direct messages to other users and take part in group chats. We store messages, participants and time sent in order to provide the conversation to those involved. In a chat the other person sees “Seen” once you have opened their message, and “is typing …” while you write. For this we store when you last read and last typed in the chat; typing is shown for a few seconds only. We do not analyse message content for advertising or analytics. If a message is reported to us, we look at it as part of moderation (see 4.13). If you recall a message, nobody sees it anymore. We keep its text for at most 30 days, only so that we can review reported content. After that, we delete it. Legal basis: Art. 6(1)(b) GDPR.
4.6 Saved events, RSVPs, check-in and contacts
We store which events you save and which you say you are attending, so you can find them again and – depending on your visibility settings – your contacts can see who is going. We also store which places and pages you save (for example venues, clubs, bars, sights, towns or organisers’ pages), so you can find them again in your plan under “Saved” › “Places”. Only you see this; the page is not told who saved it. At check-in you confirm your attendance with the event code the organiser provides on site, with the scan at the door or, if you allowed it in your browser or device, with your location. The app then sends your device’s position, with its accuracy and time, to our server once for that one check-in. We only compare it with the event’s location to decide whether the check-in counts for points and rewards. We do not store the position itself; we only store the result, the time and the event’s location. The same applies to a check-in at a place without an event, such as a sight, a museum, a leisure park, a market or a restaurant or bar: we only store at which place you checked in and when, that place’s public location and whether the check-in counts. Others only see how often people checked in at a place in total, never who. So that points only go to people who really stay, we first only reserve a check-in’s points. If you open the app again at least 20 minutes later while the check-in is open, the app reads your device’s position once – only if you have already allowed location, without asking again – and sends it with its accuracy and time to our server. Again we compare it only with the event’s place and do not store it; we only store whether the points were credited. Without this second look the check-in stays, the points lapse. If you are offline, the check-in and its position stay on your device only, for up to 24 hours, until it is sent. In the app you can also check in when no page loads at all: the app's offline page keeps your check-in with its time and location (coordinates and accuracy) in the app's storage on your device and sends it as soon as you have signal again. It stays there for at most 24 hours and is deleted once it has been sent. The legal basis for accessing your location is your consent (Art. 6(1)(a) GDPR in conjunction with Section 25(1) TDDDG, see 4.7). If you reach an event through an organiser’s code or link, for example the QR code on a flyer, an LED wall or a table stand, or a link shared in a story or on WhatsApp, we store with your “I’m going” or your check-in which of these ways you came through. Only the first way counts. The organiser only sees numbers, for example “87 said they were going through your flyer code”, never your name. We delete this detail with your “I’m going”, at the latest with your account. We also store whom you follow and whom you block, and the time of your last activity ("last seen"). We also use this time so that your points only expire if you have not been active for 24 months. If you follow a town, a district or a part of a town (Ortsteil), others can see it as with any public profile you follow, unless your profile is private or you have limited “Who can see whom you follow?”; places you followed before 5 November 2026 remain visible only to you; they are not counted in the place’s public number of followers either. Legal basis: Art. 6(1)(b) GDPR.
When you reserve a reward, we also store a random command identifier with the reservation. Your retry after a lost response then identifies the same reservation, without booking another reward or deducting more points. The identifier is part of the redemption receipt and follows its existing retention and erasure rules. On your device the pending attempt is kept only as described in 4.9 a); no new reservation is sent without another tap from you.
In your account we also store whether “Show points & game” is switched on and when a new part of Rewards (for example badges or missions) was first shown to you, so you do not see everything at once; this applies on all your devices, is part of your data export and is deleted with your account. The legal basis is Art. 6(1)(b) GDPR.
You can pin up to three of your badges to the top of your profile. For this we store which badges you chose; everyone who may see your badges can see them. Badges and scenes that can reveal something about your sexual orientation or your faith (the scenes “Queer & Diversity” and “Church & Faith”) are shown to others only if you switch on “Show queer and faith badges to others” in “Edit profile”; without your decision it is off. You always see them yourself. We store both settings in your account until you change them or delete your account; they are part of your data export. The legal basis for pinning is Art. 6(1)(b) GDPR; for showing the queer and faith badges to others it is your explicit consent (Art. 9(2)(a) GDPR), which you can withdraw at any time by switching it off.
Under “Events”, your profile shows the events you checked in to and your upcoming RSVPs (“I’m going”). Others only see your RSVPs as your visibility settings allow: in Settings under “Who can see which events you’re going to?” and for each RSVP on its own; if you switch them off, only you see them. If you’re under 18, only people you follow who follow you back see them. If you follow each other, event cards may show your friends that you are going (for example “Lena and 2 friends are going”), with your first name and your profile picture. This only happens when your setting “Who can see which events you’re going to?” and that single “I’m going” allow it. People who do not follow you back never see this line. We store nothing extra for it; the line is built when the card is shown, from your “I’m going” and your follows. The “Events” number on your profile counts only your check-ins. So that an event you attended stays on your profile even if the event is removed later, we store the event’s title, place and a reference to its picture with your check-in. Whoever may see your profile sees these events under the same visibility settings as your RSVPs. With “Remove from profile” you take an event off your profile; your check-in and your points stay. These details belong to your check-in, are part of your data access report and are deleted with your account. Legal basis: Art. 6(1)(b) GDPR. We do not delete past events once they have ended: they stay visible as the history “What was on here” on the page of the organiser, the venue, the artist or provider and the town. There we only show the published details of the event itself (title, date, place, picture), never who said they were going, took part or checked in; only the organiser sees how many there were.
When someone scans the changing QR code on an event's live screen or the QR code on a Regional.Events check-in sign, we count for the organiser how often this happened and how often someone went on from there to the App Store or Google Play. We do not store who scanned. When someone checks in through such a sign, we only note the channel "check-in sign" with the check-in so the organiser sees how many guests came that way. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is showing organisers what their displays bring.
We count how often our pages are viewed and how a visit reached us (for example through a search engine, a social network or an AI assistant). For this your browser only reports a number of page views and, once per visit, one word from a fixed list such as “Google search” or “ChatGPT”; the address of the page you came from is not transmitted. From this we store only totals per day, route and region: no IP address, no identifier, no cookie and nothing on your device. To limit abuse, we briefly count in working memory how many reports come from one IP address (for the running minute each time); it is not stored. When a preview service (such as WhatsApp's, Facebook's or LinkedIn's) or an AI service fetches one of our pages automatically, we count this per service and day; these are fetches by programs, not people. We also retrieve, from services where we hold an account ourselves (for example Google Search Console, Bing Webmaster Tools, Instagram, Facebook, TikTok, YouTube and our advertising accounts), daily totals about our own pages, posts, videos and ads; we receive no information about individual people in doing so. From all these totals we produce evaluations, estimates and forecasts of our reach. For a short weekly report we send only such totals to our AI service provider Anthropic. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is knowing the reach of Regional.Events and being able to show it to organisers, advertising partners and the press.
When someone taps “Tickets” on an event, the link first goes through our server and then on to the organiser's ticket shop. We count how often this happened – per event, ticket seller, place in the app (such as the event page or the Event Pass), region and day – and add to the link that the visit came from Regional.Events (for example “utm_source=regional-events”). We do not store who tapped: no IP address, no identifier, no cookie. So that a double tap does not count twice, we form a check value from the IP address and the browser identifier only in working memory, with a random key that changes daily, and discard it after 30 minutes. Organisers see the figure for their event, our team the totals per ticket seller. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is showing organisers and ticket sellers how many visitors come through Regional.Events. For ticket links from partner programmes, the redirect also goes through the partner network Awin (AWIN AG, awin1.com). We pass a reference made up of source and event (e.g. ticket_<Event-ID>), without personal data from us. Awin and the ticket provider may use cookies or tracking on their own sites to attribute commissions; their privacy notices apply. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is financing through commissions. When you tap the link, Awin and the ticket provider, as with any link, see your IP address and the device details your browser sends. From us they only receive the reference made up of source and event.Deals, rewards and redemption statements. When you redeem a reward, a deal or your stamp card at a business, we store the redemption with its number, date, time, what was redeemed and the value the business stated itself. The business only sees numbers and a statement list without your name. So the business can tell how many different guests came, we give you an anonymous guest number per business. We delete the link between you and that number when you delete your account. The statement list itself holds nothing about you as a person and stays with the business for its bookkeeping. The legal basis is Art. 6(1)(b) GDPR (redeeming at your request) and, for the statement list, Art. 6(1)(f) GDPR (the business's legitimate interest in a list for its bookkeeping).
Redemption statement by email. For pages with redemptions in the previous month, the monthly PDF service is on by default. On the second day of the month we try to send the statement through Resend to the current page owner’s sign-in email address. For this we process that address, the page name, the month and the PDF statement without guest names. We store the setting and whether sending has already been started for that page and month, to prevent duplicate emails. You can switch the service off in the redemption statement area and also download the statement there yourself.
Sticker set from the shop. If you redeem points for a sticker set, we store the name and postal address you enter for it with the order. We use them only to send you the set by post; for this they are on the item the postal service delivers. Once the set has been sent, we delete name and address from the order; if you delete your account before that, we delete them with it. The order itself (what and when) stays stored and is deleted with your account. The legal basis is Art. 6(1)(b) GDPR.
When you use "Nearby" in the deals list, the distance is worked out on your device from the location you already shared, rounded to about 1 km. Your location is not sent to us for this.
4.6a Referral links
Every account has a personal referral link with a code and QR code. If someone registers via your link, we store which code the account came from. An account can be assigned to only one referral; the first valid one counts. You then only see how many people joined via your link and how many events they published in total – no names. There is no money or commission for referrals. For Crew links see 4.12. Legal basis: Art. 6(1)(b) GDPR. We delete the assignment with the account. When you share a link in the app, for example via WhatsApp, "Copy link" or as a story, we count how often you shared which link through which channel and how often a link with your code was opened. We do not store who opened the link. You see yourself how often your links were opened, and organisers see how often shared links to their event were opened. We also count how many sign-ups and RSVPs (“I’m going”) came from an opened link, only as a number per link and day, never who. For this, profile links carry a short identifier from your code. The Regional.Events team sees the numbers to understand how Regional.Events is recommended, for example by the Crew. They are part of your data export and are deleted with your account. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is understanding how people find Regional.Events.
Invitations through the App Store or Google Play. If you open a friend's referral link on an Android phone and get the app from Google Play, we pass on to Google Play only the invitation code and a short word for where the link came from (for example “share”). Google hands exactly these details to the installed app (Play Install Referrer). On the first start without being signed in, the app reads them once and sends them to our server; from them we keep only the invitation code in the cookie
__Host-re_invite(see 4.9 a)), just as if you had opened the link in the browser. If you were already signed in when the app read them, because you registered right after the start, we instead assign the invitation code directly to your new account, under the same rules as when signing up through the link; this works only in the first days after registration and only while your account is not yet assigned to an invitation. So that this happens only once, the app remembers on your device that it has handed the details over. On the iPhone the App Store passes on no such details. There, the page for getting the app shows you the invitation code; only when you tap “Copy code and get the app” do we put exactly this code on your clipboard. In the app you paste it at “Who invited you?”; the app reads the clipboard only when you tap “Paste” there. Reading the Play Install Referrer on your device is strictly necessary for us to provide the service you asked for, namely that your friend's invitation survives the trip to the store (section 25(2) no. 2 TDDDG). For this hand-over we create no device fingerprint and store no device identifier; the random identifier that protects invitations against abuse (see below) is separate and is not formed from the Play Install Referrer. The same rules as for the link apply: the first valid invitation counts, and points come only with the first check-in on site. Legal basis for the processing on our server: Art. 6(1)(b) GDPR.The preview of your personal referral link (the picture and headline WhatsApp and other messengers show when you share the link) shows your @username, your profile picture and the picture of your home region, for example “@lena invites you”. This applies only if you are an adult, your profile is public (not private) and your profile header is visible to all members; otherwise the preview names nobody. Anyone who has the link or knows your code can see it; your code is also part of the other links you share from the app, for example to an event. Messengers may keep a preview they have fetched; we have no influence on that. The legal basis is Art. 6(1)(b) GDPR, because you share the link yourself to invite someone.
An invited friend only counts once they check in on site at their first event. For this we store on the invitation the date of their first on-site check-in. We also continue to read the times they signed in to the app and keep the date on which they opened the app on a second day, as described in the paragraph on traceability. Only for friends who confirmed their account by 12 November 2026 does this second day still decide, until the end of their 14-day window, whether they count; for everyone else only the first check-in counts. If an invited friend deletes their account, we keep on your invitation only these dates and the date of the deletion, with no link to the deleted person, so your level does not drop; invite points that fall away within 30 days of counting are taken back as described. In the “Top inviters” ranking, your name and number of friends only appear if you agreed to the ranking and are 18.
Whoever invited the most friends in their region in a calendar month wins a guest-list place at a partner. For this we store with your account the month, the region, the number of counted friends, when we awarded the prize and whether you used it for a guest list. For the partner it is an ordinary guest-list reservation; they get no further details. These details are part of your data access report and are deleted with your account. Legal basis: Art. 6(1)(b) GDPR.
Preventing abuse of invitations. So that invite points only go to real new members, the app creates a random identifier on your device and sends it when you sign in. We only store an encrypted check value of it, together with your account and the date. We use it only to recognise whether a new account was created on the same device as the inviting account, or shortly after another account on that device. In that case there are no points for that invitation. The legal basis is our legitimate interest in protecting the points programme from abuse (Art. 6(1)(f) GDPR); storing the identifier on your device is strictly necessary for this (Section 25(2) no. 2 TDDDG). The check value is deleted when you delete your account. You can object; then no invite points are given for invitations from your device.
Record of the invitation. So that invitation points can be traced and are credited correctly, we record for each invitation which code it came through, by which route (for example a link, a typed name or added later), how the new account was created (for example with a password, a sign-in link, Apple or Google), on which kind of page the link was first opened (for example an event or a page), through which channel and on which day, and the times of the confirmation, of the second day in the app and of the first check-in. We do not change these entries afterwards. Our team (administration and accounting) can view them to check whether points were credited correctly; in doing so it sees which account came through whose invitation. Other members do not see this. If you delete your account, we replace your identifier in these entries with a random identifier that has no connection to you, and your personal code is not issued to anyone again. The legal basis is Art. 6(1)(b) GDPR and our legitimate interest in being able to verify how points were credited (Art. 6(1)(f) GDPR).
Points for pages. Pages (for example of artists, organisers, venues or clubs) can collect points too. These points belong to the page, not to a person, and can only be used for visibility for the page's events. A page gets points in three cases: when you signed up to Regional.Events through its link and then check in on site at an event for the first time, when you check in on site at one of this page's events, and when you follow it. If you sign up through a page's link, we store with your account which page you came through; only the first one counts. For every credit we store the page, your user ID, the occasion (invitation, guest or follower), for a guest the event, the points, the time and whether the points are credited, still waiting or held back. A check-in only counts for this if your email address is confirmed and the location check at this event was passed. Following only counts if your account is at least 7 days old, your email address is confirmed and you have checked in at an event before with the location check passed. Per day and per week we only count a limited number for each page; anything above that waits and counts later. Whoever looks after the page earns it no points. To detect abuse, in all three cases we use the check value described above to see whether your account was created on the same device as the account of a person who looks after the page; in that case we hold the points back until our team has checked them. The page only sees totals: how many points it got for invitations, guests and followers and how many are still waiting or held back. It does not learn who is behind them. Our team (administration and accounting) can view the entries to check the crediting. Nothing is deducted from you, and you get no message about it. Entries that are still waiting, held back or cancelled again are kept just like credited ones. If you delete your account, the entries stay so that the page's balance remains traceable, but only with an ID that no longer belongs to any account. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest and that of the page is to reward pages for real new guests, to prevent abuse and to be able to verify the crediting.
Promo codes. If you redeem a promo code on the website or our team gives you something directly (for example points, free days for a Boost, Pro or Premium for a page), we store which code it was, what your account or page received, who redeemed or gave it, when, and until when it applies. This makes the benefit work, makes sure a code is redeemed only as often as intended, and helps us detect abuse. So that nobody can guess codes, we briefly count your attempts. Codes contain no personal data. You get no email for this. We keep these details for as long as your account exists. Legal basis: Art. 6(1)(b) GDPR; for abuse prevention, Art. 6(1)(f) GDPR.
If you are allowed to use “Get more guests” for an event, we count how often you visibly open the tool and how often you explicitly start sharing or saving after a file has completely loaded. We store only the account identifier or the identifier of the authorised page, the type of action, the day and the count. We do not store an event or file identifier or information about the people you want to reach. A preview or a generated file does not count as sharing or saving; the count also does not prove that a file was saved, posted or printed. The Regional.Events team sees the totals and the share of pages with a currently published event for which a visible opening was recorded in the selected period, to understand use of the tool. Account-related counters are included in your data export and deleted with your account. Page-related counters are included in the current page owners’ data exports. They remain with the page when it is handed over and are deleted when the page is permanently deleted (see 4.16). We store nothing on your device for this. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is understanding which invitation tools are used.
4.6b My tickets
Under "My tickets" you can keep tickets you bought elsewhere – as a PDF, photo, screenshot or Apple Wallet pass (.pkpass), up to 10 MB per file. We store the file in our private storage (see 5.) and read, on our server, the code on it (QR code or barcode) and the file's words and date to suggest the matching event. We store the file, the code and the event or the name and date you enter; we do not store the file's other words. Only you can see your tickets. We pass them on to no one, not to organisers either, and do not use them to check entry. If you assign a ticket to an event in the app, this counts as "I'm going" (see 4.6); the ticket itself stays private. So that your Event Pass works without internet, the app keeps your Event Passes for today and the next days, with your tickets' codes, on your device (see 4.9); this copy is deleted when you sign out. If no code can be read on a ticket, the app also keeps its original file (picture or PDF) on your device only, so you can show it at the entrance without internet; it is deleted when you sign out, when you switch accounts, when you delete the ticket and at the latest one day after the event (after 14 days if no event is assigned). An uploaded file that did not become a ticket (for example because reading it stopped) is deleted after 24 hours at the latest. You can delete any ticket at any time; if you delete your account, we delete all tickets and their files. Your tickets are part of your data export. Legal basis: Art. 6(1)(b) GDPR.
Event Pass: In the Event Pass we show what the organiser provided for guests of an event (programme, offers, drinks and food menu, site map, “good to know”, a number for help on site and sponsors), and your own points from the check-in. The organiser publishes these details; they contain no data about guests. For “Head home” we use your saved town (“My town”) only to build a link to Google Maps, Apple Maps, bahn.de or Uber; you only leave the app when you tap it, and we store no position. When you tap “Open in Uber”, Uber opens on the way there with the venue and the event's name as the destination, and on the way home with the venue or your location as the pick-up and the name of your home town as the destination – never with a street. Your location is then determined by Uber itself in its app; we do not pass it to Uber. If you share the ride home with your crew, the link carries at most the venue; if we do not know its exact point, it carries no place. The small map for the Uber ride is loaded from our own server and only for the venue; the app works out the approximate distance (“X km as the crow flies”) on your device only, and only if you have already allowed location. Organisers see only numbers about their sponsors (such as how many guests had a pass or checked in), never names. The legal basis is Art. 6(1)(b) GDPR.
Saving to Apple Wallet or Google Wallet. If we offer “Add to Apple Wallet” or “Save to Google Wallet” with your Event Pass and you tap it, we create a pass with details your Event Pass also shows: the event, date and time, the event's place, the name on your Event Pass and a QR code with the link to your Event Pass. For Apple Wallet your device downloads the pass as a file from our server; Apple receives nothing from us. For Google Wallet your device opens a link signed by us at Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) that contains these details; Google then creates the pass in your Google account and stores it there under its own responsibility until you delete it. If the event changes later, a pass already saved does not change by itself. The legal basis is Art. 6(1)(b) GDPR.
Sponsor vouchers. If you redeem a voucher in the Event Pass, we store which voucher you redeemed and when, so it counts only once per person. The organiser and the sponsor only see how many vouchers were redeemed, never by whom. For vouchers with alcohol we check your own age statement (18 or older); without it you do not see such vouchers. Your redemptions are part of your data export and are deleted with your account.
Meeting point on the site map. If you set a meeting point, we store the spot on the site map (no location tracking, no GPS) and your short note. Only people you send the link to can see it; we store who opened it, so you see who is coming. The meeting point disappears by itself after the event. It is part of your data export and is deleted with your account. The legal basis for both is Art. 6(1)(b) GDPR.
4.6c Planning room
As an organiser you can open a planning room for an event and invite people by link. In the room we store who is in it (lead or member, plus a label you choose yourself, e.g. "Sound"), what is planned (to-dos, shifts, who brings what, who took what on), "I'm here" on the event day and the files someone uploads (PDF, JPG or PNG up to 10 MB, in our private storage, see 5.). Only the people in the room see any of this. The room's chat is a group chat (see 4.5). If you leave the room, we remove your place and what you took on; what you created or uploaded stays for the team without your name. The same applies when you delete your account. Legal basis: Art. 6(1)(b) GDPR.
In a planning room you may leave a phone number if you want to. It applies to that room only and only the people in it see it, so they can call you, message you on WhatsApp or save you as a contact. If someone asks for your number, you decide: "Share" or "No". Without your yes we never pass your number on. If you share a contact card in a chat, the people in that chat see it. We delete a room's numbers 30 days after the event, with the room, or as soon as you remove yours; if you delete your account we also delete the contact cards about you. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time by removing the number.
Contact card in chats. In any chat you can share your own contact card with ➕: your name, your @name and your phone number, but only if you type it in for that. Only the people in that chat see the card. If you take the message back, nobody sees the number any more and we delete it within 30 days at the latest; if you delete your account, we delete it as soon as your account is permanently deleted. The legal basis is your consent (Art. 6(1)(a) GDPR).
4.7 Location
If the place search does not find a word you typed, we add that word up per day so we can fill in missing places. We store only the word and the count, nothing linking it to you or your session, and delete the count after 90 days. We count single words that a chooser in the app (such as a category, a scene or a music genre) does not know in the same way, so we can add what is missing: each word on its own, with no link to the other words, to you or to your session, and also for 90 days only.
With "Find my region" we determine the nearest region on your device only. Your location is not sent to us or stored. If you use the radius search, the app sends the coordinates to our server for that single search only; we do not store them. When the start page shows "Near you", it is the same radius search: the app sends your location, rounded to about one kilometre, to our server for that one request only; we do not store it. The same applies when the app orders results by distance: if you search or browse events, or the start page shows you sights nearby, while the app knows your location, it sends your location, rounded to about one kilometre, with that request to our server so that nearer results come first; we do not store it. If you search for a town, the town search sends only a coarse location grid (about 25 km), solely for sorting so that nearby towns come first; we do not store it. The same applies to a check-in at the place, for that one check-in (see 4.6). The app only accesses your location if you allowed it in your browser or device; you can withdraw that permission in the settings at any time. Legal basis: Art. 6(1)(a) GDPR in conjunction with Section 25(1) TDDDG.
Paid placements (Boost, campaign, ad slot) can be booked for single towns instead of the whole region. So that you see the ones booked for your town, the app, once it has recognised your town, sends only your municipality's code (the official municipality key) to our server with the requests for the start page, search and event lists and with the measurement of whether a paid placement was shown or tapped, never your coordinates. The server uses it for that one request only. We do not store the code with you, set no cookie for it, put it in no address and do not log it per person. All we count is how often a paid placement was shown or tapped per municipality and day, as a total without any link to you; the advertiser sees figures below five only as "under 5". This count only runs if you have agreed to reach measurement. If the app does not know your town, it sends nothing; you then only see placements booked for the whole region. The legal basis is the same as for location above.
If you have allowed location access, the app checks which region you are in each time you open it, each time you return to it, and every five minutes while it is open. If it notices that you are on the move, it checks once a minute for the next five minutes. When the app starts, and only if you have already allowed location access, it asks right away for your approximate location so the right region is there as soon as it opens. For this the location stays in your device's session storage for a few seconds at most and is deleted as soon as the region is found. Only the region's name is kept. So that the right region is there from the start, it may first use a location your device determined up to 15 minutes earlier. This happens only on your device, and we keep only the region's name there for at most 24 hours, never your location. The app never asks for your location in the background. If a location reading is too imprecise to name your town reliably, the app shows only the region or "near" a town and, while it is open, asks for a more precise reading for at most eight seconds. That reading is not sent to us for this either.
To recognise your region and town on your device, the app loads the boundary data of your district and of nearby districts as files from our server. These are not details about you, and your coordinates are in none of these requests. The files loaded do, however, show roughly which area you are in. Like any page request, these requests can appear in the server logs (see 3.1); we do not link them to your account.
Travel time to an event: if you entered a home town or already allowed the app your location, we work out the distance to the venue on your device. For bus and train times we send the location to our server once. It only finds your municipality and plans from its centre. The location is not stored, not logged and not shared. We never ask for your location for this.
We convert venue addresses into map coordinates on our server using Nominatim based on OpenStreetMap (OpenStreetMap Foundation, St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS, United Kingdom). Only the venue's address and name are sent, also while you type the address when entering an event, without any details about you and without your device's location. Legal basis: Art. 6(1)(b) and (f) GDPR; our legitimate interest is showing venues correctly on the map and in radius search. We check venue details from public event calendars in the same way.
Links to Google Maps open Google's site only after you click them; no data goes to Google before that.
Links to Deutsche Bahn, Uber, Google Maps and the taxi search open those providers' pages and apps. The link only carries the venue, the time and, if given, the name of your home town. If you tap “Train” in “Getting there” and location is on, we also pass your approximate location (rounded to about one kilometre) to Deutsche Bahn as the starting point. This only happens on your tap; we do not store the location for it. From then on the provider's privacy policy applies. The links currently carry no partner or tracking code. We ask the Deutscher Wetterdienst (via Bright Sky) for weather only for the venue or the region.
4.7a Camera, microphone and photos
The app only uses your device's camera when you open a feature for it yourself:
- Scanning QR codes, for example when checking in with an event's or sign's code, checking a Crew ID or scanning Event Passes at the entrance. Your device reads the code from the camera picture; only the content of the code reaches us, never a picture. The camera picture is not stored.
- Scanning a poster. Here the app takes a photo; what happens to that photo is described in 4.21.
- Taking photos and videos, for example for your profile picture, an event or guest photos. Only what you then explicitly upload is stored (see 4.3 and 4.4). The app only uses the microphone when you record a video yourself.
In the browser your browser, in the store app your device asks for permission before the camera or microphone is used for the first time. Without that permission you can pick an existing picture instead or type the code in by hand where the feature offers this. You can withdraw the permission at any time in your browser or device settings. Legal basis: Art. 6(1)(a) GDPR in conjunction with Section 25(1) TDDDG.
4.8 Notifications
We notify you in the app, for example about new messages or news about events and meet-ups that concern you. By email we only notify you about topics for which you switch email on in the settings; by default email is off for all topics. You can switch each type of notification on and off in the settings. We always send by email the link that confirms your email address, the link that resets your password and the link with which you confirm that it is you before sensitive steps (viewing your data, deactivating or deleting your account), because only then are these steps secure. If you have a subscription paid through our website, we also always remind you by email and in the app before we charge you: three days before every charge, and for an annual subscription also 30 days before. This reminder is part of your contract and therefore cannot be switched off; we only send you advertising by email if you have switched it on. We send emails via Resend (see section 5).
If you follow an artist's page, you get a notice in the app when it shows a new song (“New song from …”); you can turn this off in the settings under notifications.
Invitation from a page you follow. If you follow a page, it can send you an invitation to one of its events at most once a week, labelled “Sponsored”. For this we only use the fact that you follow the page; the page does not see who received the invitation. You can switch these invitations off in your notification settings. The legal basis is Art. 6(1)(f) GDPR; our and the page’s legitimate interest is to point its followers to its own events. You can object with the switch. The invitation arrives as a notice in the app (“… invites you: …”); Regional.Events sets the text, it only names the page and the title of the event. Once the event has started, no invitation comes any more. You only get it as a push notification if you have switched push on yourself for “Follows and invitations”, and never between 10 pm and 8 am; we never send it by email. You can also stop following the page. For the push notification the legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw in the settings at any time.
Push notifications. In the app from the App Store and Google Play we can send notifications to your device, for example for a new message, an answer to your enquiry, a change to or cancellation of an event you said "I'm in" to, a reminder the day before, or points about to expire. We only send push notifications if you have allowed them: the app first asks when you say "I'm in" or follow someone for the first time, and then your device itself asks for your permission. If you allow them, we store with your account an identifier for your device (push token), the platform (iOS or Android) and when the app last checked in. For delivery we pass the push token and the title and short text of the notification to the Apple Push Notification Service of Apple Inc.; for Android devices to Firebase Cloud Messaging of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. A transfer to the USA cannot be ruled out; Apple Inc. and Google LLC are certified under the EU-US Data Privacy Framework. Between 10 pm and 7 am we send no notices that can wait, and at most three such notices a day, then a single summary notice. You choose which topics reach you in the settings under notifications. You can switch push notifications off completely at any time in your device settings (iPhone: Settings › Notifications › Regional.Events; Android: Settings › Apps › Regional.Events › Notifications). If you sign out in the app, we delete that device's push token; if Apple or Google report that a token is no longer valid, we delete it too, at the latest with your account. Legal basis: your consent (Art. 6(1)(a) GDPR in conjunction with Section 25(1) TDDDG).
Legal basis: Art. 6(1)(b) GDPR, for legally required notices Art. 6(1)(c) GDPR.
4.9 Cookies and storage on your device
The app stores cookies and entries in your browser's storage on your device. Cookies and storage always belong only to the address at which you are using Regional.Events (for example regional-events.de) and do not apply to other addresses. If you have used Regional.Events at a different address so far, you therefore sign in once again at regional-events.de. We distinguish four groups.
a) Strictly necessary. We set these without consent because they are strictly necessary for a feature you expressly use (Section 25(2) no. 2 TDDDG):
Name Type Purpose Lifetime __Host-re_sessioncookie keeps you signed in until sign-out; ends after 14 days without activity, at the latest 30 days after sign-in __Host-re_loginscookie keeps your other accounts on this device signed in when you use several (see 4.2) until sign-out; each account ends after 14 days without activity, at the latest 30 days after its sign-in __Secure-re_pending_sign_incookie holds the sign-in while you answer the age step 15 minutes __Secure-re_oidc_bindingcookie links the sign-in with Apple or Google to your browser at most 10 minutes __Secure-re_oidc_pendingcookie holds the sign-in with Apple or Google until you complete it at most 30 minutes re_devicecookie recognises your device so we can warn you about a sign-in on a new device (see 4.16a) 1 year, renewed at every sign-in re_account_noticecookie shows “Welcome back” once after signing in 10 minutes re_pass_doorcookie Security mode for Team passes: remembers on this phone which event you work the door for, so every scan counts “in” or “out” (see 4.4); only for team members with the door right 12 hours, or until you switch it off re_signin_intent,re_intent_noncecookie remembers what you wanted to do before signing in (for example save an event) so it runs once after sign-in 10 minutes re_consentcookie your choice on audience measurement (granted or refused) and whether “Remember on this device” is switched on 1 year re_themecookie light or dark mode, only if you choose it 1 year re_a11ycookie your "Accessibility" settings (for example text size, highlighted links, reduce motion), only if you choose them 1 year NEXT_LOCALEcookie the language you explicitly chose via German/English on this device; not set by automatic detection or by applying your saved account language until you close the browser re_active_profilecookie which page of your organisation you have chosen until the sign-in session ends or you sign out, at most 30 days re_previous_profilecookie which of your accounts you used before the current one, so a double tap on the profile switches back to it (your member ID and the account's ID) until the sign-in session ends, at most 30 days event_lineup_invitationcookie holds an invitation to take part in an event that you opened until the invitation expires re:region-v1local storage your chosen region until changed or deleted re_start_regioncookie which region the start page last showed (only the region's name, e.g. "westerwald", never your location), so the app and Entdecken open straight on that region instead of loading the page twice 1 year re_launch_handoffcookie hands over from the launch screen to the requested page when the installed app opens; contains only the fixed mark “1”, no identifier or location deleted when the page opens, at the latest after 15 seconds re_app_shellcookie only in the app from the App Store or Google Play: tells our server that a page is meant for the app, even when the phone asks for it without the usual app marker, so it looks as it does in the app; contains only the fixed mark “1”, no identifier or location 1 year re:in-app-stepsession storage remembers that you have already moved from one page of the app to another in this window, so "Back" takes you to where you came from until you close the window re:become-provider-draft,re-ad-enquiry-draft,re-ad-enquiry-worksession storage drafts while you register as a provider or prepare an ad enquiry until you close the window remix:kept:…,remix:kept-title:…session storage the song request you chose or typed, so it is not lost when you sign in until you close the window re.held.v1…local storage the last loaded view of Home, Discover and Rewards in your language (for example your points and rewards), so it shows at once the next time you open the app; never messages and never your profile until you sign out or switch account or profile; a newer view replaces it re:offline-passeslocal storage your Event Passes for today and the next days with your tickets' codes and, where the organiser provided them, the programme, offers, “good to know” and the number for help on site, so they open without internet (see 4.6b) until you sign out; at most 8 days old re-ticket-files-v1your browser's storage (Cache Storage) or app storage the original file (picture or PDF) of your tickets on which no code can be read, so you can show it at the entrance without internet; only for your account on this device (see 4.6b) until you sign out, switch accounts or delete the ticket; at the latest one day after the event, 14 days if no event is assigned re:pass-weather:…local storage an Event Pass's last weather line, so it still shows without internet; only the forecast for the venue, nothing about you (see 4.6b) until you clear your browser's storage re.tip.card-going.v1local storage whether you have seen the hint “Tap = I'm going” on an event card until deleted re.story-ask.off.v1local storage whether you switched off the question “Add to story?” after “I'm going” in the settings until you switch it back on or delete the entry re.story-ask.asked.v1local storage for which events (event numbers) we have already asked you, so that we ask only once per event until deleted re:account-switchedsession storage briefly remembers which account you switched to, so the “Now active” notice names the right account at most 20 seconds re.device,re.device.sentlocal storage, session storage a random identifier of this device for preventing abuse of invitations (see 4.6a) and the mark that it was already sent in this session; only set while this protection is switched on and you are signed in identifier until you delete it; mark until you close the window re:unterwegs-here-v1local storage which region you were in when you last opened the app, only the region's name and the time, never your location; only set if you allowed location access (see 4.7) 24 hours re:unterwegs-choice-v1session storage whether you switched to the region you are in right now, or back to your own region until you close the window re-error-retrysession storage the address of a page that could not be loaded and when the app reloaded it once by itself, so that it tries only once (no personal data) until you close the window (an entry counts for 30 seconds only) re:launch-place-v1session storage the first location of the app's start, only for the seconds between the start screen and the app; deleted when read and never used once it is older than 30 seconds; only set if you allowed location access (see 4.7) at most 30 seconds re:debug-standortlocal storage for troubleshooting only: turns on a log of the start sequence in the console (names and milliseconds, never a location); not set by default until you delete it re:location-ask-v1local storage your answer or “Not now” on the “Allow location” card, so that we respect your answer and ask at most every 30 days after “Not now” until you delete the entry re-locale-choicesession storage the language you just chose, until our server has stored it, so a slow connection cannot undo your choice until confirmed, at most until you close the window re-history-localesession storage the language chosen in this window, so “Back” opens earlier pages in that language until you close the window re-menu-reopensession storage after a language change in the menu, the chosen language and the time, so the menu opens once more after the page reloads; no person identifier until the menu has opened again, usable for at most 10 seconds, at the latest until you close the window offline pages ( re-offline-…)service worker storage two notice pages for when you are offline, their scripts (Event Passes and your region) and – only if you have an offline map – the map libraries; no personal content until the next app update re-offline-regionyour browser's database (IndexedDB) or app storage your region for use without internet: upcoming events, places and sights of your current and your home region, the offline map of these regions; plus your own "I'm in" and "Saved" and the latest messages of your newest chats – encrypted in the browser with a key that never leaves your device region and map until the next sync; your own data until you sign out or switch accounts, at most 10 minutes old at sync re:offline-intentslocal storage or app storage what you tapped or wrote without a connection (I'm in, follow, a message), with an internal account reference and command id, so it is sent exactly once as soon as you are online again until the server answers; messages at most 24 hours, everything else at most 7 days; deleted when you sign out or switch accounts __Secure-re_pending_resetcookie holds the requested password-reset token only for the new-password form until completed, at most 30 minutes __Host-re_invitecookie remembers the invitation code from an opened referral link for a later sign-up; only while this feature is enabled (see 4.6a) until sign-up, at most 30 days __Host-re_invite_viacookie remembers, for that invitation code, on which kind of page the referral link was opened (for example an event, then with its public identifier, or a profile), the channel marks from the link ( src,via) and the day; nothing about you; only set together with__Host-re_invite(see 4.6a)until sign-up, at most 30 days install_referrerapp storage (Android app only) whether the app has already handed the invitation code from Google Play over to us; only yes or no (see 4.6a) until you delete the app __Host-re_vorabcookie keeps the personal code from an invitation to early access until you have created your page, so the form is pre-filled after sign-in (see 4.21) until the page is created, at most 1 day re_accentcookie the accent colour you expressly chose 1 year, or until you return to the default colour re-web-build-reloadedsession storage which running and new app versions have already triggered one page reload, to prevent a reload loop; no person identifier until you close the window re_app_guestcookie your choice “Look around first” in the installed app, so you can keep browsing without signing in 1 year, or until you delete the entry re-pro-hints-hidden-…cookie for which own page you chose to hide Pro hints; the page identifier is part of the cookie name 90 days re-founder-welcomelocal storage internal identifiers of accounts whose founder-pin welcome moment was shown on this device, so another account receives its own moment until you delete the entry re-launch-greetedlocal storage that you have already seen the launch greeting on this device, so it does not appear again on the next start; a technical marker, not tracking, it is not transmitted to us until you delete the entry re.rewards.partner-unlocked-seenlocal storage whether this device has already shown the partner-rewards-unlocked moment until you delete the entry re.crew-door.teaser-hidden-untillocal storage until when the “Join the Crew” card stays hidden after you dismiss it; only a timestamp effective for 14 days; the entry remains until deleted re:store-bar:closed-atlocal storage when you closed the notice about the app in the stores with ✕, so it stays hidden for a week; only a timestamp effective for 7 days; the entry remains until deleted re.suggestions.v1.*local storage which suggestions you hid with ✕, per account on this device; internal identifiers only until deleted re:near-km-v2.*local storage the radius in kilometres you chose yourself for “Near you”, per account on this device, so it applies again the next time you open the app and after switching accounts; only the number and an internal account identifier, never a place until you choose another radius or delete the entry re:club-door-queuelocal storage entry or stamp actions already confirmed whose server answer is still missing, so they can be sent later for the same account; internal account association, signed pass, confirmation type and time until the server gives a final answer, you sign out, switch account or delete the entry re:treffen-draftsession storage your meetup entries when sign-in expires during publishing, so the form can restore them after you sign in again until restored into the form, or you close the window re:event-draftlocal storage your entries for a new event, so a page reload does not lose them; a photo chosen only locally is not stored until publication, discarding or deletion; after 14 days the draft is no longer used re:reward-passeslocal storage your reserved reward and offer passes with internal account association, signed code, item, provider and valid day, so they can open without network (see 4.6) until redeemed, the end of the valid day, sign-out, account switch or deletion re:reward-confirm-queuelocal storage the completion confirmation for your reward pass while it could not yet be sent; internal account association, signed code and confirmation time until the server gives a final answer, you sign out, switch account or delete the entry re:reward-shownlocal storage your running redemption ticket with internal account association, signed pass, reward, provider, any included points balance and start time, so you can reopen the same proof during its validity until the ticket expires, at most 10 minutes, or sign-out, account switch or deletion; expired entries are removed on the next read re:reward-reserve-intentslocal storage the reward reservation you deliberately started, so your retry after a lost response returns the same pass without booking twice; internal account, command and offer identifiers, valid day and start time until a final answer, sign-out or account switch; at most until the end of the valid day and never longer than 8 days; expired entries are removed when read re:check-in-queuelocal storage or native app storage your offline check-in with internal account association, event and command identifiers, time and the location you allowed including accuracy, so it can be sent once later for the same account (see 4.6 and 4.7) until the final server answer; usable for at most 24 hours; cleanup is attempted on sign-out or account switch and requires accessible device storage re:hashtag-preview-v1local storage the hashtags you expressly chose in the preview on this device; only slugs, never sent to the server until you remove the choices or delete the entry re.tours.seen.v1local storage which page hints your account has already seen and the server has not yet confirmed; internal identifiers only (account, hint, command), no names and no content; the entries stay on this device after sign-out until the server has confirmed them until the server has confirmed the entry or you clear the device storage The app also remembers on your device that you have already seen the launch greeting, so it does not appear again on the next start and the cold start is shorter. This is a technical marker, not tracking; it is not transmitted to us as usage statistics.
b) Remember on this device. These entries remember on your device what you have used in the app, for example your recent searches, stories you have seen and hints you have dismissed, so that you do not see them again on every visit. They do not leave your device. We set them without consent because they belong to functions you use yourself (Section 25(2) no. 2 TDDDG). You can switch them off at any time in the menu under “Cookie settings” with the “Remember on this device” switch. We then delete these entries at once and create no new ones.
Name Type Purpose Lifetime re:app-opens-v1local storage counts openings on this device so that the location card appears from the third opening at the earliest until deletion or until you switch “Remember on this device” off re:app-open-counted-v1session storage a mark that this opening of the app has already been counted until you close the window re:search-recent-v1local storage your recent searches until deleted regional-events.recent-profiles.…local storage recently viewed profiles, linked to your internal user ID until deleted re:seen-region-stories-v3,re-onboarding-seenlocal storage whether you have seen the region stories and the introduction until deleted re-profile-setup-dismissed…,re-profile-privacy-seen…local storage whether you closed or saw profile set-up notes; contains your internal user ID until deleted re-soft-prompt-shown,re-anon-strip-dismissed,re-app-banner-dismissedlocal storage whether you have seen or closed a notice (sign-up, notice bar, install) until deleted re.treffen-group-offer.…local storage whether you closed the one-time offer „Start a group?“ on one of your meetups; contains the meetup's ID until deleted re-page-views,re-page-last,re-app-banner-shown-onsession storage counts page views so the install hint is not shown too early until you close the window re:listing:…session storage state and scroll position of a list, so "Back" returns you to the same place until you close the window re_inbox_unreadsession storage number of unread messages for display until you close the window or sign out re_launchedcookie shows the installed app's launch screen only on first launch until you close the app or browser re-pro-welcome,re-page-team-hintcookie shows the welcome and the line "Add your team" once after you create a page 10 minutes, or until the line was shown once, at most 14 days re:recent-search-v2:…local storage your recent search terms and opened profiles, per account or as a guest; internal profile identifiers instead of names or photos until you delete the entries or switch “Remember on this device” off re.lastSignInMethodlocal storage last successfully used sign-in method (Apple, Google or email), no address or name until the next successful sign-in method, deletion or switching “Remember on this device” off re.signInAttemptsession storage attempted Apple or Google sign-in method in this tab until a signed-in page confirms it; no address or name until confirmation, another signed-out page, closing the tab or switching “Remember on this device” off re.following.lastVisitlocal storage the time of your last “Following” visit, so the dot only points to newer posts until the next visit, deletion or switching “Remember on this device” off re-push-ask-laterlocal storage how often and when you dismissed the push-permission question, so it returns at most once and no sooner than 7 days later until you delete the entry or switch “Remember on this device” off re-app-update-latersession storage for which recommended app version you chose “Later”; this cannot hide a required update until you close the window or switch “Remember on this device” off re:battle-last:…local storage the last loaded region-battle standings per language, so a known result remains visible during a slow read; regions and scores, no people used only in the same calendar month; until overwritten, deleted or “Remember on this device” is switched off re:after-purchase:…local storage for which purchase you dismissed the recommendation with “No thanks”, so it does not reappear; internal purchase identifier in the name, only the mark “1” as value until you delete the entry or switch “Remember on this device” off re:feedback-hint-dismissed:v1:…local storage whether you closed “Help us get better” or chose “Tell us”; internal user identifier in the name, only the mark “1” as content until you delete the entry or switch off “Remember on this device” c) Only with your consent.
Name Type Purpose Lifetime re.measure.sessionGrant,re.measure.sessionToken,re.measure.sequencesession storage random, short-lived identifier for audience measurement (see 4.14), not linked to your account until you close the window or withdraw consent re.measure.probesession storage checks after measurement consent whether session storage is available; only the fixed mark “1” removed immediately after the check d) Only with your consent to ad measurement (Meta; off by default). These cookies exist only while we have switched on the measurement of our advertising with Meta (see 4.14a) and you have consented under “Measure advertising” (Section 25(1) TDDDG). Without this consent they are not set; never in the app from the App Store or Google Play:
Name Type Purpose Lifetime _fbpcookie (set by the Meta Pixel) random identifier of your browser for measuring our advertising on Facebook and Instagram (see 4.14a) up to 90 days; if you withdraw consent we delete it immediately _fbccookie (set by the Meta Pixel) click identifier, if you came from an ad on Facebook or Instagram (see 4.14a) up to 90 days; if you withdraw consent we delete it immediately You can find your consent settings and the “Remember on this device” switch at any time in the menu under "Cookie settings". You can also delete all entries in your browser settings.
4.10 Payments
You pay for paid services such as boosts, advertising and subscriptions via Stripe (Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland). You are redirected to a Stripe payment page and enter your payment details, such as card data or your IBAN, directly with Stripe. We do not receive these details. We store a Stripe customer reference, the service purchased, amounts, payment status and invoices. Stripe processes payment data partly under its own responsibility, for example to prevent fraud and meet legal obligations; Stripe's privacy policy applies. Data may be transferred to Stripe, LLC in the USA; Stripe, LLC is certified under the EU-US Data Privacy Framework.
Depending on the payment method you choose, further providers receive the data needed for the payment and process it under their own responsibility: PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg; Klarna Bank AB (publ), Sveavägen 46, 111 34 Stockholm, Sweden (Klarna may carry out a credit and identity check under its own privacy policy); Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland (Apple Pay); Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google Pay). SEPA Direct Debit and Link are handled by Stripe.
We process invoices and accounting records in the accounting software Lexware Office of Haufe-Lexware GmbH & Co. KG, Munzinger Straße 9, 79111 Freiburg, Germany, as a processor. Incoming payments and refunds go through our business account at Qonto (Olinda SAS, Paris, France); the bank processes payment data as an independent controller.
For every payment on our website we automatically create an invoice in Lexware Office and send it to you as a PDF by email. For this we pass your name or company name, your email address and, if you buy as a business, the billing address and VAT ID you enter on Stripe's payment page to Lexware Office, where you are stored as a customer. We send the email via Resend. The legal basis is Art. 6(1)(b) GDPR, and for retention Art. 6(1)(c) GDPR in conjunction with Section 147 AO and Section 14b UStG.
Legal basis: Art. 6(1)(b) GDPR (performance of contract) and for retaining invoices Art. 6(1)(c) GDPR in conjunction with Section 147 AO and Section 257 HGB.
Purchases in the app from the App Store or Google Play. If you buy a digital service in these apps (for example Pro or a Boost), you pay through the payment system of Apple (Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) or Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). You enter your payment details only there. Apple or Google process the payment under their own responsibility, issue the invoice and handle renewal, cancellation and refunds; their privacy terms apply to this. So that we can match the purchase to your account, the app passes a random identifier of this purchase with it that contains no name and no email address. Through Apple's (App Store Server API) or Google's interfaces (Google Play Developer API, notifications via Google Cloud Pub/Sub) we receive and verify about the purchase: product, transaction numbers, time of purchase, term, price and currency and later a renewal, cancellation or refund with its reason. We store these details with the identifier to unlock the service and to prove the purchase. The legal basis is Art. 6(1)(b) GDPR, for retention as an accounting record Art. 6(1)(c) GDPR.
Advertising and Season Pins for your page. If you prepare or buy advertising or a Season Pin for a page, we store the details of your order: the page, the event where applicable, selected regions and periods, the goal, your text and the design used. We keep the preparation versions and the page’s authority to purchase. Prepared Pin templates also retain the internal account identifier of the person who prepared them as evidence. For advertising in several regions, we store which region and period each placement belongs to.
For a selected Season Pin we store a temporary reservation with its expiry time before payment. After purchase we record which page and original season period the sponsored Pin belongs to and whether that attribution was ended. The authorised sponsor page appears as “presented by”. For a Scene presentation we store the selected Scene, region and original complete calendar month purchased. We record which authorised page appears as “presented by” and whether that attribution was ended. If a payment arrives when the page, event, Scene or Season Pin is no longer available, we store the payment reference, amount, time and reason for the required reconciliation.
Design directly from a provider. If you request a Pin design through an offer, the selected provider page receives your request with the purchasing page and the event concerned. We store the request, the quote with its price, scope, terms and deadline, the delivered design and your approval. The parties’ pages can view these order details in their authorised area.
These order and sponsorship records belong to the respective page. They remain with the page when it is handed over. They are not deleted with a personal account and are excluded from the personal data export; the link to the person who prepared a template remains only as an internal account identifier. Purchase and payment records follow the retention rules in section 7.
4.10a Purchase, withdrawal and cancellation
When, on our website, you take out a subscription, buy a boost (for yourself or for a page) or buy advertising, a campaign, an Event Pin, a pin top-up or a fan badge for a page, we store for that purchase that you accepted our terms and which version, whether you buy as a consumer or as a business and, if you buy as a consumer, your declaration that the service may start immediately, each with the time and the account that bought. Campaigns, Event Pins, top-ups and fan badges are purchases of your page and only possible as a business. After payment for a subscription, a boost, a campaign, an Event Pin, a top-up or a fan badge we confirm the contract to you by e-mail. If you cancel a subscription, we store the cancellation with its time. We need this to carry out and prove the contract, a withdrawal or a cancellation. Legal basis: Art. 6(1)(b) and (c) GDPR (contract and our obligations under Sections 312f, 312k and 356a BGB).
4.11 Pages for organisers, clubs and providers
Organisers, clubs, venues, artists and service providers can create their own page showing the details they publish, such as name, description, picture, region and contact options. Business pages carry operator information under Section 5 DDG with name, address, authorised representative, register entry, VAT ID and contact details; for sole traders and small clubs this may be personal data of the owner. Not publicly, but internally for billing and administration only, we store tax number, bank details, billing address and billing contact and an internal phone number, if one is given. Artists can also state on which days they are available.
When you create a page, you give a recovery email for it. We fill in your sign-in address; you can change it. The address is not public. If nobody runs the page any more, we send a link to this address with which the page can be taken over; only someone who signs in with exactly this address can take it over. If you enter another person's address, please tell them. So that the address counts, we send it a confirmation link once when the page is created and at every change; only after the click does it count as confirmed, and the page's settings show "Email confirmed" or "Confirmation pending". For this we store when the link was sent and when it was confirmed, but of the link and the address only a hash. We keep the address until it is changed or the page is deleted. The legal basis is Art. 6(1)(b) GDPR; for another person's address Art. 6(1)(f) GDPR (your interest in the page carrying on without you).
Several people can run a page, each with their own account and a role (for example admin, editor or door). Someone can be invited by username or by email address. For an invitation by email we store the address and send it a link once; if the invitation is not accepted within 14 days and nobody has signed in with the address, we delete the address again. Your personal profile can be public or private. A private profile shows its content only to those whose request you accepted; you still appear in follower lists (see 4.3). Your check-ins, points and level still count for you. Whoever comes to Regional.Events through a page without an account (creates a page or accepts an invitation) gets a personal profile with “Private” already chosen; for it we store only the email address and the name. One tap makes it public. If you invite someone, please tell them first. The legal basis is Art. 6(1)(b) GDPR; for the invitation by email Art. 6(1)(f) GDPR (the page's interest in putting its own team together).
Paying organisers see statistics on their own events, such as how often they were viewed. These figures contain no guest names. Views of operated service provider pages are counted only as a daily number per page and shown to the operator. So that nobody can drive this number up artificially, our server keeps your IP address in its working memory until midnight, only for this counting limit; it is neither stored nor logged. We do not show such figures publicly.
Host levels: for organisers we automatically determine a level per region (host, regular host, honoured host). It is based solely on the amount paid for boosts in that region in the last 12 months (regular host from €150, honoured host from €500). The level affects how often booked placements appear first and extra boost days (see Terms § 13 and "How we sort"). We announce a downgrade 60 days in advance. We store the level per region and the boost bookings counted. Legal basis: Art. 6(1)(b) GDPR. This is not a decision within the meaning of Art. 22 GDPR, because the level only grants advantages and is calculated from fixed, published amounts. We delete the level when the account is deleted; boost bookings are kept as business records.
Search engines: pages and published events are public and can appear in search engines such as Google or Bing and in AI search services. Whoever manages a page can switch this off when editing the page with “Show in search engines”; we then ask search engines not to include the page. It stays visible in the app and through its link. When an event is published, changed, postponed or cancelled, we tell search engines only the address of the public event page through the IndexNow service, no other data. We do not show members' profiles to search engines. The legal basis is Art. 6(1)(b) GDPR, for the IndexNow notice Art. 6(1)(f) GDPR; our legitimate interest is that public events are found quickly.
When a food truck or stall adds one of its own stops at an event or market, we store which event the stop belongs to and show the stall on that event's page. If the organiser is on Regional.Events himself, we show the stall there only once he has agreed. The legal basis is Art. 6(1)(b) GDPR (the stall operator's terms of use).
If an organiser adds your page to their event as a DJ, act or other participant, we notify the page's owner in the app and by push notification with the event's title and ask whether it is right; if the page declines, the organiser is told, with the page's public name.
Legal basis for the other details in this section: Art. 6(1)(b) GDPR; for operator information and retaining billing data Art. 6(1)(c) GDPR.
4.12 Crew
As a member aged 18 or over you can join the Crew and support Regional.Events in your region. We store when and for which region you are a member, which tasks and assignments you take on and the evidence you submit (such as a link to a post). You belong to exactly one home Crew. If you join another region's Crew chat as a “guest from …”, we store in which region and since when; the others there see you with your profile and your home region. You can leave again at any time.
As a Crew member you have your own Crew link with a code. If someone registers or a business signs up via your code, we store that assignment; referrals of your own business do not count. For Crew assignments at events (on-site places) we store your reservation, confirmation or place on the waiting list. About 24 hours before the start, the organiser receives the list of confirmed Crew members. For a confirmed place you receive a Crew pass with a QR code. The QR code contains only a random string, no name and no address; we store only a check value derived from it. Whoever checks the pass on site sees whether it is valid.
Crew application and Crew agreement. When you apply for the Crew through our application link, we store with your account your first and last name, your phone number, your postal address, your region, the state of your Crew membership (for example "Active") and when you were admitted. You are admitted right after sending, without anyone at Regional.Events checking the application first. You sign the Crew agreement electronically: you type your full name and sign with your finger. For this we store your account, the typed name, the signature, the time, the version of the agreement and a checksum of the exact text. Name and signature are stored encrypted; entries are never changed afterwards. Only Regional.Events' Crew management sees your phone number, address and signature. When you are admitted, we e-mail the signed agreement as a PDF to you and to us. We delete a declined application 6 months after the decision. If your Crew membership ends, we keep the application, agreement and signature until the end of the third year after that, so the agreement can be proven, and then delete them. If you delete your account, we delete the application and signature as soon as your account is permanently deleted, unless a law obliges us to keep them. Legal basis: Art. 6(1)(b) GDPR (application and agreement) and, for keeping them as proof, Art. 6(1)(f) GDPR.
For your Crew pass we store a sequential Crew ID, your first and last name, your phone number and your private address. The pass, the check page and the organiser's list show only name, photo, role and Crew ID. Only Regional.Events' Crew management sees the phone number and address, so that we can tell who is out and about with the Crew, for instance when a pass is misused; every access is logged. You can change these details at any time under "My stuff". If you leave the Crew, we keep name, phone number and address for another 6 months, for Crew management only, so that we can follow up incidents, and then delete them automatically; if you come back within that time, they are kept. If you delete your account, we delete them as soon as your account is permanently deleted. A Crew ID is never given out a second time. Legal basis: Art. 6(1)(b) GDPR and, for keeping them after you leave and following up incidents, Art. 6(1)(f) GDPR.
Legal basis: Art. 6(1)(b) GDPR. When your Crew membership or account ends, we delete the shipping address and passes; finished assignments remain stored without your name.
4.12a Parental consent form (supervision delegation)
Anyone can download the parental consent form as a PDF without an account. What you type on that page goes only into the file you download; we store none of it.
A person under 18 starts the digital parental consent form in the Event Pass. For that one event we store: their first and last name as on their ID, the chosen companion (an account that taps "Yes, I'll look after them" itself, or a typed-in name with a mobile number) and, once a parent or guardian confirms through the shared link: their name, a mobile number for the night, the finger signature with its time, a shortened trace of the internet connection and the browser identifier, and the e-mail address the confirmation code goes to. Whoever scans the QR code from the Event Pass at the door, and the organiser of that event in their "Parental consent today" overview, see names, status, the time of the confirmation and the phone number for questions. After the event has ended, the organiser can still search the "Parental consent forms" overview until it is deleted, in case something happened, but can no longer change anything. The companion sees in their own Event Pass for that event whom they are accompanying (first name and age), until when the confirmation is valid, whether the parents have confirmed yet and, once they have, the parents' phone number. When the companion taps "Yes, I'll look after them", we mark them as going to that event ("I'm going"), just as if they had tapped it themselves (with their visibility setting, see 4.6), so they have their Event Pass; we store the time of this with the parental consent form. If the companionship ends or the parental consent form is deleted, we take this "I'm going" back, unless they changed it themselves afterwards or had already said they were going. Every view is logged (who and when, not what). We check neither parental responsibility nor the details; the organiser decides whether the parental consent form is accepted. We neither upload nor store IDs or copies of IDs. The parental consent form does not replace an ID: the young person must always carry their own ID (identity card, passport or driving licence, the original). The data is used for nothing else – no advertising, no analysis, no rewards. Legal basis: Art. 6(1)(b) GDPR (the parental consent form you request) and Art. 6(1)(f) GDPR (proof of the confirmation and questions at the door). 30 days after the event ends we delete everything about this event automatically; you can also delete your parental consent form yourself at any time. If you delete your account, we delete your entries as soon as your account is permanently deleted; if you were a companion, the entry opens again. We save your first and last name so you don't have to type it again for your next parental consent form, and whether you have ever started a parental consent form or tapped ‘I don't need this’. We delete this when you delete your account. For the digital parental consent form we also store the date of birth of the young person and of the companion, so that it can be compared with their ID at the door, the time until which the parents gave their confirmation, and which version of the declaration was ticked. We delete this with everything else 30 days after the event; your own date of birth we keep, like your name, for next time until you delete your account.
4.13 Reports and moderation
You can report content and profiles that break our rules or the law. We process your report, the reported content and details of the person concerned. The person who posted the content does not learn who reported it, unless we are legally required to disclose it. Without an account you can report guest photos and song requests directly and object to entries taken from public sources; all other content you report without an account by email to info@regional-events.de or via the report form. If you report without an account, we keep the email address you give for follow-up questions until 90 days after the case is closed. Reported guest photos and song requests are automatically hidden provisionally upon the report until a human has reviewed them.
AI pre-sorting of reports. So that we see urgent reports sooner, an AI pre-sorts every new report. For this we send our provider Anthropic (see 5) the type of the reported content, its label, the reasons chosen and the report text; we mask email addresses and phone numbers in the report text beforehand, and we do not send your name or your account. The AI suggests a category, an urgency and a possible measure. It decides nothing and hides or deletes nothing; every decision is made by a person on our team. We store the suggestion with the case for as long as we keep the case. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is handling reports quickly and in the right order.
Automatic check of uploaded pictures. Every picture you upload (for example a profile picture, page picture, event picture, story, guest photo or group picture) is checked before it is published by a recognition program on our own server at Hetzner Online GmbH (see 5) for nudity, violence and depictions of children. The picture is not passed to any other provider. If the result is clear, we show the picture as usual. If it is unsure, or if the check cannot be reached at the moment, only you see the picture until a person on our team releases or rejects it. If the result is unambiguous, we do not store the picture and tell you that we cannot show it. For every checked picture we store the result, the values of the check and a checksum of the picture; who uploaded it we store only while it waits for the check. We keep the checksums of blocked and rejected pictures so that the same picture cannot be uploaded again. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is protecting children, young people and all users from unlawful and disturbing pictures.
If we take a moderation decision, we inform those affected with a statement of reasons in the app and, if they have email notifications switched on, also by email. Against a warning, a restriction of features or a suspension the person affected can appeal in the app within 14 days. Anyone who reported content, or whose content was hidden or removed, can ask for a re-review by email within 14 days. We store appeals, requests for re-review and our decisions on them. If there is a suspicion of a criminal offence threatening the life or safety of persons, we must inform the competent authorities (Art. 18 Digital Services Act).
Legal basis: Art. 6(1)(c) GDPR in conjunction with the Digital Services Act (Regulation (EU) 2022/2065) and Art. 6(1)(f) GDPR; our legitimate interest lies in protecting our users and a safe platform.
4.14 Audience measurement and local ads
To understand how events and ads are received, we run our own audience measurement. It is off by default and only runs if you expressly consent. We count, for example, how often and how long an event's detail page was viewed and how often a local ad was shown or clicked. Measurement stores no user ID, no IP address and no name; individual events are linked by a random, short-lived identifier that is not connected to your account, is kept only in your browser's session storage (see 4.9, group c) and is deleted when it expires. No user profiles are created. Advertisers and organisers only receive aggregated figures. The legal basis is your consent under Art. 6(1)(a) GDPR in conjunction with Section 25(1) TDDDG. You can withdraw it at any time in the cookie settings; measurement then stops immediately.
Local ads and paid placements in the app are served by region and placement, not based on a personal profile, and are labelled: boosts "Sponsored", banner ads "Ad". How we sort lists is explained under "How we sort". If a paid placement is booked for particular towns, a radius or a scene, we compare, when it is delivered, the town you chose or the scenes you joined with that booking; we build no advertising profile of you from it. We use no ad networks or third-party tracking services, do not follow you across other companies' apps, and pass no data to data brokers; exceptions are the measurement with Meta under 4.14a, which applies only while it is switched on and only with your consent, and the redirect of ticket links through Awin under 4.6. This redirect is not advertising to you and builds no profile of you.
For our internal reporting we keep an activity log (for example: a sign-up, a check-in, an RSVP, a message – each only as a count with its time, region and, where applicable, the public event or public page). The log contains no names, usernames, e-mail addresses, IP addresses or member numbers. So that an event is not counted twice, we store a check value derived from the record with a secret key (pseudonymisation); the log alone does not identify a person. The legal basis is our legitimate interest in reliable figures (Art. 6(1)(f) GDPR).
4.14a Measuring our ads with Meta (only if switched on)
This section applies only while we have switched the measurement with Meta on. While it is off, none of this happens: no script from Meta loads, no Meta cookies are set and nothing is sent to Meta. In the app from the App Store and from Google Play this measurement never takes place.
We advertise on Facebook and Instagram. To see whether these ads work, our website then uses the Meta Pixel and the Conversions API of Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland ("Meta"). This happens only if you consented under "Ad measurement". Before that, nothing from Meta loads; "Decline" is an equal choice.
With your consent your browser loads a script from Meta. Meta then receives your IP address, details of your browser, the address of the page you opened without any search query, and which of these events happened: a page view, viewing an event (with our event number), a search (without the search words), signing up, creating a page for an organiser, club or business, and publishing an event. Meta sets the cookies
_fbp(a random id of your browser) and_fbc(the click id when you came through an ad on Facebook or Instagram) for this, each for up to 90 days. We also send the same events from our server to Meta (Conversions API), so they are counted even if your browser blocks the script; a shared event id makes sure Meta counts each event only once. When you sign up, create a page or publish an event we also send a hash (SHA-256) of your email address, never the address itself. Meta may link this information to a Facebook or Instagram account if you have one. We do not send names, phone numbers, home towns or search words. Automatic matching of further details on our pages ("advanced matching") is switched off.We and Meta are joint controllers for collecting these data and sending them to Meta (Art. 26 GDPR); Meta's Controller Addendum applies (https://www.facebook.com/legal/controller_addendum). Under it, Meta is responsible for answering your requests and fulfilling your rights regarding the data stored by Meta; you may also contact us. Meta alone is responsible for any further processing, for example to deliver and evaluate ads; Meta's privacy policy applies (https://www.facebook.com/privacy/policy). Meta may transfer data to Meta Platforms, Inc. in the USA; Meta names the safeguards for this in its privacy policy.
The legal basis is your consent (Art. 6(1)(a) GDPR; for storing and reading information on your device, Section 25(1) TDDDG). You can withdraw it at any time with effect for the future: in the menu under "Cookie settings" or in your account settings. When you withdraw, we stop the measurement at once and delete the
_fbpand_fbccookies in your browser. Meta deletes data it already received according to its own periods. We do not store anything about it ourselves.4.15 Operation, logs and abuse protection
The platform runs on Vercel (see 3.1 and 5); its server functions are set up for the Frankfurt am Main region. Server logs with IP addresses arise and are stored only briefly. To prevent abuse and overload we limit the number of requests per sender. For each counted request we store in our database a check value formed with a secret key (HMAC), together with the time and expiry. Depending on the feature, the check value is formed from your IP address, at sign-in from your email address, or when signed in from your internal user ID; we do not store the address itself for this. An entry only counts within its window (between one minute and 24 hours depending on the feature) and is deleted afterwards. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest lies in secure and stable operation. To keep the app fast and stable, we send technical measurements (load time, type of page, error messages) to our hosting provider for a share of page views. These measurements contain no name, no account data and no precise location.
4.16 Deleting your account and exporting your data
You can deactivate or delete your account in the app at any time (☰ › Account & security › Deactivate or delete account). Instructions, also without the app, are at https://regional-events.de/en/delete-account.
Deactivate: Your profile is no longer visible to others and can no longer be found in search, and we sign you out on every device. We delete nothing. As soon as you sign in again, your account is visible again. We only store since when your account is deactivated.
Delete: The deletion takes effect 14 days after your request; until then you can withdraw it in your settings. After that we delete your profile data, your settings, your sessions and the content tied to your account, unless statutory retention duties apply (see section 7).
To protect your account from others, we ask for a fresh sign-in before you deactivate it, delete it or change the email address of an account without a password. If your last sign-in was more than 15 minutes ago, we send you a link to your email address for this. The legal basis is Art. 6(1)(b) GDPR (contract) and Art. 32 GDPR (security of processing).
Pages you run as a sole owner are first hidden for 30 days and then deleted. Pages of clubs or companies that other people manage remain and are continued by them.
With the export function in the app you receive a copy of the data we store about your account as a downloadable file.
4.16a Notice when you sign in on a new device
So that you notice when someone else signs in with your account, we set a cookie with a random identifier on your device at every sign-in (
re_device, valid for one year). We only store an irreversible check value of it, a rough description of the device (for example “iPhone · Safari”) and the day of the first and the last sign-in. No IP address, no location, no device number. If someone signs in on a device your account has never used, we send you an email with the device and the time. We keep at most 20 devices per account; we delete everything together with the account. The cookie is strictly necessary to protect your account (Section 25(2) no. 2 TDDDG). The legal basis for storing it is Art. 6(1)(f) GDPR; our and your legitimate interest is protecting your account against access by others (Art. 32 GDPR).4.17 Images from Unsplash
Some images in the app – placeholder and sample images, and images that page owners entered as a link from Unsplash – are loaded by your browser directly from the image service Unsplash (Unsplash Inc.) at
images.unsplash.com. For technical reasons Unsplash receives your IP address, date and time of the request and details of your browser. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is an appealing presentation.4.18 Events from public sources
We take some events from publicly accessible sources, for example event calendars of municipalities or organisers. We take the event details published there (title, date, place, description, organiser). If the organiser is an individual, this may be personal data. Such entries are marked in the app as taken over. The organiser can take over the entry for their own page or object without an account; we then review the entry and remove it where appropriate. Legal basis: Art. 6(1)(f) GDPR; our and our users' legitimate interest lies in a complete overview of events in the region. You can object at any time (section 9).
4.19 Programme window on other websites
Organisers, clubs and venues can embed their programme from Regional.Events as a window or data feed on their own website. If you visit such a website, your browser loads the programme from our server. For technical reasons we process your IP address, date and time and browser details in the server logs (see 4.15). Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is delivering the programme as the organiser wishes. The website operator is responsible for embedding it on their website.
Queries through AI assistants: AI assistants such as Claude, ChatGPT, Gemini or Grok can use our public interface for AI assistants (an MCP server and an equivalent OpenAPI interface on regional-events.de) to retrieve the same public information about events and places that the website shows without sign-in. Usually the assistant's provider sends the request from its own server; some assistants, however, call the interface directly from your browser, and anyone can also call it themselves. We receive the IP address of the calling device, that is the provider's server or, when it is called directly from your browser or device, your own IP address, which assistant it is, and the search details, for example town, period, category, search words and, if the assistant sends them, coordinates for a radius search. We use the search details and coordinates only for that one answer and do not store them; we limit the number of requests as described in 4.15. We never release members' data, chats, tickets or contact details through this interface. The links in the answers name the assistant (for example utm_source=claude) so that we can see where visitors come from; they contain no information about you. What the assistant's provider does with your input is governed by its own privacy policy. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is that people can also find our public offering through AI assistants.
For editors: newspapers, broadcasters, weeklies, portals, blogs and tourism offices can show event tips from Regional.Events as a widget on their website and fetch them as a file or feed. The widget works like the programme window: your browser loads it from our server, it does not set cookies, and we store nothing about you as a reader of the outlet; to prevent misuse we only count briefly with an encrypted check value of your IP address (see 4.15). If you click an event in such a widget, we count the click for the outlet, only as a total per outlet and day, and forward you to the event page. For the free editorial access we store the outlet's name, type and website, the email address it enters itself, the language, the times of request and confirmation, the version of the usage notes, and check values of the confirmation link and the access key, not the key itself. We only send the confirmation link to this address. A request that is not confirmed within 48 hours is deleted. We count per outlet and day how often the export, feed and widget were fetched and events were clicked from them. Legal basis: Art. 6(1)(b) GDPR (the access at the outlet's request) and, for the counting, Art. 6(1)(f) GDPR; our legitimate interest is evaluating the use and reach of the widgets. The outlet can end the access at any time by email to info@regional-events.de; we then delete its details and counts.
4.20 Coming soon to your area
Coming soon to your area: if you tap “Let me know” for a town or region where Regional.Events has not started yet, we store the place you enter, or the region it belongs to, and, if you are signed in, your member ID, otherwise your email address with your consent and when you gave it. We count the entries per place or region to decide where we start next. Once it starts there, we write to you once; after that we delete your email address. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time with effect for the future by emailing info@regional-events.de; as a member, the entry is deleted with your account.
Telling us a town is in the wrong region: when you tap “Is your town in the wrong region? Tell us” under a town, a district or in the region picker, we store the town or district, the region we show it in, the region you suggest, your optional note and whether you were signed in. We do not store who you are and no IP address. To stop unlimited hints we briefly count them per member ID or per encrypted device address (see 4.15); that count is not kept with the hint. Once our team has handled the hint, we delete your note. The legal basis is our legitimate interest in towns being in the right region (Art. 6(1)(f) GDPR).
4.21 Pages nobody runs yet and taking them over
To show the region completely, Regional.Events lists events, places and businesses from publicly available sources, such as their own website or imprint. We only use business details (name, address, public contact details, dates, pictures with their source) and mark such pages as 'not confirmed by the operator'. The legal basis is our legitimate interest in a complete regional events offer (Art. 6(1)(f) GDPR). Operators can take over their page, change details or have a picture removed at any time.
Pages without an operator: for organisers, clubs and associations, venues and providers who do not use Regional.Events themselves yet, we create pages from publicly available sources, mainly their own websites, social media profiles, public event calendars and Wikidata/Wikimedia Commons. We only take details the business publishes itself: name, location, description, website, social media accounts, business e-mail address and phone number, logo or building photo with its credit, and its public events. The purpose is a complete regional calendar of events and leisure. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest and that of our visitors lies in making regional offers easy to find. These pages are labelled "Created from public sources". You can object to this processing at any time (Art. 21 GDPR): "Ask to remove this page" in the page's ⋯ menu hides it at once and it is not created again, or write to us by e-mail. Operators can also take over their page free of charge and edit it themselves.
We count how often such a page is viewed only as a daily number per page. So that nobody can drive this number up artificially, our server keeps your IP address in its working memory until midnight, only for this counting limit; it is neither stored nor logged.
If someone wants to take over such a page, we may, at their request, send a one-time confirmation code to the business email address the business itself publishes. We only store a check value of the code, which is valid for 30 minutes. We send the code only at that person's request. Separately, this address may receive an invitation to early access (see “Invitation to early access” below).
If the email address you are signed in with ends on the page's website address (for example info@club-example.de for club-example.de), that is enough for us as confirmation. If your address is not confirmed yet, we send you a code there once. We only compare the part after the @ with the page's website.
The same applies to a single event from a public source that does not belong to any page yet: if your confirmed sign-in address ends on the event's website or on the domain of the contact address it publishes, the event belongs to your page at once. Otherwise our team looks at your request. For 30 days our team can take such a takeover back, for example after a report; we record the decision with the person, time and reason. The legal basis is Art. 6(1)(b) and (f) GDPR.
If you take over a page via Instagram, we read once, through Meta's interface, the public bio of the account the page names on its own website. We only check whether your code is in it and do not store the text.
Events from Instagram posts. Our team can take over events from public posts of Instagram business accounts, for example of organisers and venues in our regions. For this we read the account's public posts (text, date, type and address of the picture, link to the post) through Meta's interface (Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland). We store only the event details (title, date, time, place, category), the account name and the link to the post; we do not copy the post's text or picture. With the event we show the original post behind “Load post”. Only when you tap it does your device load the post and a script directly from Instagram; Meta then receives your IP address, details of your browser and the page address and may set cookies or recognise you if you are signed in to Instagram. What Meta does with this data is governed by Meta, under its own responsibility, in its privacy policy. The legal basis for loading is your consent, given by the tap (Art. 6(1)(a) GDPR, § 25(1) TDDDG); without a tap nothing is loaded from Instagram. For taking over the public posts the legal basis is Art. 6(1)(f) GDPR (a complete regional events calendar); objection and removal as described above.
After a takeover we keep how the page stood before (public details and its list of events) and, for 7 days (30 days after a takeover with a document), record who changed which fields and when, without contents. This lets us resolve a wrong takeover.
If you report 'This is actually my page', we store your reason, an optional proof and your account. Only our team sees it. We record the decision with person and time; if it is in your favour, the page goes to you.
If you upload a document to confirm, we store it privately. The page is yours at once, but only provisionally at first. We then send a notice to the business e-mail address the business itself publishes (for example on its website or in its imprint), never to an address you give us. The notice names the page and contains a link to object; it does not contain your name or your e-mail address. Each takeover gets the notice only once. If sending fails, we try again a few times. Takeovers from before we started sending these notices get it once afterwards. We store when the notice was sent, the identifier our e-mail service gives the notice, whether it came back as permanently undeliverable and whether an objection was made. For 30 days from sending, the real operator can object through the link or take over the page themselves with a code sent to their published address. After an objection the page shows its state from before the takeover again. Events you created as the page during that time then belong to your own profile and no longer appear on the page; if your profile is private, we take them out of public view at the same time. If the notice arrived and there is no objection, the takeover is final after the 30 days. We offer taking over with a document only if the business publishes a business e-mail address the notice can go to. If the notice bounces, the takeover stays provisional. While it is provisional, the page’s name and website and the ticket links of its events stay as they were. If the notice was undeliverable, our team checks your document and either confirms the takeover or returns the page to its earlier state; if it returns the page, your events belong to your own profile, as after an objection. Our team only looks at the document after an objection or an undeliverable notice. With a document one person can take over at most 2 pages in 30 days. The legal basis for the notice is Art. 6(1)(f) GDPR; our legitimate interest and that of the business is to detect a wrong takeover.
Scanning a poster: if you photograph a poster or flyer, we send the photo once to our AI provider Anthropic (Anthropic PBC, USA, as a processor), which reads the title, date, place and the organiser's details. We do not keep the photo; it is discarded after reading. If the event is not listed yet, we add it with these details as an entry from a public source. We store which events you added with a scan, so we can credit you the points for it, and whether you were the first to scan a page; this is deleted with your account. If you have allowed the app to use your location, we send it with the scan, rounded to about 100 metres, to recognise the poster's place better. We do not store it. The legal basis is Art. 6(1)(b) GDPR; appropriate safeguards under Art. 44 et seq. GDPR apply to the transfer to the USA.
Organiser details from posters (Art. 14 GDPR): if a scanned poster shows the organiser's name, website, Instagram account, phone number or e-mail address, we use these details only for their page without an operator. If the poster names a website, we read its home page and imprint once to confirm the business contact details. If the organiser may be a private person, we leave out private e-mail addresses and mobile numbers. We store the postal address from the imprint only for clubs and associations, companies, municipalities and churches. To do so we read every web address and Instagram account on the poster and the QR codes in the photo, the latter on our own server. If the poster names no organiser, we read the home page and imprint of at most two of these websites once, never those of ticket shops, sponsors or media, to find out who runs the event. Logos on the poster (venue, sponsors, technical services, ticket sales, media) are stored only as company names with the event, for our internal overview; they are never shown publicly. If an event comes back every year, we remember that and, eight weeks before the next date, remind the page's operator in the app to list it again; if the page has no operator yet, our team notes it for permitted outreach. If the poster names artists, bands or DJs, we show their names as printed, as text at the event; we do not create a page for them. If an artist already runs their own page here, we link the event to it. A cover band is never listed as the original band. Our team may call the organiser once on their published business phone number or send them a letter to the postal address from the imprint, saying that the event is on Regional.Events and the page can be taken over for free; we email them only as an invitation to early access at their published business address (see below) or if they gave us their address themselves and agreed. We store who on the team made contact, when and how. Anyone who no longer wants to be contacted tells us, and we do not get in touch again. The legal basis is Art. 6(1)(f) GDPR; objection and removal as described above.
Keep follow. If you tap an act at an event that has no page with us yet, you can tap “Keep follow”. We store your user ID, the act's name as it stands in the line-up, the event and the time. If the act later creates its own page and confirms the name is theirs, you follow it automatically and get one notice in the app. The act only sees how many people are waiting, never who. The entry ends after 12 months by itself, or once you follow; you can take it back at any time. The legal basis is Art. 6(1)(b) GDPR. We do not create pages for artists or other persons.
Having an entry removed. Owners of a business can have an entry we created from public sources removed. We check by email that the request comes from the business (an address on its own website domain or, without one, the business's own address); the address is used only to send the code. The entry is hidden at once; to keep it from being imported again we keep the business's name and town on a block list. The legal basis is Art. 6(1)(f) GDPR (the business's wish not to be listed and our interest in respecting it for good).
When you create a new page, we compare its name and its town with the pages that already exist, so that no page is created twice. If it already exists, we show you the existing page to take over; a page for a municipality, a town or a district always leads to the existing page of that place. We store nothing extra for this comparison. The legal basis is our legitimate interest in avoiding duplicate pages (Art. 6(1)(f) GDPR).
Our team sees a list of pages that look the same: the same website, the same Instagram, the same phone number or the same name in the same town. If we merge a page nobody runs into another one, you then follow the page that stays, and the merged page is hidden.
Invitation to early access: where the address comes from and how we send it. We invite clubs, businesses, towns and other organisations in our regions by email to create their own page on Regional.Events. For this we write to the contact address the organisation published itself, mainly on its website or in its legal notice, on Wikidata, on OpenStreetMap or in public directories; we found some of these addresses through search engines. In our contact directory we store the organisation's name, its town and kind, the address, the source with date and when we wrote. The directory also contains organisations in regions where Regional.Events has not started yet; we write to them only when their region starts. If an organisation does not react for three years, we stop writing to it and no longer use the entry for invitations. We send the invitations through Amazon Simple Email Service of Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg, as our processor (see 5). Amazon processes the address, the content of the mail and delivery details, for example whether it bounced or was reported as spam. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to inform the region's organisations about their free page. You may object at any time (Art. 21 GDPR): via the unsubscribe option in the mail (see “Unsubscribing from our e-mails”), with a short reply to the mail or by email to info@regional-events.de; we then block the address and stop writing to it.
Invitation to early access. When we invite a club, a business or another organisation by e-mail to create its page itself, the link in it can contain a personal code. It consists of the name, the town, the region and the kind of the business as we know them from public sources, an internal identifier of our contact directory and an expiry date, and it is signed with a secret key. It contains no e-mail address, no phone number and no personal name. When you open the link, we take the code out of the address at once and keep it in a cookie on your device until you have created your page, at most one day (see 4.9). We check it on our server and only use it to pre-fill the “Create a page” form; everything stays editable, including the username we suggest from the name. We do not store the code on our server and do not link it to your account. Like any address, the first request of the link can appear in the server logs (see 3.1). An expired or invalid code is not used. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to make creating your page easier.
Unsubscribing from our e-mails. Every such invitation and every other e-mail from our contact directory can be unsubscribed with one click, also directly through the unsubscribe function of your e-mail program. For this, the unsubscribe address contains a check number from which your e-mail address cannot be read. When you click, we store this check number and the time and pass the check number on to our contact directory. There your address is blocked, and you get no more e-mails from us. Your e-mail address itself is not transmitted. We keep the check number and the time, so that another click reports nothing twice and your objection remains provable. The legal basis is Art. 6(1)(c) GDPR in conjunction with Art. 21 GDPR and § 7 UWG (honouring your objection).
4.22 Music from artists (Spotify)
Artists can show music from Spotify on their page. For this we store public details about their songs: title, cover image, release date and the link to Spotify. We fetch these details from Spotify (Spotify AB, Regeringsgatan 19, 111 53 Stockholm, Sweden) when the page adds a link, or regularly through Spotify's interface. We send no data about you. Cover images are loaded through our own server; your device does not connect to Spotify for them.
We load Spotify's player only when you tap “Listen” or “Listen on Spotify”. Until then you only see a preview made of our own content; your device does not connect to Spotify for it. Only after your tap does your device load the player directly from Spotify (Spotify AB, Regeringsgatan 19, 111 53 Stockholm, Sweden). Spotify then receives your IP address, details about your browser and device and the address of the page on which you open the player, and Spotify may use cookies or similar technologies in the player, for example to control playback or to recognise you if you are signed in to Spotify. What Spotify does with this data is governed by Spotify's privacy policy (https://www.spotify.com/legal/privacy-policy/). The legal basis for loading the player is your consent, which you give with the tap (Art. 6(1)(a) GDPR, Section 25(1) TDDDG); it applies only to that one player, and nothing is loaded without a tap. If we have switched the player off, “Listen” instead opens the Spotify app or Spotify's website outside Regional.Events. We do not connect a Spotify account of yours and do not read what you listen to. For the public details about the songs above, the legal basis is Art. 6(1)(b) GDPR (the page's terms of use).
Connecting Spotify: an artist page can connect a Spotify profile; the same Spotify profile can also be connected to several pages. We do not currently offer a confirmation with a tick, and we read neither Instagram nor a website for it. If a page confirmed its Spotify profile earlier (with a code in the bio of its Instagram account or with links on its website), we keep showing that tick and store only whether, how and when it was confirmed, not the content of the bio or the website. If someone reports an artist page with the reason “This is not this person”, our team can remove the connection to Spotify; the songs taken from Spotify then disappear from the page, and we keep a note that this page may not connect that Spotify profile again. The legal basis is Art. 6(1)(b) GDPR (the page's terms of use) and Art. 6(1)(f) GDPR (our legitimate interest in fans not being misled by someone else's music).
Insights for artists with Premium. If you follow an artist page that uses Premium, the page sees how many of its fans come from which town. For this we count the town you set under “My town”. A town is only named from three fans; your name together with your town is never shown. The page also sees how many new fans joined after a gig, and the fans who have followed it longest, as they appear in its follower list anyway. It never sees who voted or checked in. The legal basis is Art. 6(1)(f) GDPR (the artists' legitimate interest in an aggregated view of their reach). You can clear “My town” in the settings at any time.
4.23 Polls on pages
Pages (artists first) can run polls. If you vote, we store your choice with your account, so each person votes only once and you see your choice again. The page and other members only see the number of votes per answer, never who voted how. Your votes are part of your data export (see 4.16). If you delete your account, we delete your votes; if the page deletes a poll, we delete all its votes. Reported polls are reviewed like other reported content (see 4.13). The legal basis is Art. 6(1)(b) GDPR.
5. Recipients and processors
We only pass on your data where necessary for the purposes described. These service providers process data on our behalf and on our instructions (Art. 28 GDPR):
- Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA – hosting of website and platform, storage of files (profile pictures, event pictures, guest photos, documents, tickets) in private storage (Vercel Blob)
- Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany – storage for the regions' offline maps and our own server for the automatic check of uploaded pictures (see 4.13)
- Neon, LLC, a Databricks, Inc. company, 160 Spear Street, Suite 1300, San Francisco, CA 94105, USA – platform database; the database is located in Frankfurt am Main (Amazon Web Services, region eu-central-1)
- Resend, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA – sending emails (confirmation links, password reset links, notifications, confirmations, invoices)
- Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg – sending the invitations to early access (Amazon Simple Email Service), see 4.21
- Anthropic PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, USA – AI reading of poster and flyer photos and of links when an event is entered, pre-sorting of reports (see 4.13), reply drafts for support requests (see 4.4), and a weekly report from reach totals without personal data (see 4.6) (processor; transfer to the USA with appropriate safeguards under Art. 44 et seq. GDPR)
- Haufe-Lexware GmbH & Co. KG, Munzinger Straße 9, 79111 Freiburg, Germany – accounting and invoices (Lexware Office)
- HubSpot Ireland Limited, 1 Sir John Rogerson's Quay, Dublin 2, Ireland – contact management for website enquiries and sign-ups
- Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, Ireland – email inbox (Google Workspace)
We also transfer data to these recipients, who process it under their own responsibility:
- Stripe Payments Europe, Limited, Dublin, Ireland – for fraud prevention and legal obligations; Stripe carries out the payment processing itself as our processor; depending on the payment method also PayPal, Klarna, Apple or Google (see 4.10)
- Qonto (Olinda SAS), Paris, France – our business account
- Google Ireland Limited, Dublin, Ireland – sign-in with “Continue with Google”, if you choose it (see 4.2); online meetups via Google Meet; delivery of push notifications to Android devices via Firebase Cloud Messaging; purchases in the app from Google Play (see 4.10); “Save to Google Wallet” (see 4.6b)
- Apple Distribution International Ltd., Cork, Ireland – sign-in with “Continue with Apple”, if you choose it (see 4.2); purchases in the app from the App Store (see 4.10)
- Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA – delivery of push notifications to iPhones via the Apple Push Notification Service (see 4.8)
- Meta Platforms Ireland Limited, Dublin, Ireland – only if we switch it on and you consented: measuring our advertising on the website (see 4.14a); fetching public Instagram bios and posts through Meta's interface (see 4.21, 4.22); your device loads an Instagram post directly from Instagram only after you tap “Load post”
- WhatsApp Ireland Limited, Dublin, Ireland – only if you asked for a WhatsApp notification
- OpenStreetMap Foundation, Cambridge, United Kingdom – converting venue addresses into coordinates (no personal reference to you)
- Bright Sky (api.brightsky.dev), a service that provides open weather data of the German Weather Service – our server fetches the weather forecast for the venue (Event Pass, weather notices; see 4.6b); only the venue's coordinates rounded to about one kilometre and the time window are sent, nothing about you
- Unsplash Inc. – images requested by your browser (see 4.17)
- Wikimedia Foundation, Inc., 1 Sansome Street, Suite 1895, San Francisco, CA 94104, USA – Wikidata and Wikimedia Commons: our server fetches public details and image files on sights for whole areas, partly through the Wikidata mirror query service QLever of the University of Freiburg (Germany); the queries are not related to individual visitors, nothing about you is sent (see 4.21)
- Spotify AB, Stockholm, Sweden – fetching public details about artists' songs, without data about you; only after you tap “Listen”, Spotify's player or Spotify outside Regional.Events (see 4.22)
- other users, where you make content visible to them
- authorities and courts, where we are legally required
- our tax adviser, where necessary for accounting and tax
Recipients that are controllers in their own right (not processors): when you tap a ticket link of a partner programme, we redirect you through the partner network AWIN AG, Otto-Ostrowski-Straße 1A, 10249 Berlin, Germany, to the ticket provider (see 4.6). Awin and the ticket provider process what reaches them in their own responsibility under their privacy notices.
6. Transfers to third countries
Some of these providers are based in the USA or use facilities there. We base a transfer to the USA on the European Commission's adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR). According to our check on 20 October 2026, the following recipients are certified under the EU-US Data Privacy Framework: Google LLC, Stripe, LLC, Vercel Inc., Resend, Inc. and – for Neon – Databricks, Inc. For the United Kingdom there is an adequacy decision of the European Commission. You can request a copy of the safeguards from us.
7. Retention
We store personal data only as long as necessary for the respective purpose or until you withdraw your consent. In detail: server logs at most 30 days; website form data until your request is handled, your meetup attendance or requested notification is complete, or you object or withdraw consent; account and content in the app as long as your account exists, and after deletion (effective 14 days after the request) as described in 4.16; sole-owner pages hidden for 30 days after account deletion, then deleted; location data not stored; audience measurement – the random identifier is deleted when it expires, only aggregated figures without personal reference remain; invoices and accounting records 8 years, commercial letters and other tax-relevant documents 6 or 10 years (Section 147 AO, Section 257 HGB); records of purchases, consents, withdrawals and cancellations until the statutory limitation period ends (usually three years from the end of the year in which the claim arose, Section 199(1) BGB), unless they must be kept longer as accounting records; emergency contact until you remove it, at the latest with your account; referral assignment and host level as long as the account exists; check values for request limits until their window has passed (at most 24 hours); reports and moderation decisions as long as needed to trace the decision, for appeals or to meet legal duties, and the contact address of reporters without an account 90 days after the case is closed.
Where legal retention duties prevent deletion, we restrict processing and delete the data when the period expires.
8. Legal bases
- Consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG): audience measurement in the app, location access, launch reminder and WhatsApp notifications.
- Contract and pre-contractual steps (Art. 6(1)(b) GDPR): account, profile, emergency contact (your own details), content, messages, saved events, RSVPs and check-in, referral links, notifications, payments, withdrawal and cancellation, organiser and provider pages, host levels, Crew, support, meetup and call sign-ups.
- Legal obligation (Art. 6(1)(c) GDPR): retaining invoices and accounting records, operator information, confirmations under Sections 312f, 312k, 356a BGB, obligations under the Digital Services Act for reports and moderation.
- Legitimate interest (Art. 6(1)(f) GDPR): server logs and abuse protection, origin information for forms, geocoding of venue addresses, images from Unsplash, proof of consents, answering general enquiries, moderation to protect users, content about people who are not users, data of emergency contacts entered, events from public sources, programme window on other websites.
- Storage on your device without consent (Section 25(2) no. 2 TDDDG): the entries in 4.9, groups a and b.
8a. Required information, no automated decisions
For an account we need your email address and your confirmation that you are at least 16; without them we cannot provide an account. For purchases we need the details required for payment and invoicing. Everything else is voluntary. You are not legally obliged to give us data.
We make no decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). Moderation decisions are made by a human. An AI only pre-sorts reports (see 4.13); it decides nothing. Reported guest photos and song requests are automatically hidden provisionally pending review; a human then decides. Uploaded pictures are checked by a recognition program before they are published (see 4.13): a person decides on an unsure picture; only a clearly impermissible picture is automatically not stored. If you think that was a mistake, write to us and a person will look at it. If check-ins or invitations show a pattern that looks like abuse of the points programme (for example two check-ins too far apart to travel between, or very many sign-ups through one invite link in a short time), the system pauses redeeming points for now; the points are kept, and a person from our team decides. For this we only use data we already store for the points programme. At registration we also check whether the email address belongs to a known throwaway inbox; such an address cannot open an account. Nothing is stored for this. The order of lists follows fixed rules (paid placement, taking into account the host level under 4.11, date, name), not a personal profile.
9. 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 (Art. 21). You can exercise many of these rights directly in the app: change profile details, delete content, export data and delete your account. Otherwise a message to info@regional-events.de is enough.
Withdrawing consent: you can withdraw consent at any time with effect for the future, for example in the app's cookie settings, in your browser or device settings, or by email. This does not affect the lawfulness of processing before the withdrawal.
Right to object under Art. 21 GDPR: where we process your data on the basis of a legitimate interest (Art. 6(1)(f) GDPR), you have the right to object at any time on grounds relating to your particular situation. We will then stop processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims. You can send your objection informally to info@regional-events.de.
Right to lodge a complaint: you have the right to complain to a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is: Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz, Hintere Bleiche 34, 55116 Mainz, Germany.
10. Children and young people
You must be at least 16 years old to use Regional.Events. When registering you confirm that you are at least 16. Chats, groups and meetups are open to every member; we do not ask for your age for them. Some features are only available from 18, in particular purchases, pages for clubs, businesses and music, rewards with alcohol, meetups “For singles”, joining the Crew, on-site Crew shifts at events and events marked "18+". For these you confirm once, with a tick, that you are at least 18, when you first use such a feature. If you said you are under 18, we do not show you the invitation to the Crew, and you cannot join the Crew. We store only this confirmation; if you gave your birthday earlier, the result from then and – while you are not yet 18 – the day you turn 18. Rewards with alcohol: the venue checks your ID when you redeem. We use this answer only to control access to these features, not for advertising or display in your profile.
11. Security
We protect your data with technical and organisational measures, in particular: encrypted transmission of all connections via HTTPS; sign-in with a password, with passwords stored only as salted hashes and confirmation links, password reset links and session keys only as hashes; private storage of profile pictures and guest photos and videos, removal of metadata such as location; access to internal data on a least-privilege basis and a second factor (one-time code) before admin actions affecting user accounts and content; limiting requests per sender to prevent abuse.
12. Changes to this policy
We update this privacy policy when our service, the services we use or legal requirements change. The version published here applies. We also inform you in the app or by email about material changes that affect your account.
Last updated: 19 November 2026


