Privacy notice
Last updated: 19 November 2026.
This notice explains which personal data the beets app and this website process, why, who can see it and how long we keep it. beets is for meeting professionals near you in person, so some data, like your profile, is meant to be seen by others.
1. Who is responsible
The data controllers are Salvatore Casalino and Natale Tornatora, who run beets together as joint controllers: we decide together why and how your data is processed. You can reach us at hello@beetsmeeting.com for any privacy question, and you can exercise your rights with either of us. If we set up a company to run beets, it will become the controller of your data: we'll tell you beforehand.
2. Without an account
You can look at the map, public meetups and the profiles of the people hosting them without an account. In that case we store nothing about you. If you have already given the app location permission, your phone's coordinates are used to find meetups nearby: they reach our servers and the map services (section 7) but are not stored.
3. What we process
- Account. Email and password (stored encrypted), or sign-in with Apple, Google or LinkedIn. From these services we receive first name, last name and email, and the provider may also send a link to your profile photo; we copy your name into your beets profile and, if you don't have a profile photo yet, a copy of that photo (you can change or remove it at any time). We also store the language you use in the app, to write notifications and emails to you in that language.
- Profile. What you choose to add: photo, role, company, city, one link (for example your website or LinkedIn profile), a short bio, what you're looking for, skills, sectors and work experience.
- City. After signing up you choose the city where you're available; if you're travelling you can set another one, for a day or until you're back. We store the city's name and its centre, never where you actually are. We keep it as long as you have an account; the trip city until the date you chose or until you return.
- beets code. Every profile has a map-shaped code, derived from the account's identifier: it contains no name, photo or other data about you. When you scan someone else's code, the camera images are read on your phone and are neither saved nor sent: only the sequence of numbers that was read reaches our servers, to find the profile.
- Meetups and activity. The meetups you create (title, description, date, place, photo, seats), the ones you join, your drafts, the people you follow and the meeting proposals you send or receive.
- Activity. What happens between you and other people on beets: profile visits (one a day per person), follows, beets (meeting requests) and their answers, joins and changes to meetups. After a beets is accepted, the two of you can send each other quick messages chosen from a fixed list (for example "Running a few minutes late"); there is no free-text chat. If a host removes you from a meetup, we keep that so you can't rejoin it.
- How your beets went. Two hours after a beets you accepted, we ask how it went ("Good", "So-so", "We didn't meet"). Your answer is private: the other person never sees it, only the beets team does, to understand how meetups go and to spot problems.
- Notifications. If you allow notifications, we store your phone's notification token, its system (iPhone or Android) and its language, to let you know about beets, quick messages, changes to your meetups, new followers, the end of your visibility on the map and, rarely, news from the beets team. You choose which ones in Profile → Settings → Notifications.
- Blocks and reports. The people you block, and the reports you send about people or meetups (reason and any details you add). The person reported is not told who reported them.
- Moderation. To keep the community safe, the photos and texts you publish on your profile and in your meetups (there are no chats) are checked automatically when you add or change them. If something breaks the rules we can remove it, send you a notice in the app or suspend your account for a limited time. We keep the notices, whether you have read them, and the outcome of the checks.
- Location. See section 4.
- Usage. The days you use the app and when you use "Show me" or "On my way" (not where you are), to count active people and see which features are used. Only our team sees them, as totals.
- App errors. When something goes wrong in the app (a request refused by our server, or a crash), the app sends us the error message, where it happened, the system and app version and, if you're signed in, your account, so we can fix it. Only our team sees them; they are kept on our servers at Supabase and deleted after 30 days.
- On your phone. The app keeps your sign-in session, a few preferences (such as the reminders you chose and the language) and a temporary copy of images on the device. Meetup reminders are local notifications scheduled on the phone.
We don't use third-party analytics, advertising or tracking tools, and we don't sell your data.
4. Location
The app uses your location only with your permission, and only in these cases:
- Map and search. To show meetups near you and suggest places. The coordinates are sent to run the search and are not stored.
- Creating a meetup without choosing a place. Your phone's position at that moment becomes the meetup's place, visible to anyone who can see the meetup.
- "Are you in another city?". Only if you've already granted the location permission: when you open the app, your phone compares your position with the city you chose. If you're far from it, the position is sent to the place search service (section 7) to find the name of the city you're in, and the app asks whether you want to appear there. We store only the city you confirm, never the position.
- "Show me" (people nearby). Only when you tap it: each tap saves your position at that moment once, rounded to about 200 metres, and it is never updated automatically. Only other people who have also tapped "Show me" can see it, together with your name, role and photo, for the time you choose in Profile → Settings (1, 3, 5 or 8 hours; 3 if you don't choose); then it is deleted, we let you know with a notification, and you have to tap again to be visible. "Hide me" deletes it straight away.
- "On my way". Only if you turn it on, for a meetup you're joining, from 30 minutes before to 30 minutes after the start. The app sends your position every 10 seconds: on Android also in the background, with a persistent notification; on iPhone only while the app is open. We keep only the latest position, rounded to about 50 metres within 2 km of the place; further away we store only the distance, rounded to 100 metres. Only the other participants of that meetup see it, and only during that window. Sharing stops when you arrive, when you stop it, when you leave the meetup or sign out, and in any case 30 minutes after the start: from then on nobody can see it, and the data is deleted by the next automatic clean-up.
5. Who sees your data
- Anyone, even without an account: public meetups (with place, photo and the initials of some participants) and the full profile of the person hosting them. Profile and meetup photos are published through links that anyone who has the link can open. When you share your profile or a meetup from the app, the link opens a page on our site that shows anyone your name, photo, role and city, or the meetup's title, day and time, city and host. Not your other profile details, never the exact place, and never private beets.
- People with a beets account: your profile, who you follow and who follows you, the meetups you join and the city you're in. On the map each city shows how many people are there and, when tapped, who they are (name, role and photo); people using "Show me" at that moment are marked "Here now", without their position. Anyone who scans your beets code opens your profile.
- Only the participants: private meetups that come from an accepted beets, and the activity of a meetup (who joined, changes).
- Only you and the other person: beets and your activity together. When you open someone's profile, they see that you visited it.
- Only you: your drafts.
A profile is made to be seen: add only what you want the people you meet to know.
6. Why, and on what legal basis
- To let you use beets (account, profile, city, meetups, messages, reminders, location search): necessary to provide the service you ask for (Art. 6(1)(b) GDPR).
- "Show me", "On my way" and notifications: your consent, which you give by turning them on (or allowing notifications) and withdraw by turning them off (Art. 6(1)(a)).
- Security and abuse prevention (for example limits on sign-in attempts): our legitimate interest (Art. 6(1)(f)).
- Content moderation (automatic and by our team), notices and suspensions: our legitimate interest in keeping the service safe, also required by the app stores (Art. 6(1)(f)).
7. Providers and outside services
- Supabase hosts the database, accounts, photos and activity, on servers in the European Union (Frankfurt, Germany). It acts as our data processor.
- Stadia Maps provides the map tiles (from OpenStreetMap data): your phone downloads the tiles for the area you're looking at, so Stadia Maps sees your IP address and that area.
- Photon (komoot) searches for places when you choose where to meet and for cities when you choose yours (or when the app checks whether you're in another city, section 4): it receives what you type and the position used for the search.
- Firebase Cloud Messaging (Google) and Apple Push Notification service deliver notifications to your phone: they receive the notification token and the text of the notification, which can include the first words of a message.
- Firebase Crashlytics (Google) receives a report when the app closes because of an error: what went wrong in the code, the phone model, the system and app version and an installation identifier, never your profile, messages or position. We use it, on the basis of our legitimate interest, only to fix bugs; the reports are deleted after 90 days.
- Aruba, which hosts our domain, website and mailbox, sends beets emails (codes, account and security emails, and beets or meetup emails when a notification can't reach your phone): it handles your email address and the text of the email. It acts as our data processor.
- OpenAI checks the photos and texts of profiles and meetups with its moderation service: it receives that content when you publish or change it. It acts as our data processor; under its API terms the content is not used to train its models and may be kept for up to 30 days to prevent abuse.
- Apple, Google and LinkedIn, only if you use them to sign in: they process your data under their own privacy policies.
- Links in profiles (websites, LinkedIn) open in your browser and are handled by whoever runs those sites.
Some of these providers may process data outside the European Union; in that case the transfer relies on the safeguards required by the GDPR, such as the standard contractual clauses.
8. How long we keep it
- Account, profile, meetups and activity: as long as you have an account.
- "Show me" position: for the time you chose (1 to 8 hours) from when you tap it, or less if you hide it or delete your account.
- "On my way" position: only the latest one, during the meetup window (section 4).
- Notification token: until you sign out on that phone, delete the app (the token stops working and we remove it) or delete your account. Notifications are deleted as soon as they are sent.
- App errors: 30 days.
- Reports: as long as needed to review them and handle any repeat cases; they are deleted together with the account of the person reported.
- Notices, suspensions and moderation checks: as long as you have an account. We keep a record of moderation decisions (what was done, when and by which administrator).
- When you delete your account we delete your profile, the meetups you host, your participations, messages, positions and photos. We keep your name and email for 30 days only to confirm the deletion if you contact us, then we delete them, also from the moderation record.
9. Phone permissions
- Location: for the uses in section 4. You can refuse it: the map then starts from a default city.
- Location in the background: only on Android, during "On my way".
- Camera and photos: to choose your profile photo and meetup photos, and to scan another person's beets code.
- Notifications: for activity notifications (messages, proposals, meetups, followers), meetup reminders and, on Android, the "On my way" notification.
You can change these permissions at any time in your phone's settings.
10. Your rights
You can ask to access, correct or delete your data, to restrict its processing, to receive a copy in a readable format (portability) or to object to processing based on legitimate interest, and you can withdraw your consent at any time. You can correct most data yourself from your profile in the app.
You can delete your account yourself in the app, in Profile → Settings → Delete account: everything is deleted straight away. To exercise the other rights, write to hello@beetsmeeting.com from the address you signed up with: we reply within 30 days. You can also complain to your data protection authority (in Italy, the Garante per la protezione dei dati personali).
11. Age
beets is for professional meetups and is meant for people aged 18 or over.
12. Changes
If we change this notice we update the date at the top; if the changes are significant we'll tell you in the app or by email.