Last updated: 21 November 2026
This notice explains which personal data AcroSpot processes, why and on which legal basis, who receives it, how long it is kept and what your rights are. It follows the Swiss Federal Act on Data Protection (FADP) and, for people in the EU and the EEA, the General Data Protection Regulation (GDPR).
AcroSpot (acrospot.org) is run by Sandro Winkler, J. J. Balmer-Strasse 1, 4053 Basel, Switzerland (see the imprint), who is responsible for the processing described here. For every question about your data write to info [at] acrospot.org.
Organizers who publish events on AcroSpot are responsible on their own for the registration details they receive (independent controllers). AcroSpot passes your registration details to the organizer so that your ticket contract with the organizer can be carried out. How the organizer uses them is up to the organizer; our terms of use allow it only to run that event.
For an account we need your email address. You log in with a code sent by email, with Google, with Facebook, with a passkey or with a password you set (stored only as a hash). When you sign up we ask your name, where you are right now (your home or, if you travel, your travel location), your acro role and disciplines with your levels, and that you are 18 or older and accept the terms of use and this notice.
In the settings you can add more: a profile picture, mobile number, date of birth, gender, ID or passport number, social links, About me, languages, since when you do acro, tricks, interests, diet and allergies, and whether you host guests, help or cook at events. Date of birth, gender and ID number never show on your profile; they only fill in events that ask them, for example a sports association or a venue that keeps a guest register. Organizers and teachers also give contact details, a mobile number and, for teachers, payout details.
If you log in with Google, Google tells us your name, your email address and your Google profile picture. A new account takes the picture once as its profile picture, stored by us, so no page loads it from Google; you can change or remove it. We don't receive your Google password or anything else from your Google account.
If you log in with Facebook, Facebook tells us your name, your email address and your Facebook profile picture, which a new account takes the same way. Only the login goes through Facebook: no page of AcroSpot loads anything from Facebook (an Instagram video loads Meta's player only when you tap it, see below), and we don't receive your Facebook password, your friends, posts or anything else from your Facebook account.
Name, email address, location, role and disciplines are needed to use AcroSpot; everything else is up to you. An event can ask more when you register, for example your mobile number (often required); the registration form shows what is required.
When you register for an event, AcroSpot stores a copy of the details that event asks: name, email address, role and levels and, if asked, mobile number, date of birth, gender, ID or passport number, where you travel from, social links, languages, since when you do acro, diet and allergies, and your answers to the organizer's questions. With it we store your ticket, stay, extras, partner and the people you come with, check-in and payment status. What you keep in your profile stays with AcroSpot: an organizer receives your details only when you register for one of its events and allow it in the form, which lists what goes to it. That permission counts for that organizer until you withdraw it in Settings → Privacy.
Card payments are processed by Stripe on the organizer's Stripe account; your card details never reach AcroSpot. We store amounts, fees, the payment status and Stripe's reference numbers. Payments directly to the organizer and cash at the event happen outside AcroSpot; we store only what the organizer marks as received.
When you open the booking link of an event booked on the organizer's own website, we count the click with the event, the time, your account if you are logged in, and where you came from: the area of AcroSpot (such as the event page) or the name of the other website (such as "example.com"), never the whole address; no IP address and no cookie. The organizer sees only the numbers. The link tells the organizer's website that you came from AcroSpot (utm_source=acrospot).
Organizers enter some data themselves, for example a correction at the check-in desk, a payment they received or a travel group. The organizer's team and an event's team can keep short internal notes on you (for example special needs or changes you asked for), and the AcroSpot team on accounts and on organizer and teacher requests. They are not shown to you in the app, but like all your data you can ask us for them (see your rights below). Notes are deleted with the event, the organizer or your account.
Allergies are health data, and a diet can hint at a religion. We store allergies and intolerances (gluten-free and lactose-free included) only with your explicit consent, which you give by filling them in. When you register for an event they go only to that event's organizer and team, for the kitchen and for your safety. In your profile they are kept only when you fill them in under Settings or tick “Save the changes to my AcroSpot profile” when you register.
We delete allergies from registrations 30 days after the event ends. In your profile they stay until you empty the field. You can withdraw your consent at any time in Settings → Event preferences or by email; this does not affect what was done before.
New profiles are public, so AcroPeople can find each other: others can find your profile and see what you put in it. You can make it private at any time in Settings → Privacy; then people can follow you only with your approval. With a public profile you appear in the participant lists of your events (name, Instagram, where you are from); you can switch this off for each registration and in Settings → Privacy. Partner matching shows your role and levels to others looking for a partner at the same event, and hosting shows your offer to participants nearby. Listed teachers' profiles and organizers' pages are public.
Messages are stored and shown to the members of the conversation. We tell you about new messages by email; if you answer that email, your answer is added to the conversation.
Profile pictures, organizer logos and event photos are stored as images we re-encode, so data such as the GPS position in a photo is never stored. Only post pictures of people who agreed to it.
Organizers can add videos to an event, and teachers and organizers to their page, that are hosted on YouTube, Vimeo, Instagram or TikTok. When you open a page with a video from YouTube or Vimeo, your browser loads its preview picture from YouTube (Google) or Vimeo, so they see your IP address; the preview picture of an Instagram or TikTok video is a copy we store, so nothing loads from them until you tap it. The video plays only when you tap it, in YouTube's privacy-enhanced player, Vimeo's player without tracking, or the player of Instagram (Meta) or TikTok; while it plays, that site receives what its player needs and may set its own cookies. Links to other sites open only when you tap them. Teachers and organizers can also upload a video of their own: your browser makes it smaller first and leaves out its tags (such as the phone and the place where it was filmed), then it is stored with us like the photos and played by our own player, so nothing loads from another site.
We use your home and travel location for events and people near you, hosting and the emails about events nearby; coordinates are rounded to about 1 km. Your device location is used only when you tap "Use my location". To turn a place into coordinates, and coordinates into a place name, we ask the Nominatim service of OpenStreetMap. For your home or travel location, and for an organizer's city, we send only the city and country, or the rounded coordinates. For the place of an event or of its accommodation we send the name and address the organizer entered, which are shown on the event page anyway. When an organizer gives the address of the seller of their tickets, we send it to Nominatim to check that it is on the map, when they continue in the request and when they save it in the settings; its position is kept only for the organizer's team and the AcroSpot team and never shown publicly. While you type a city or a street, our server asks Photon from komoot for matching places, in the chosen country or, while no country is chosen, in all countries, sending only the typed letters, the city and the country. These suggestions, and the place of your device location, are limited per minute: per account, or per internet address while you have no account yet (when you sign up while registering for an event).
The country and approximate location that our hosting provider Vercel derives from your IP address are used to suggest your country and currency and, for visitors without a location, events nearby; they are not stored, except the approximate place with a login code you ask for, until it is deleted within about an hour and a half, or within about two and a half hours when you confirm your email while registering for an event (see "Security, support and logs").
Maps load their map tiles from OpenFreeMap; your browser connects to it, so OpenFreeMap sees your IP address.
We send the emails the service needs (login codes, a welcome email after you sign up, tickets, payments, changes to your events, messages) and notifications you can switch off in Settings → Notifications. "New events near me" and "Discounts at events near me" are sent only if you switch them on, at sign-up with the box "Tell me about new events and discounts near me" or in the settings; we keep the time of your consent and use your location, radius and disciplines to pick the events. You can switch them off at any time. No newsletters and no advertising. The platform owner can read a copy of each email we sent for 7 days, to check that our emails work; one-time login codes are hidden in it.
"For you", suggested people and the order of partner suggestions are worked out from your location, levels, interests, follows and the events you go to. This is profiling in the sense of the law, but no decision with legal or similarly significant effects for you is made automatically.
To run and secure AcroSpot we record which action an account ran and how it ended (success, error, not allowed), with the time and the order or the event it was about. No form contents, messages, payment details or IP addresses. It helps with support, with following up reports and with finding errors and misuse. Only the platform owner and admins see it, and it is deleted after 30 days.
When a page shows an error (a page that doesn't exist, or an error on our side) or a script on a page breaks in your browser, we record it on our own server: the page, the time, the pages you opened just before in the same browser tab (kept only in that tab until then), the page you came from, if you are logged in your account, the technical error message (without what was entered in a form) and, in rough terms, on what it happened: browser and system with their main version (for example "Safari 18, iOS 18"), phone, tablet or computer, the version of AcroSpot, the page's language, whether the window was narrow, medium or wide and whether AcroSpot ran as an installed app. No IP address, no full browser identifier, no cookie, no form contents, no analytics service. It helps us find and fix errors. Only the platform owner and admins see it, and it is deleted after 90 days. Once a day, errors on the website are summarised as tasks for our developers on GitHub (Microsoft), only as counts and page addresses, without your account, name, email address or what you entered.
To learn what makes events work, we count on our own server when an event page, its registration or booking form or a step of the registration is opened: the event, the time and, if you are logged in, your account. No IP address, no cookie, no analytics service. While you are logged in, these visits also appear in the record of actions above (30 days). The visits themselves, with your account if you were logged in, are kept for one year and then deleted. Only the platform owner and admins see them; the event's own team is not counted. We also count per day how often the buttons and links of an event page are tapped, with nothing about you: only the event, the button, where it stands and the number. Our legitimate interest is to improve AcroSpot and the events on it; you can object at any time by email, and we then delete your visits.
We count per day how often the app is installed, with nothing about you and nothing stored on your device: only whether it was installed in Solar or Lunar mode, the kind of device (Android, computer) and the number. Only the platform owner and the admins see the numbers. Our legitimate interest is to improve AcroSpot.
If you connect an assistant such as Claude to your account, we record each call it makes to AcroSpot: the time, your account, which tool it used, the organizer it named, how the call ended and how long it took. Never what you asked it or the words and names it searched for. It helps us run the connection and improve it. Only the platform owner and admins see it; it is kept for one year and deleted with your account.
A request you send with “Help & feedback” is stored as a chat with the AcroSpot team, which the platform team reads and answers. Only for “Problem with the website” the owner, the admins and the feedback address also get an email with your last steps from this record; the form says so.
Without an account you can report something or tell us what is missing. We store what you write and, only if you give it, your email address, so the team can answer you by email; when you later log in with that address, your request shows among your messages. To keep out spam bots, Vercel BotID checks your browser when you send, and we count sends per IP address for one hour.
Your login sessions store the IP address and browser they were started from, for security; expired sessions are deleted. When platform admins help you in the support view, the start with its reason and IP address and the end are recorded, like every change they make. Our hosting provider keeps technical server logs, including IP addresses, for a short time. When you ask for a login code on the login page, the browser, device and approximate place (from the IP address) you asked from are kept with it while it is valid (30 minutes) and deleted within about an hour and a half, so the button in the email can show them when it is opened on another device. When you confirm your email while registering for an event without an account, they are kept until you continue, at most one hour after you asked for the code, and deleted within about two and a half hours. When we send you a code by email, which of our mail providers sent it is noted with a fingerprint (hash) of your address, so that a code you ask for again goes through another provider; it is deleted within about an hour and a half after your last code.
AcroSpot only uses cookies it needs to work: your login, your language, the light or dark look, how many entries a list shows per page, short messages after an action and whether you have already seen an introduction. There are no analytics or advertising cookies. Long texts you type are also kept as a copy in your browser (local storage) until they are saved, so nothing is lost if the page crashes; this copy stays on your device.
We process your data to provide AcroSpot and carry out the contracts you make with organizers (GDPR Art. 6(1)(b)), because of our legitimate interest in a secure and well-working platform, in recommendations, in showing new profiles publicly and in showing people with a public profile in the participant lists of their events, both of which you can switch off at any time (Art. 6(1)(f)), to meet legal duties such as keeping accounting records (Art. 6(1)(c)), and with your consent for allergies (Art. 9(2)(a)) and the emails about events nearby (Art. 6(1)(a)). Under the FADP we follow the same purposes.
Organizers receive the registration details of their own events, as described above. We don't sell data. Our emails go out through Brevo, Mailjet or Resend, each email through one of them. These service providers process data for us or provide a part of the service:
Our data is stored in Europe: the database in Frankfurt, Germany, pictures and uploaded files in Western Europe. Some providers are based in the USA, the United Kingdom or Australia or can access data from there. Switzerland and the EU recognise the protection in the United Kingdom as adequate. For the USA we rely on the Swiss-US and EU-US Data Privacy Framework where the provider is certified, otherwise, like for Australia, on the EU Standard Contractual Clauses with the additions Swiss law asks.
Your account and profile are kept as long as you have the account; what you remove from your profile is deleted right away. Registrations, orders and payment records, including who registered for which event and when, and all other records are kept for 10 years: accounting law (Art. 958f of the Code of Obligations) requires it for payment records, and it lets us prove registrations and payments. This also applies after an account is deleted.
Exceptions: allergies in registrations are deleted 30 days after the event, the record of actions after 30 days, the record of errors after 90 days, the counted visits of event pages and the calls of a connected assistant after one year, and login sessions when they expire. Organizers keep what they downloaded under their own responsibility.
When your account is deleted, it disappears right away for everyone else and you are logged out. We keep your data for 90 more days so that you can get the account back by logging in again with your email address or Google, for example after a deletion by mistake, unless the platform team blocked that; you can also start fresh with a new account then. During this time only the platform owner and admins see it. Then we delete your personal data for good: name, email address, profile and teacher profile, pictures, login methods, payout details, settings, whom you follow, the content of your messages and the words and name of your event feedback. Your registrations, tickets and payments stay for the 10 years above, but from the deletion on organizers see them only under a made-up name such as "Deleted participant 4821", without your contact details, answers and allergies. If you paid for a registration, the platform owner and admins keep the name and email address you paid under with that payment record for these 10 years (accounting law); organizers don't see them.
You can ask for access to your data and a copy of it, have it corrected or deleted, restrict its processing, receive your data in a common, machine-readable format (data portability) and object to it, in particular to processing based on our legitimate interest. Write to info [at] acrospot.org; we answer within 30 days. You delete your account yourself in Settings → Security, or have it deleted by writing to us; for 90 days you get it back by logging in again (see "How long we keep data").
Where you gave your consent, you can withdraw it at any time, mostly with the same switch in the settings; this does not affect what was done before.
You can complain to a data protection authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC, edoeb.admin.ch), in the EU the authority of the country where you live or work.
AcroSpot is for people aged 18 or older; at sign-up you confirm that you are. Younger people take part in events only through a parent (see the terms of use).
When what we do with data changes, we update this notice and its date. We tell you by email about important changes.