What this reads, and what it shows.

Apple Music is read to build a taste profile: Replay, heavy rotation, loved songs, recent plays, and library artists. The profile is top artists, genres, how recent they are, and a mainstream-to-niche score.

Genres are enriched with MusicBrainz tags because Apple's own labels are coarse. We do not invent audio features. Danceability, energy, valence, and tempo are not collected and not computed.

A compare link shows a match, shared artist names, and one bridge track. It does not show the rest of the library. Album art is never placed on the share card. Playback, when Apple Music is connected, is the only place artwork would sit, and this milestone does not render it.

The match is music overlap: shared artists, including close neighbors, styles, and scene. A crew score leans on the weakest pair. No model writes either number. MusicBrainz genre tags stay off unless that source is explicitly enabled. Spotify, if it is ever connected, is display only for a few testers.

A profile can also hold photos, a short video, prompts, and lifestyle choices you type yourself. Those choices are not folded into the music percent. Other people see your age, not your birth date, and a verification badge, not the selfie or the ID. Dealbreakers for age, distance, and intent only hide people.

Crew members see each other's fit and the open spots. They do not see the rest of a library. If a friend bails, the ticket can be offered to someone still in that crew. That is a note inside the group, not a payment or a public resale.

Spotify is not connected. Its terms ban building profiles from listening data and ban sending that data to an AI model.

FestivalBuddies is for adults 18 and older. A phone number, a selfie, and an ID stay private. Other people can see a badge, not the image. Sharing plans with someone outside the crew can include one location, and that point expires. The checks themselves are not on screen in this build.

Without Supabase, profiles stay in a file on the machine running the app. With Supabase, row-level security keeps full snapshots off anonymous clients. The service role key stays on the server.