Privacy Policy

When you create an account, we collect your email address, display name, and username. You may optionally provide a profile photo and a short bio. Your email address is used for authentication and is never shown to other users. Your display name and username are public.

If you provide a home city in Settings, we send that text to our geocoding service (Supabase Edge Function calling a map API) and store the resulting latitude and longitude in your account. We store these coordinates on our servers, not just on-device. They are used to find upcoming shows near you and to surface city-level stats on your profile. We do not collect or store real-time GPS location at any point.

We store every concert log you create, including the artist, venue, date, the headliner/support role, your tier rating (Life Changing / Solid Show / It Was Okay), your ranking score relative to other shows in that tier, any written notes, and the names of people you attended with. This is the core data that powers your personal history and ranked profile.

When you rate a venue, we store your scores for sound quality, atmosphere, sightlines, and crowd on a 1–5 scale. These are linked to your log and used to compute an aggregate venue rating shown on venue profiles.

Concerto’s core mechanic is ranking concerts. By ranking shows against each other and assigning them to genre buckets, you create an explicit record of your musical preferences. We store this ranked list and use it to:

• Show your ranked profile to other users (if your profile is public or to your followers)
• Power the TasteDNA feature, which derives your genre fingerprint from your ranked logs
• Personalise discovery recommendations (artists to check out, shows nearby that match your taste)

This is more personal than a listening history — it is an ordered preference ranking. We treat it as sensitive and do not sell it or share it with advertisers.

If you tap “I’m Going” on an upcoming show, we store that as an attendance record linked to your account. This information is used to show your friends which shows you plan to attend.

Photos you upload are stored in Supabase Storage (our database provider) on servers in the United States. Videos are uploaded to and streamed from Mux, a video infrastructure provider, also based in the United States. Videos are limited to 30 seconds. You can delete individual photos and videos at any time from the log edit screen, or delete all of them by deleting your account.

We store the follows, likes (Encores), comments, posts, and direct messages you create. We also store your block list and mute list so we can enforce those preferences on our servers.

To deliver push notifications, we store a push notification token issued by your device’s operating system. On iOS this is an APNs token; on Android it is a Firebase Cloud Messaging token. This token is a device identifier tied to your device and Concerto installation. It is used only to route notifications to you and is deleted when you delete your account or sign out.

If you use the “Find Friends from Contacts” feature, we request access to your device contacts. Phone numbers from your contacts are sent to our servers, where a server-side function compares them (as hashed values) against phone numbers registered on Concerto. We return only the public profiles of users who match. We do not store your contacts, do not build any contact graph, and do not use your contacts for any purpose other than this one matching operation. The data is discarded on the server after the query runs.

If you use the Spotify top artists import, we connect to the Spotify API using OAuth and receive your top artists list. We store your Spotify user ID in your Concerto account to manage this connection. We store the resulting artist records (artist names and genres) but do not continuously sync your Spotify listening history. You can disconnect Spotify at any time by contacting us.

If you import past shows from Setlist.fm using your Setlist.fm username, we fetch your public setlist history from Setlist.fm’s API and store the resulting concerts as past logs in your account. We store only what you explicitly approve importing; we do not continuously sync or retain your Setlist.fm username after the import is complete.

• Supabase — database, authentication, and file storage. Your account data, logs, posts, messages, and uploaded photos are stored on Supabase infrastructure in the United States. Supabase processes data on our behalf under a data processing agreement.
• Vercel — web hosting for getconcerto.app. Vercel may log standard web request metadata (IP addresses, user agents) as part of normal CDN operation.
• Mux — video hosting and streaming. Videos you upload are sent to and stored on Mux’s servers. Mux processes video data on our behalf.

• PostHog — product analytics. We send anonymous usage events to PostHog to understand how the app is being used. The events we track include: concert log created (including the tier and genre group of the log), log edited, log deleted, post shared, venue rating saved, import completed (source and counts only), artist/venue/user followed or unfollowed, comment posted, post liked, search performed (which tab was active), nearby shows viewed, and sign-in/sign-up/sign-out (method only). These events do not include post captions, comment text, message content, or personally identifying information. Events are associated with a random session identifier, not your email or name. PostHog servers are located in the United States.

• Sentry — error and crash monitoring. When the app encounters an error, we send a crash report to Sentry containing the error message, stack trace, and the sequence of actions (breadcrumbs) leading up to the error. Passwords, tokens, phone numbers, and authorization headers are automatically stripped from all Sentry reports before they leave your device. Error reports are associated with a random user identifier — not your email or name. We also capture a UI session replay (a representation of what was on screen) when an error occurs, to help us reproduce bugs; this replay may include UI elements you had visible at the time of the crash. Sentry captures performance traces for approximately 20% of app sessions (sampled randomly). Sentry is based in the United States.

• Mapbox — interactive maps for venue profiles and the passport screen. Map tile requests are made from your device and include the coordinates of the map area you are viewing. Mapbox may collect anonymized usage telemetry per their SDK terms. We do not send your personal information to Mapbox.

• Expo Push Service / Apple APNs / Google FCM — push notification delivery. We use Expo’s push notification gateway, which routes notifications through Apple’s APNs (iOS) or Google’s FCM (Android). These services receive your device push token and the notification content (title and body). They do not receive your email address or other account data.

• Apple Sign In — if you sign in with Apple, Apple authenticates you and sends us a verified identity token and, on first sign-in only, your name (if you choose to share it). If you chose to hide your email, Apple provides a private relay address instead. We use this only for authentication. We do not share your Concerto activity back to Apple. We store an Apple-issued refresh token in your account so we can revoke your Apple Sign In authorization when you delete your account, as required by Apple’s guidelines.
• Google Sign In — if you sign in with Google, Google authenticates you and sends us a verified identity token containing your Google user ID and email. We use this only for authentication. We do not share your Concerto activity back to Google.

• Spotify — artist images, genres, and (for the top-artists import) your top artists list. We send artist name searches and (for import) OAuth requests to Spotify. Your personal information is not sent to Spotify unless you explicitly connect your Spotify account via the import flow.
• Setlist.fm — historical setlist data. We query Setlist.fm by artist name and date. Your personal information is not sent to Setlist.fm unless you provide your Setlist.fm username for the import feature.
• Ticketmaster — upcoming event data. We query Ticketmaster by artist name and location (city coordinates). Your personal information is not sent to Ticketmaster.
• JamBase — upcoming show listings. We query JamBase by artist name. Your personal information is not sent to JamBase.
• Last.fm — artist genre data. Our server queries Last.fm to enrich artist genre information. This happens server-side; your device does not contact Last.fm.

We may disclose your information to law enforcement or other parties if required by applicable law, court order, or to protect the safety of our users or the public. We will tell you when we receive such a request if we are legally permitted to do so.

Under the California Consumer Privacy Act, California residents have the right to know what personal information we collect about them, to request deletion of that information, and to opt out of the “sale” of their personal information (we do not sell personal information). To exercise these rights, contact us at the address below. We do not discriminate against users who exercise their privacy rights.

If you are located in the European Economic Area, United Kingdom, or Switzerland, you have rights under the General Data Protection Regulation (or equivalent local law), including rights of access, rectification, erasure, restriction, portability, and objection. Our lawful basis for processing your data is the performance of a contract (providing the Concerto service) and, for analytics, our legitimate interest in improving the product. To exercise your rights or lodge a complaint, contact us at the address below.