Privacy Policy
Courtesy translation. This English version is provided for convenience only. The German version is the legally binding one.
1. Controller
The controller for data processing under the GDPR is:
MuCode, owner: Tobias WoydichKreittmayrstr. 7
80335 Munich
Germany
Email: support@mucode.de
Full provider identification: Legal Notice (German). There is no statutory obligation to appoint a data protection officer.
2. Principles
Bubbles is an app for meeting up in real life. Only the data needed to run it is collected. Nothing is passed on to advertisers, there are no advertising IDs, no profiling for advertising purposes and no third-party analytics SDKs.
3. This website (joinbubbles.app)
3.1 Hosting and server log files
The website is hosted by Cloudflare (Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA; represented in the EU by Cloudflare Germany GmbH, Rosental 7, 80331 Munich). Cloudflare processes the data as a processor under a contract pursuant to Art. 28 GDPR.
When a page is requested, technically necessary access data is processed:
- IP address of the requesting device
- date and time of the request
- the address requested and the amount of data transferred
- the server’s status response
- browser type and operating system (user agent), where transmitted
- the previously visited page (referrer), where transmitted
This processing is necessary to deliver the page, to keep operations secure and to fend off attacks. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in stable, secure operation). Access data is kept only briefly, usually a few days, and then deleted automatically; it is never evaluated for analytics or marketing.
Cloudflare runs a worldwide server network, so processing may also take place outside the EU. Cloudflare, Inc. is certified under the EU-US Data Privacy Framework, and standard contractual clauses under Art. 46(2)(c) GDPR are in place as an additional safeguard.
3.2 No cookies, no tracking, no external content
This website sets no cookies, uses no local storage and embeds no analytics, advertising or social media services. No JavaScript runs in your browser; the vibe link pages (3.4) are rendered on the server. Every resource, including the Nunito typeface, is served from our own server and never loaded from third parties, so no connection to Google Fonts is created. Consent under § 25 TDDDG is therefore not required, and there is no cookie banner.
3.3 Getting in touch by email
If you write to support@mucode.de, your sender address and the content of your message are processed in order to answer your request. The legal basis is Art. 6(1)(b) GDPR for enquiries relating to your use of the app, otherwise Art. 6(1)(f) GDPR (legitimate interest in responding). The address is forwarded to a private mailbox via Cloudflare Email Routing (processor, see 3.1); messages are not stored there permanently but deleted once the request has been dealt with and no retention obligations apply.
3.4 Vibe links and guest RSVPs (joinbubbles.app/v/…)
App users can share a vibe as a link (https://joinbubbles.app/v/…). Anyone who opens it sees a page with the host’s first name, the vibe text, the time window, the name of the meeting place (if one was given) and the number of people who have said yes — no profiles, no photos, no surnames, no coordinates. The host decides whether and with whom to share the link; anyone holding it can view the page while the vibe is active. Withdrawing the vibe invalidates the link immediately; for up to seven days afterwards the page only says that the vibe is over.
The page is delivered through Cloudflare Pages (see 3.1 for server logs) and rendered on the server from our database at Supabase (EU). No JavaScript runs in your browser and no cookies are set. To prevent abuse, the IP address of a request is used only as a salted SHA-256 checksum that changes daily, kept for at most 24 hours to limit request rates; it is never stored in plain text and never linked to an RSVP. We also count how often a link was opened (link previews generated by messengers count too); only the host sees that number.
Guest RSVP without an account: You can say yes on the page with a name of your choice (1–40 characters; a nickname is fine). We store only that name, the vibe and the time of your RSVP — no email address, no phone number, no IP address. The host sees the name in their guest list and receives a notification. The confirmation page (a link containing a random key valid for this one RSVP only) lets you withdraw again. The host can remove guests from the list at any time. Guest RSVPs are deleted as soon as the vibe is deleted, and at the latest 30 days after it ends. The legal basis is Art. 6(1)(b) GDPR (carrying out the RSVP you requested) and Art. 6(1)(f) GDPR for abuse prevention.
If you open a vibe link in the app and register within seven days, Bubbles remembers whose link brought you here and notifies that person. This does not create a friendship or join anything automatically. To report misuse of a link: support@mucode.de.
4. Minimum age
Using Bubbles requires a minimum age of 16. People under 16 may not use Bubbles; an account can only be created from age 16 (checked via the date of birth at sign-up). No data is knowingly collected from anyone under 16. If we learn of an account belonging to someone under 16, we delete it.
5. What data the app collects
5.1 Account data
- email address and password (stored encrypted)
- username and display name
- date of birth (age verification; you control whether your age is visible on your profile)
Sign in with Apple. If you sign in with your Apple ID, we receive from Apple an identifier, your name and your email address (or the relay address Apple generates if you hide your email). We also store an access token from Apple, which we use to end the link with Apple for you when you delete your account; Apple requires this of apps that offer Sign in with Apple. If you abandon registration after signing in, we remind you once by email and delete the incomplete account after 48 hours.
5.2 Profile data
- profile photo (optional, stored on Supabase Storage, EU)
- town / postcode (optional, for nearby search)
- interests and tags
- mood / status (optional)
Your profile photos are kept in file storage at Supabase (EU) under random file names that cannot be guessed. If your profile is private, only friends see your additional photos.
5.3 Social data
- friend connections
- community and group memberships
- bubbles: your private labels for friends (“bubbles”) — only you can see them; the people you label cannot
- visibility settings: who sees your age (everyone/friends/no one, default: friends), who sees your RSVPs, and whether your profile is private (non-friends then see only your photo, name, age and shared interests)
- invitation source: if you come to Bubbles through an invitation link, we store for up to 7 days which link you came through and notify the person who invited you
- blocks and reports (see 5.8)
Search and profile links. If you find a person through a search (nearby, by name or by phone number) or open their profile through a link or QR code, we note against your account that you found this profile, so that you can open it during the following 24 hours. Only you and we can see this entry, not the person you found. It is deleted after 24 hours, at the latest during the following night.
5.4 Content
- vibes: activity signals with a category, a time window and optional free text — these expire automatically (<24 h)
- events: gatherings with attendee lists
- chat messages and reactions
- vibe links (optional): a random link code per shared vibe, the “opened” and “guests” counters and your guest list (see 3.4); deleted with the vibe, at the latest 30 days after it ends
What others see of you depends on what you share: vibes and events go only to the recipients you choose (All friends, individual bubbles, communities, or public). For events, hosts always see who has accepted; other attendees see RSVPs according to your visibility setting (5.3). If you answer “Maybe” with a condition, only the host sees the condition. Event crews are small groups within an event with their own chat; members can see each other. When you join a bubble or community, open event invitations from that group are added for you.
5.5 Communication and technical data
- phone number (optional; only if you switch on being found by phone number — we store the number and a SHA-256 checksum of it; it is used only so that someone who enters your number in “Add friends” can find you; the entered number is compared with yours as a checksum)
- push notification token (for notifications, revocable)
- read status of messages and notifications
We send notifications through Expo’s push service to Apple (APNs), which delivers them to your device. In the process, your device’s push token and the text of the notification (for example the vibe text or the name of the person inviting you) leave our servers for Expo and Apple (see section 8). Push is optional: the app only asks once a notification would be useful to you, and you can switch it off at any time in your iOS settings; the app works without it.
5.6 Location and places
Your location. For nearby results and the map, the app may use your location, only while you are using it (iOS permission “While Using the App”, revocable at any time). Your exact position never leaves your device. The app converts it on the device to a grid cell of about 500 metres and uses only the centre of that cell: to query what is happening near you, and as the rounded coordinate of your profile from which your radius is derived. We never store your location more precisely than this cell. The only exception: if you deliberately choose your current location as the exact meeting place of a vibe or event with “My location”, that place is stored as the meeting place (see below). Without location permission, the app uses the postcode or town you choose in your profile instead. Postcodes are mapped to towns and coordinates in our own database, built from the open GeoNames dataset (CC BY 4.0); what you type into the place search is never sent to a third party.
Finding people near you. Under “Add friends → Nearby” you can search for profiles in your area. Only people who have switched on “Profile discoverable” in their profile are found; you yourself appear to others only if you switch on “Profile discoverable”. If you have given the app location permission, your device sends the centre of your location cell (a grid of roughly 500 metres, never your exact position) to our server for this search; the server uses it to calculate the distance to discoverable profiles and does not store your coordinate. Without permission, the search is centred on the town you entered in your profile. Shown are name, profile photo with badge, town, the distance in whole kilometres and, if you have switched it on, the note “Open to new contacts”; you never see other people’s position more precisely than the location stored in their profile, rounded to about one kilometre. To protect profiles from being harvested, we count per account how often a search is run (at most 30 searches per hour and 120 per day); for this we store only timestamps without any location; they are deleted after 24 hours, at the latest during the following night.
Meeting places. When you create a vibe or event with a place, we store that meeting place as part of the content (see 5.4): type of place, name or address, and coordinates. This is not where you are, but where the meet-up takes place. Who sees the exact meeting place depends on how it is shared: recipients of your private vibes and events see it straight away; for public and community events, attendees see it once they have accepted, or everyone does if you explicitly release the place; everyone else sees only a rough area (cell or town). If you block someone, that person no longer sees the place. Places you save as favourites in the app are stored with your account.
Map. The map shows meet-ups, not people: meeting places appear as circles or markers, never the position of other people and never your own beyond the cell.
The legal basis is Art. 6(1)(b) GDPR (providing nearby results, people search, map and meeting place); granting location permission is itself voluntary. The search counter is based on our legitimate interest in protecting discoverable profiles (Art. 6(1)(f) GDPR).
5.7 Contacts and address book
Bubbles does not access your address book and does not match contacts. The app never asks for permission to read your contacts. You choose whom to invite yourself: you share an invitation link through the iOS share sheet; the recipients are picked in the app you use for sharing and never reach us. Should we offer contact matching later, we will describe it here first and ask for your consent.
5.8 Reporting, blocking and community rules
You can report people, vibes, events and communities in the app. We store your account as the reporter, the reported account or content, the reason you chose and an optional free-text note. Only the operator reads reports; the reported person never learns who reported them. Reports are deleted automatically after 180 days. Content you report is hidden for you; that list lives on your device only. If you block someone, the block is stored for as long as it exists; the blocked person is not notified. The legal basis is Art. 6(1)(f) GDPR (protecting other users, keeping the service safe) and, where reporting is part of the agreed use of the app, Art. 6(1)(b) GDPR.
When you register you accept the community rules; the time of your acceptance is stored in your profile so that we can show you a revised version once for renewed acceptance. The rules are available in the app under Settings → About. Complaints about content: support@mucode.de.
Reports are handled under the notice and action mechanism of the Digital Services Act (Art. 16 DSA): you briefly describe what breaks the law or the community rules and confirm that you are reporting in good faith. You receive a confirmation of receipt in the app and later our decision, with information on how you can challenge it. Anyone affected by a measure (content removed, account suspended) receives a statement of reasons (Art. 17 DSA). For this we store, with the report, the time of your confirmation and the notices sent. You can also report content without an account: by email to support@mucode.de (for what to include, see joinbubbles.app/en/support). We usually review reports within 48 hours.
Protection against misuse. So that no one can flood others with requests, search profiles in bulk or swamp the reporting function, we limit per account how often certain actions are possible in an hour and in a day: friend requests, reports, searching for people by name or phone number, and opening profiles through a link. For this we store against your account only the type and time of each action — not whom you sent a request to, what you reported or what you searched for. These counter entries are deleted after 24 hours, at the latest during the following night. Which profiles a search found is described separately in 5.3. If you reach the limit for reports, you can still tell us what you noticed by email to support@mucode.de. The legal basis is Art. 6(1)(f) GDPR (protecting users and the service).
5.9 Error and diagnostic data
To find bugs and make the app faster, the app sends technical data to our database at Supabase (EU): error reports (which app feature was affected and what kind of error occurred) as well as loading times and the number of server requests at launch and when switching tabs, at most twice per app session. Error reports and measurements contain no message or vibe texts and no identifiers of other people, but may contain the technical identifier of the event, vibe or chat concerned; they are linked to your account ID and are deleted after 30 days. We store the app version, update level and iOS version of your device once per account, until you delete it. The legal basis is our legitimate interest in a stable and fast app (Art. 6(1)(f) GDPR); you can object to this processing (section 9).
5.10 Tom (automatic tips)
“Tom” is not a person but a companion in the app, written by us: he sends you prepared messages in chat, for example when you start, after your first vibe or while you still have few friends. To do this, our server evaluates how far you have got in the app (such as the number of your friendships, whether you have sent a vibe yet) and when which Tom message was sent to you. There is no language model: in the chat with Tom you only pick from prepared replies, you cannot write free messages to Tom, and no one reads along. To send feedback, use “Send feedback” (see 5.11). The legal basis is Art. 6(1)(b) GDPR (helping you get started in the app) and Art. 6(1)(f) for reminders; you can mute Tom’s notifications on his profile; his messages then still appear in chat, just without a push.
5.11 Feedback
If you send us feedback from the app, your text goes by email (via Resend, see section 8) to the operator together with your username and account ID, the category you chose, app version, operating system version, language and time; your email address is not included. We also store the feedback in our database for 180 days. Resend keeps the email for 30 days; in our mailbox we delete it after 12 months at the latest. We use feedback only to improve the app. The legal basis is Art. 6(1)(f) GDPR (improving the app).
6. Purpose and legal basis
The data in section 5 is processed on the basis of Art. 6(1)(b) GDPR (performance of a contract) in order to provide the app’s functions. Push notifications are based on your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in your iOS settings. For vibe link pages, guest RSVPs, location, reports, error and diagnostic data, Tom and feedback, the legal bases stated in 3.4, 5.6 and 5.8 to 5.11 apply.
7. Retention
Your data is stored for as long as your account exists. After you delete your account, all personal data is erased within 30 days. Vibes expire automatically, and chat messages are deleted along with the chat they belong to. Vibe links and guest RSVPs are deleted at the latest 30 days after the vibe ends, IP checksums of the link pages after 24 hours (3.4). Reports are deleted after 180 days (5.8). Diagnostic data in our database is deleted after 30 days (5.9). Incomplete accounts after Sign in with Apple are deleted after 48 hours (5.1). People-search timestamps, the entries on profiles you found and the counter entries that protect against misuse are deleted after 24 hours, at the latest during the following night (5.3, 5.6, 5.8). Feedback is deleted from our database after 180 days, the related email at Resend after 30 days and in our mailbox after 12 months at the latest (5.11). Our hosting provider keeps daily backups of the database for 7 days. Before larger interventions we additionally make our own backups; they are stored encrypted on a device belonging to the operator, not in a cloud, and are deleted after 30 days at most.
8. Service providers and transfers to third countries
We use the following service providers to run the app. Where they process data on our behalf, a data processing agreement under Art. 28 GDPR is in place. Several providers, or their parent companies, are based in the USA; we base transfers there on the adequacy decision for the EU-US Data Privacy Framework (DPF) where the provider is certified, and additionally or otherwise on standard contractual clauses under Art. 46(2)(c) GDPR.
- Supabase Inc. (USA) — database, sign-in, file storage and server functions of the app. The data is located in the EU (Frankfurt). Processor; transfers to the USA (e.g. support, logs) on the basis of standard contractual clauses.
- Cloudflare, Inc. (USA) — hosting of this website, delivery of the vibe link pages, email forwarding (see section 3). Processor; DPF-certified, with standard contractual clauses in addition.
- Expo (650 Industries, Inc.) (USA) — delivery of push notifications to Apple (see 5.5) and distribution of app updates. For push, Expo receives your push token and the text of the notification; when updates are fetched, technical details of your device such as IP address and app version. DPF-certified, with standard contractual clauses in addition.
- Apple Inc. (USA) — delivery of push notifications through the Apple Push Notification service, Sign in with Apple if you use it (see 5.1), and the map in the app. Apple processes this data as a controller in its own right under its privacy policy and, by its own account, bases transfers to the USA on standard contractual clauses.
- Resend, Inc. (USA) — sending our emails to you (account confirmation, account deletion, replies to feedback). Resend receives your email address and the content of the message. Processor; DPF-certified, with standard contractual clauses in addition.
Nothing is passed on to advertisers. No third-party map or geocoding service is used for the place search (see 5.6); GeoNames is a data source, not a recipient of your data. The map in the app shows meeting places using the iOS map component (Apple Maps); Apple receives the map sections displayed, under Apple’s privacy policy, not your stored location.
Links to other services. In some places you can open another service from within the app: directions to a meeting place in Apple Maps, an event in Google Calendar, an Instagram profile, or the App Store. This only happens when you tap. The app then passes on what the service you open needs — for example the meeting place for directions, or the title, time, place and description of the event for the calendar entry. From that point the privacy policy of the respective provider applies.
9. Your rights
You have the right to:
- access the data stored about you (Art. 15 GDPR)
- have inaccurate data corrected (Art. 16 GDPR)
- erasure (Art. 17 GDPR) — in the app under Settings → Account
- restriction of processing (Art. 18 GDPR)
- data portability (Art. 20 GDPR)
- object to processing based on legitimate interests (Art. 21 GDPR)
- withdraw consent with effect for the future (Art. 7(3) GDPR)
To request access, rectification, restriction, portability or to object, email support@mucode.de; we reply within one month (Art. 12(3) GDPR). You can delete your account directly in the app.
You can also lodge a complaint with a data protection supervisory authority. The competent authority is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany.
10. Changes to this privacy policy
This privacy policy is updated whenever the processing changes. You will be informed about significant changes by in-app notification or email. The date of the latest version is shown at the top.
11. Contact
For privacy questions: support@mucode.de