Privacy

How RaveLog handles your data.

Last updated: July 31, 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 unless you explicitly enable one of the rating-sharing choices described below. 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. Except for the optional rating projections described below, sync is between your own devices unless you explicitly invite a friend.

Optional Crew rating averages

Artist ratings remain private by default. If you enable Share averages with Crew, RaveLog sends each accepted friend a recipient-encrypted snapshot containing a canonical artist identifier, your numeric average for that artist, how many completed sets contributed to it, and its update time. It does not include your individual set scores, artist names, event history, dates, venues, tags, notes, or photos. A Crew score is shown only after at least three friends contribute. Turning the setting off deletes your encrypted Crew snapshot and recipient copies.

RaveLog-wide rating contributions are not enabled in the current App Store release. Before that capability becomes available, this policy will be updated to describe the exact controls and data handling.

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

RaveLog uses CloudKit's public database for a searchable social profile (your display name and optional avatar), friend-request routing, and content-free social routing records. Those routing records can expose opaque user IDs, record type, sharing audience, and posting time. In the current app, the actual names, venues, artists, event identifiers, dates, festival details, schedules, and notes in friends-visible activity are encrypted separately for each authorized recipient; the public routing record does not contain that content. CloudKit co-attendance invitations are disabled; use RaveLog's direct festival share link or file when you want to send a plan to someone.

Older RaveLog versions wrote some social posts and co-attendance invite content to the public CloudKit database in plaintext for client-side filtering. This version stops creating those records, scrubs supported legacy activity when you update it, and retires legacy co-attendance records that your account owns. You can use Erase Cloud Social Data in Settings to delete records your account is permitted to delete. Records owned by another person may require that owner to remove them; RaveLog reports partial deletion failures instead of claiming they succeeded.

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 and Resident Advisor)

Event discovery uses the public EDMTrain API and approved factual listings from Resident Advisor. If you grant location permission, Apple Maps converts your precise location to a city and region on your device. RaveLog sends only that city, region, ISO country code, the requested date range, a result limit, and an ephemeral per-request identifier through RaveLog-operated services. Those services resolve EDMTrain's location identifier and request limited Resident Advisor event facts such as the title, date, venue, artists, attendance count, festival status, and canonical source URL. Release builds do not contact Resident Advisor directly. In this app version, your precise coordinates and a persistent install identifier are not sent through these event-discovery services. Earlier installed RaveLog versions may send latitude, longitude, and state through the EDMTrain proxy while users transition to the current version.

Live Resident Advisor lookup responses are not written to RaveLog's servers. RaveLog may maintain normalized public event listings that are not tied to any user. If you mark a listing Interested or import it, the factual event details and canonical source URLs are saved on your device and may sync through your private iCloud library. Ordinary service and security logs may process request metadata, provider outcome, result count, and request duration under our infrastructure providers' retention policies. The providers' own policies, including Resident Advisor's privacy policy, apply to their processing. If you don't grant location access, you can browse events by city manually.

Optional Signal Match learning uploads

Signal Match ranking and its local learning history stay on your device by default. If you explicitly choose Upload Aggregate Metrics, RaveLog sends summary counts, model versions, and ranking-quality measurements; that report has no install identifier. If you choose Upload Training Signals, RaveLog sends a pseudonymous install hash, app/build version, interaction labels, ranking context, and numeric fit features, plus the time each interaction was recorded so training can preserve sequence. Both uploads go to a Firebase service we operate and exclude event identifiers, event dates, cities, artist names, notes, and location. Uploaded reports and batches expire after 30 days. You can delete training batches associated with this install from the same Settings section. We use these signals only to evaluate and improve Signal Match.

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.

Festival lineup parsing

When you add a lineup photo, Apple's Vision framework reads the image on your device. The original photo is not uploaded. If AI-assisted parsing is available, RaveLog sends the resulting OCR text, the festival date context, and any artist names needed for matching through a Firebase Cloud Function that we operate to Google's Gemini API. When you import a lineup from a web page, stripped page text may be processed through the same service. The proxy does not save these requests or responses as profile or library data; ordinary service and security logs may process request metadata under our infrastructure providers' retention policies. If AI parsing is unavailable, RaveLog falls back to on-device parsing.

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: resolving your city for nearby events when you open Discovery, and triggering an optional check-in prompt when you arrive at a venue. In this app version, precise coordinates are not sent to RaveLog's servers or shared with friends. As described above, the resolved city and state pass through RaveLog's event-discovery services but are not saved as profile or library data. Earlier installed versions may send coordinates and state through the EDMTrain proxy during the transition.

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

We don't sell or rent your data.
We don't run third-party advertising or marketing analytics.
We don't have an account system separate from Sign in with Apple.
We don't read your nights or your friends list.

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.