Privacy policy
Last updated: November 2026
This privacy policy explains how Alphabees UG (haftungsbeschränkt) processes personal data when you visit the Alpha Events website or use the Alpha Events platform – as an organiser, team member, artist, crew member, guest, ticket buyer or visitor. This is a translation for convenience; the German version is legally binding.
1. Controller
Alphabees UG (haftungsbeschränkt) Kolonnenstraße 8 10827 Berlin Germany Email: info@alphaevents.tech
Represented by the managing directors Lasse Erdweg and Marcel Pasternak.
Data protection officer: Lasse Erdweg, reachable at info@alphaevents.tech.
2. Who is responsible for what?
We are the controller for processing on our website, for user accounts and organisations, for credit purchases, for contact and demo requests, for problem reports from the back office and for audience measurement.
Organisers use Alpha Events to run their events. For the data they manage there – for example artists, crew and volunteers, bookings and riders, shift plans, guest lists, ticket orders, wristband balances, the visitor app, newsletter subscriptions, surveys and applications – the respective organiser is the controller. We process this data as a processor under Art. 28 GDPR, solely on the organiser's instructions (Annex A of the platform terms at /terms). Please direct questions and requests about this data to the organiser, whose details you will find on the respective pages (e.g. in the ticket shop). If such a request reaches us, we forward it to the organiser and help them answer it.
3. Visiting the website
When you open our pages we process technically necessary data: IP address, date and time, requested address, referrer, browser and operating system. It is stored in operational logs in order to deliver the pages, analyse errors and prevent abuse.
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in secure and stable operation).
Festival guide (/festivals): we count how often a festival page is viewed and how often links to the festival's website, ticket shop or social networks are clicked. So that each person counts only once per day, we derive an encrypted check value from IP address, browser identifier, festival and date, which is deleted automatically after 48 hours; we do not store the IP address or browser identifier. Nothing is stored on your device. Only aggregated daily figures without personal reference are kept. Links to festivals carry a note that you come from Alpha Events (utm_source/ref parameters) so the organiser can see where visitors come from. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in measuring the guide's reach).
Reach measurement with Umami: on our information pages – such as the home page, product and pricing pages, blog, guides, tools, event directory and festival guide – we use Umami Cloud to measure how often pages are viewed and where visitors come from. The back office, portal, sign-in, visitor app, ticket shop, guest lists and scanners are not measured. Umami does not set cookies. It records the requested address including campaign parameters (e.g. utm_source), page title, referrer, browser, operating system, device type, screen size, language and approximate location (country, region, city). Your IP address is processed only briefly to determine the approximate location and to form an anonymous visit identifier (a hash of IP address, browser identifier and a random value that changes monthly); it is not stored in the analytics data. Umami and its infrastructure providers may also record IP addresses in operational and security logs. Umami processes the data on our behalf (section 11). Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in measuring the reach of and improving our website).
4. User account and organisation
For registration and use we process first and last name or artist name, email address, password (as a hash only), optionally phone number and profile picture, organisation name, roles and permissions, and the time and version of the accepted platform terms. To protect accounts we process session data, failed sign-in attempts and – if enabled – two-factor authentication data. Our team is notified internally about new registrations.
If you choose to sign in with Google, Microsoft or Apple, we receive your first and last name, email address, whether the provider has verified that address, and an identifier of your account there from the respective provider; we then store no password. Signing in with the provider is governed by its privacy policy (Google Ireland Limited, Dublin; Microsoft Ireland Operations Limited, Dublin; Apple Distribution International Limited, Cork). Data may be transferred to the USA in the process (section 12).
Legal bases: Art. 6 (1) (b) GDPR (contract) and Art. 6 (1) (f) GDPR (protecting accounts against abuse).
5. Credits and payments
Paid features are paid for with credits. Credits are bought via Stripe; Stripe does not pass card details or other payment details on to us. We store the purchase amount, time, payment reference, invoice details and credit usage.
Legal bases: Art. 6 (1) (b) GDPR (contract) and Art. 6 (1) (c) GDPR (retention obligations under commercial and tax law).
Ticket payments and online top-ups, on the other hand, run through the organiser's own Stripe account, and card payments at the till through the organiser's SumUp account; the organiser is the controller for these (section 2).
6. Contact, demo requests and problem reports
If you email us or request a demo, we process your details (such as name, email address, preferred contact channel and date, event size and message) to answer the request and keep the contact in our customer management system. Problem reports from the back office contain your description, the contact channel you entered, your account and organisation, technical details about your browser and app version and – if you attach them – screenshots. Our team is notified internally about demo requests and problem reports.
Legal bases: Art. 6 (1) (b) GDPR (pre-contractual steps and performance of the contract) and Art. 6 (1) (f) GDPR (answering requests, fixing errors).
Adding or correcting a festival (festival guide): when you submit a festival or send a correction, we process the festival details, your message, your email address and, optionally, your name and role (organiser, fan, other). We use them to check the details, to answer you if we have questions and – if we accept the submission – to inform you about it once by email. Our team receives an internal notification with the festival's name, not with your contact details. Submissions are deleted automatically 180 days after they arrive. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in an accurate festival guide and in answering your submission).
7. AI features and connected AI assistants
Some features use AI models from OpenAI, for example reading uploaded invoices, planning suggestions, text suggestions for emails and shop texts, summaries of free-text survey answers, importing wristband lists and the onboarding bee "Bea". Processing only takes place when a user triggers the feature, and only the content needed for it is transmitted. Bea receives no field values or table contents of the page. Questions you type into Bea yourself are stored together with your user account, your organisation, the page you were on and Bea's answer, so that we can improve Bea and spot common difficulties in using the platform; the legal basis for this is Art. 6 (1) (f) GDPR (legitimate interest in improving our service).
OpenAI does not use the inputs to train models and keeps them for at most 30 days for abuse monitoring. AI results are suggestions: they are only applied after a person confirms them.
For the festival guide, at the click of a platform admin an AI reads a festival's public website (including its imprint) and proposes details. Names and contact details shown in the imprint may be transmitted to OpenAI in the process; only what a person confirms is applied. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in accurate festival information).
Legal basis: Art. 6 (1) (b) GDPR; for organisers' data, their instructions under section 2.
Connected AI assistants (ChatGPT, Claude): You can connect your account to an AI assistant such as ChatGPT (OpenAI) or Claude (Anthropic). The assistant then works on your behalf in exactly one organisation, which you select and approve when connecting, and only with your permissions in that organisation. It retrieves data when you prompt it with a question or task, and on your instruction it can make changes – for example create artists, add bookings or change their status, add stages and timetable slots, plan and staff shifts, create guest lists and invite links, create, change and delete cost plan positions, income and invoices, create, change and delete tasks, add appointments to the team calendar (external participants then receive an email invitation), write, publish and delete posts in the community feed of the visitor app, or switch bar tills on and off and assign products to them. These changes are saved directly, not as a suggestion first.
In the process, the provider of the assistant receives the name of your organisation, your name and your permissions, the names of the team members (with the people or settings permission also their email addresses and roles) and the data requested in each case. The assistant can retrieve everything you can see in the back office with your permissions, in particular: • Events: planning status, address, timetable, day sheets, site plan, riders, budget with costs, invoices and income, and the team calendar with appointments and the email addresses of external participants. • People: with the people permission name, roles, tags, email address, phone number, social media links, notes and document names, otherwise only identifier, name, roles and tags. • Bookings: fee, deal, payments, settlement and contract with the counterparty (name, email address), signatures (name, time) and, on request, the contract text. • Shifts with assigned people and the names of applicants, and tasks with assignees. • Ticket shop: sales figures, aggregated information on buyers' origin and age groups, orders with the buyers' details (name, email address and the other details requested at purchase) and the admission status. • Guest lists with the guests' name, email address, affiliation and check-in, and the lists' links. • Application forms with all submissions: contact details (such as name, email address, phone number, date of birth, gender, place of residence) and all answers; uploaded files only by their name. • Suppliers with contact persons and document names, survey results including free-text answers, figures on newsletters, bar tills, wristbands and the visitor matcher, the tills with their products, the community posts of the visitor app and the credit balance.
We do not transmit artists' information on diet and allergies (health data). We do not transmit scanner PINs, access and signing keys, Stripe and SumUp payment identifiers or the files themselves.
The provider receives this data at your initiative. It is not our service provider; it processes the data – like everything you type into the assistant yourself – under the terms and privacy notices you have agreed with it. These also determine how long it keeps the data, whether it uses it for training and in which countries it processes it. The statements on OpenAI above only apply to our own AI features. For data managed by an organiser, the organiser remains the controller (section 2).
For the connection we store the registration of the app (including its name and redirect address), your approval for the organisation with its date and the keys the assistant signs in with (access valid for one hour at a time, renewal for up to 30 days). To prevent abuse, we limit the number of requests. You can disconnect at any time under Account settings → "Connected apps"; the approval and keys are then deleted and the assistant loses access immediately. It also loses access if you leave the organisation. Data the provider has already received is not affected; its deletion is governed by the provider's terms. Legal bases: Art. 6 (1) (b) GDPR (providing the connection you requested) and Art. 6 (1) (f) GDPR (protection against abuse).
8. Visitor app, ticket shop, guest lists and scanners
Organisers provide public areas for visitors: the visitor app (programme, timetable, map, community, matcher, wristband balance), ticket shop, guest lists and guest passes, application forms and surveys. We process the data entered or generated there on behalf of the organiser (section 2).
You only receive push notifications from the visitor app if you subscribe to them in your browser (Art. 6 (1) (a) GDPR); you can end the subscription at any time in the app or in your browser settings. Favourites and similar visitor app settings are stored locally in your browser.
Trackable QR codes redirect via an intermediate page. The time, device type, operating system, browser and approximate location (country, region, city) are recorded; your browser looks up the location from your IP address directly at the service ipwho.is, and we do not store the IP address itself. Detailed scan entries are deleted after 30 days; only aggregated figures remain after that.
11. Service providers
We use carefully selected service providers; where they act on our behalf, a data processing agreement under Art. 28 GDPR is in place:
• Hetzner Online GmbH, Gunzenhausen, Germany – application hosting and file storage; data centres in Germany. • MongoDB Limited, Dublin, Ireland (MongoDB Atlas) – database; cloud region in the EU. • Amazon Web Services EMEA SARL, Luxembourg (Amazon SES) – sending emails; Frankfurt region. • OpenAI Ireland Ltd., Dublin, Ireland – AI features (section 7); processing in the USA. • Mapbox, Inc., Washington, DC, USA – map tiles in the map editor, the visitor app and the festival guide's map view (only once „Map“ is chosen); loaded directly from your browser (IP address, map section). • Unlayer, Inc., USA – embedded email editor in the back office. • Discord Inc., San Francisco, USA – internal notifications for our team (sections 4 and 6). • Umami Software, Inc., San Francisco, USA (Umami Cloud) – reach measurement on our information pages (section 3); analytics data stored in the EU, delivery, security and operational logs may involve services in the USA. • Browser vendors' push services (Apple, Google, Mozilla) – delivery of subscribed push messages; content end-to-end encrypted. • Stripe Payments Europe, Ltd., Dublin, Ireland – payment processing for credit purchases (independently responsible for payment data).
In addition, your browser loads content directly from third parties in some features, which receive your IP address in the process: YouTube (Google) when playing an artist video in the matcher – only after you click the video – or an aftermovie in the festival guide (only after a click, in privacy-enhanced mode), the respective festival's website when festival images are shown in the festival guide (share image and photos load directly from there, we do not store them), ipwho.is when opening trackable QR codes (section 8) and the jsDelivr CDN for emoji images in the back office.
12. Transfers to third countries
Some service providers also process data outside the EU and EEA, in particular in the USA. Such transfers are based on an adequacy decision of the European Commission (such as the EU-U.S. Data Privacy Framework) or on the EU standard contractual clauses under Art. 46 (2) (c) GDPR.
14. Retention
We only keep personal data for as long as the respective purpose requires. We delete account data after use ends unless statutory retention obligations apply; invoices and accounting records are kept for up to ten years under § 147 AO and § 257 HGB. Detailed QR scan entries are deleted after 30 days. Analytics data from reach measurement with Umami is deleted after 6 months. Organisers can archive finished events; guest data, among other things, is then deleted after export. Otherwise the organiser, as controller, decides how long their data is kept.
15. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). You can withdraw any consent at any time with effect for the future (Art. 7 (3)). To do so, contact info@alphaevents.tech – for data managed by an organiser, contact the organiser (section 2).
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit).
16. No automated decision-making
We do not make decisions based solely on automated processing that have legal effects on you (Art. 22 GDPR).
17. Data security
We protect your data with appropriate technical and organisational measures. These include encrypted connections, a graded role and permission model and strict separation of the data of different organisations.
18. AI transparency
AI features and the onboarding bee "Bea" are recognisable as AI in the interface. Answers and suggestions are generated by an AI model, may contain errors and do not replace professional advice.
19. Children
The Alpha Events back office is not aimed at people under 16. We do not knowingly collect data from children for our own purposes. If you believe we hold such data by mistake, please write to us.
20. Changes
We update this privacy policy when our platform or the law changes. The version published here applies.