Privacy Policy

Last updated: 2026-09-29

MusicalMap (“MusicalMap”, “we”) is an independently run interactive map of musicals around the world, available as a website (themusicalmap.com) and as the iOS app “MusicalMap” (the “app”). The website and the app share the same account and data. This policy explains what we collect and how we use and keep it.

1. Browsing without an account

You can browse the map, search shows, view show details and open ticket links without an account, on both the website and the app.

• Website. The website is a static site hosted on Cloudflare Pages; we place no advertising trackers. We use Cloudflare Web Analytics (cookie-free) and Google Analytics to measure traffic and understand how the site is used; Cloudflare, as the host, may record standard server logs (such as IP addresses) under its own policies.
• iOS app. The app contains no analytics, advertising or tracking tools. It does not use the advertising identifier (IDFA) and does not track you across other companies’ apps or websites. To show the map, the app downloads the same public show data as the website from our servers on Cloudflare, which may record standard server logs (such as IP addresses) under Cloudflare’s own policies.
• App update checks. Each time the app starts, it checks with Expo (the app-update service we use) for a newer version of the app’s content. The request includes the app version and a random identifier created when the app was installed; this identifier contains no name, email or account data, and we use it only to deliver app updates. Expo may log standard connection data (such as IP addresses) under its own policies.

2. Footprints — optional sign-in

Recording the musicals you’ve seen requires signing in with Sign in with Apple (app only), Google, or your email plus a 6-digit code we send you. Once you sign in, we collect and keep:

• Basic account data: email, name and profile picture. With Google, these come from Google OAuth. With Sign in with Apple, we only receive the email you choose to share; if you choose “Hide My Email”, it is an Apple relay address and we never see your real address. With an email code, we only have your email. Your name is set by you and is optional; there is no profile picture except with Google. Your profile picture is visible only to you and never appears on your share page or anywhere others can see.
• The show records you add: title, venue, date, rating, ticket price, seat, notes and anything else you enter.
• Your share page: your share page is private by default; nobody can see it until you turn it public. The first time you make it public, we create a personal URL from your name (my.themusicalmap.com/…; for example, Candy becomes candy, with numbers added if it’s already taken), which you can change later. After you change your name or URL, your old URL stays reserved for you and is never given to anyone else, but it no longer opens your share page.
• What your share page shows: once public, visitors can see your name, and each show’s title, venue, city, date, rating and favorites; if you haven’t set a name, the title shows “Mystery Theatregoer”. Ticket price, seat and notes each have their own switch and are hidden by default until you turn them on in your share page settings.

This data is stored in Supabase (a Postgres database) and protected with Row-Level Security, so only you can access your own records. We never sell or trade your personal data.

If you previously used MusicalMap with a different sign-in method, the app can help you find that account and, at your request, merge its records into the account you are signed in with.

We may occasionally email you about major new features or service changes that affect your account; every such email includes a way to unsubscribe, and you can also opt out by writing to us. Beyond that, we never use your email for third-party advertising, and never share it with anyone.

3. Permissions and data on your device (iOS app)

• Location. Only when you tap the “locate” button, the app asks for permission to use your location while the app is in use, and uses it once to move the map to where you are. Your location stays on your device — it is never uploaded, stored or shared. If you decline, everything else works normally.
• Photos. You can attach your own photos (for example a curtain-call photo or a ticket stub) to a show record. You pick them with the system photo picker; they are saved only inside the app on your device. They are never uploaded to our servers, and they do not appear on the website or on your share page. Deleting the app removes them.
• Sharing. When you tap Share, the app opens the iOS share sheet and you decide who to send it to and with which app; the app never sends anything by itself.
• Stored on your device. The app keeps your sign-in session in the iOS Keychain, and stores your language setting, a cache of show data and a cache of poster images on your device so it opens faster and works offline.

4. Cookies and local storage (website)

After you sign in on the website, Supabase keeps your session in cookies / browser local storage. Google Analytics sets analytics cookies to distinguish visitors (anonymous traffic measurement, not advertising). The website itself places no advertising cookies. The iOS app does not use cookies for sign-in (see section 3).

5. Maps, street view and images

• In the app, maps are provided by Apple Maps. When you view street-level imagery we first use Apple’s Look Around; where it is not available, we open Google Maps Street View in your browser. Apple’s and Google’s own privacy policies apply to those services.
• On the website, map tiles are provided by Mapbox (with OpenStreetMap data), and Google Maps Street View is loaded only when you open street view. The website also loads fonts and open-source libraries from public CDNs (Google Fonts, unpkg, jsDelivr). When your browser fetches from these services, they receive standard connection information (such as your IP address) and handle it under their own privacy policies.
• Show posters are loaded from their original public sources (such as official ticketing or theatre sites) and may be cached on your device.

6. Ticket links and affiliates

Ticket links lead to third-party ticketing platforms (such as Ticketmaster or ATG), opened in your browser or in the platform’s own app. Some may be affiliate links — when you click or buy, MusicalMap may earn a small commission through affiliate networks (currently Impact and Sovrn), at no extra cost to you. After you click, the ticketing platform or network may set cookies in your browser under its own policies; their data practices are governed by their own privacy policies and are outside our control. We do not sell anything inside the app.

7. Crash reports

If you installed the app through TestFlight or the App Store and allowed sharing with app developers in your device settings, Apple may share crash reports and basic usage statistics with us. We use them only to fix problems.

8. Third parties

Ticketing sites, official theatre sites, maps and other pages you reach from MusicalMap each have their own privacy policies and terms. We are not responsible for third-party content or data practices.

9. Your rights

• You can edit or delete individual records at any time in Footprints on the website or in the app.
• You can change your name and share page URL and turn your public share page and each field on or off: on the website in Account settings, and in the app under Settings → Share page.
• You can delete your whole account yourself: on the website in Account settings, and in the app under Settings → Account → Delete account. This deletes all your records, your share page and your URL, and cannot be undone.
• If you signed in with Google, you can also revoke our access in your Google Account settings; if you signed in with Apple, you can stop using Sign in with Apple for MusicalMap in your Apple Account settings.

Questions? Email contact@themusicalmap.com.

10. Children

MusicalMap is not directed at minors and does not knowingly collect children’s personal data.

11. Changes

This policy may be updated from time to time; changes are reflected in the “Last updated” date at the top of this page.