RaveLog ← Back

How RaveLog handles your data.

Last updated: May 2, 2026

RaveLog is built around a simple idea: your nights are yours. Almost everything you log — events, festivals, artists, ratings, photos, notes — stays on your iPhone or in your personal iCloud. We don't sell your data, we don't track you across the web, and we don't run third-party analytics in the app.

What stays on your device or in your iCloud

Logged nights, festivals, artists, venues, set ratings, ticket photos, and notes live in your local app database and (if you have iCloud sync turned on) in your private iCloud account using CloudKit. We don't have access to that data — only Apple does, under their privacy terms. Sync is between your own devices unless you explicitly invite a friend.

Sign in with Apple

RaveLog uses Sign in with Apple to identify you to other RaveLog users (so a friend can co-attend a night with you). We receive an opaque user identifier from Apple. We do not receive your email address unless you explicitly choose to share it.

Friends and shared nights

When you invite a friend or accept a co-attendance invite, your display name and the night/festival you're sharing are written to a CloudKit shared zone that only you and the people you invite can see. You can revoke access at any time from the app.

Music services (Apple Music, Spotify)

If you connect Apple Music or Spotify to import your top artists, the app reads your library or playlists with your permission and uses that information only to suggest artists to add to your RaveLog. The data is processed on your device and not sent to our servers.

Event discovery (EDMTrain)

Event discovery uses the public EDMTrain API. Your approximate location (if you grant permission) is sent to EDMTrain to find nearby events. EDMTrain's privacy policy applies to that request. If you don't grant location access, you can browse events by city manually.

Artist enrichment (Gemini, via our proxy)

When you tap into an artist for the first time, RaveLog asks Google's Gemini API for a short bio and metadata. The artist's name is sent through a Firebase Cloud Function that we operate. We don't log who asked, and we don't store the response on our servers — it's cached on your device.

Track metadata enrichment

If you use Track ID, RaveLog may look up matched track and artist metadata with MusicBrainz and Last.fm to improve album, genre, artwork, and release details. Those requests send the track and artist names or MusicBrainz identifiers needed for the lookup. Results are cached on your device.

Location

If you grant location access, RaveLog uses it locally for two things: finding nearby events when you open Discovery, and triggering an optional check-in prompt when you arrive at a venue. Location data is not sent to our servers and is never shared with anyone.

Notifications

Most notifications are scheduled and delivered locally on your device for things like set reminders, rating prompts, and recap prompts. If you start a Live Activity for a festival schedule, RaveLog may send the Live Activity push token and the schedule transition times to a Firebase Cloud Function we operate so APNs can update the Live Activity while the app is suspended. We use that token only for the active Live Activity, and stale Live Activity records are cleaned up automatically.

Sharing nights and festivals

When you share a night or festival from RaveLog (via iMessage, AirDrop, Mail, etc.), the recipient gets a link or file that contains the data you chose to share — name, dates, venue, lineup, and any notes you wrote. If you don't want a piece of information shared, edit it out before sharing.

What we don't do

Children

RaveLog is not directed at children under 13. If you're a parent and believe your child has used the app without your consent, contact us and we'll help.

Changes to this policy

If we make material changes, we'll update the date at the top and surface the change in the app's release notes.

Contact

Questions, requests, or anything else: jaguirre2192@gmail.com.