Privacy
DRAFT, to be checked before publication
This text describes the app as it is coded, but it is not legal advice.
Last updated: November 2026
This policy covers the jammap.org website and the Jam Map app (Android, then iPhone). Jam Map shows you musicians nearby without ever showing where you are exactly. We don’t sell data, show ads or track you.
1. Controller
Juliette Grieneisen, Schützenstrasse 34, 8280 Kreuzlingen, Switzerland. Email: contact@jammap.org
This policy follows the Swiss Federal Act on Data Protection (FADP) and, for users in the EU, the GDPR.
2. The website
The website is served by Cloudflare (Cloudflare, Inc., USA). Cloudflare processes the technical data it needs, such as your IP address, to deliver the page and protect it from attacks. Legal basis: Art. 6(1)(f) GDPR (secure operation).
To count visits we use Cloudflare Web Analytics. It sets no cookies, stores nothing on your device and builds no profiles; we only see overall numbers (such as page views). Legal basis: Art. 6(1)(f) GDPR.
The website has no account, no form and no cookies. If you email us, we only use your address to reply.
3. Your account in the app
For an account we need your email address and a password. The password is only stored in hashed form. To confirm your address or reset your password, you get a code by email.
Jam Map is for people aged 18 and over. That’s why we ask for your date of birth.
Legal basis for everything the app needs to work: Art. 6(1)(b) GDPR (contract).
4. Your public profile
Other signed-in users can see the following, except people you blocked or who blocked you:
- your display name and age (calculated from your date of birth, which stays private)
- your gender if you gave it, your country, city and languages
- your instruments and level, styles, what you’re looking for, gear, whether you have a rehearsal room, your description
- your photo or drawn portrait
- your YouTube, Instagram or TikTok links if you added them
- the name of your zone (such as “Paradies, Konstanz”), which you can edit
5. Location
Jam Map never shows where you are exactly. Your phone rounds your position to a grid of about 1 km before anything is sent, and our server rounds it again to be safe. Only the centre of that square is stored.
You choose your zone by typing a neighborhood, street or city, or with GPS once. GPS is never required.
In “where I am” mode, your approximate zone is updated when you open the app, only if you granted location permission. There is no background tracking. After 72 hours without an update, your usual zone applies again.
You can hide from the map at any time, or show only your city centre instead of your neighborhood.
What you type is never received or stored by Jam Map. Your phone’s geocoder (Google’s on Android) turns it into coordinates. If you refuse location permission, only the typed text is sent to Photon, an OpenStreetMap search run by komoot GmbH (Germany).
6. Messages, groups, blocking and reporting
Messages are stored so that you and the other members of the conversation can read them. A group has a name and optionally a photo that any member can change.
When you block someone, we store it so that person can no longer see you or write to you.
When you report someone, we store the reason and your details. Only moderation reads reports.
7. Push notifications
If you allow notifications, we store your device’s push token and platform (Android or iOS). For each new message, the sender’s or group’s name and the message text go through Expo’s push service and Google’s Firebase Cloud Messaging (on iPhone: Apple) to your device. You can turn notifications off at any time in your phone’s settings.
8. Map and app updates
The map uses the Google Maps SDK. Your device loads map tiles directly from Google, which receives technical data such as your IP address. Google’s privacy policy applies.
On start, the app asks Expo whether there is a new version (EAS Update). Technical data such as IP address, platform and app version is sent.
9. Payment
Jam Map costs €9.99, once. Payment goes through Google Play (later Apple’s App Store). We never see your payment details. To know whether you paid, we use RevenueCat (RevenueCat, Inc., USA), which links the purchase status to an identifier of your account.
10. Service providers
These providers process data on our behalf or under their own responsibility:
- Supabase (database, sign-in, photos, chat): servers in the EU, Ireland (eu-west-1)
- Google: Google Maps SDK, the phone’s geocoder, Google Play, Firebase Cloud Messaging
- Expo (650 Industries, Inc., USA): push notifications and app updates
- komoot GmbH (Photon), only if you refuse location permission
- RevenueCat, Inc. (USA): purchase status
- Cloudflare, Inc. (USA): website and cookieless analytics
For providers in the USA, transfers rely on the EU-US and Swiss-US Data Privacy Framework or on standard contractual clauses.
11. How long we keep data
As long as your account exists. When you delete your account, your profile, photos, messages, zone, blocks, reports (sent by you and about you) and push tokens are deleted immediately. See the “Delete my account” page.
12. Your rights
You have the right of access, rectification, erasure, restriction, data portability and objection (Art. 25 ff. FADP, Art. 15 to 21 GDPR). You can withdraw consent at any time. Write to contact@jammap.org.
You can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC, www.edoeb.admin.ch) or, if you live in the EU, to the data protection authority of your country.
13. Changes
If the app changes, we update this policy. The version on this page applies.
Not verified in the code
We could not confirm these points in the app’s code. Clarify them before publishing:
- Whether the provider, based in Switzerland, must appoint a representative in the EU (Art. 27 GDPR), since the app also targets users in Germany.
- Whether there are database backups (depends on the Supabase plan) and how long deleted data stays in them.
- How long Supabase, Cloudflare and Expo keep their server logs (IP addresses).
- Whether the EAS Update check sends a device identifier.
- Payment with RevenueCat is not in the app yet: part 9 describes the plan.
- Which service sends the code emails (today Supabase itself, later our own SMTP server).
- Whether Expo, RevenueCat and Supabase are certified under the EU-US Data Privacy Framework or use standard clauses; data processing agreements (Art. 28 GDPR) with every provider.
- Exactly which data the Google Maps SDK sends to Google.
- A group photo set by someone before deleting their account stays the group’s photo.