Privacy

How RaveLog handles your data.

Last updated: October 3, 2026

RaveLog is provided by Infinity Machine LLC and is built around a simple idea: your nights are yours. Core records begin on your device. The iPhone app can use your personal iCloud, while the Android app can use Google Firebase when you choose to sign in or use a connected feature. We don't sell your data, track you across the web, or run third-party advertising analytics in the app.

iPhone storage and 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.

Android storage, Firebase, and Google services

On Android, logged nights, festivals, artists, venues, ratings, Track IDs, and settings are stored in RaveLog's local database first. If you sign in with Google and enable connected features, RaveLog uses Firebase Authentication to identify the account and Cloud Firestore to provide account, profile, social, and supported sync features. Firebase Cloud Messaging processes an app installation token when push notifications are enabled. Google Play services may also process location requests that you initiate in the Android app. Google's privacy terms apply to Google's processing.

You can use the core Android logging experience without signing in. Local-only records remain on that device unless you export them. Clearing RaveLog's app storage or uninstalling the app removes local-only records from that device.

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 on iPhone

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.

Sign in with Google on Android

If you choose Google sign-in on Android, Google's Credential Manager provides an identity token to Firebase Authentication. RaveLog receives your Firebase user identifier and the basic profile information you authorize, such as your display name and email address. RaveLog uses that account to enable supported sync, social, and push features. You can sign out in the app and can delete the account in Settings or through the web account-deletion pathway.

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 information

On iPhone, RaveLog can retrieve artist images, genres, and biographies from Apple Music. If Apple Music doesn't provide a biography, RaveLog may look up the artist through MusicBrainz and Wikipedia. Those services receive the artist name or catalog identifier needed for the lookup; results are cached on your device.

RaveLog-operated festival schedule services

Some RaveLog-operated server jobs use Google's Gemini API to discover festivals and extract set times from public webpages, including URLs selected by the RaveLog operator. These jobs process public festival information and do not receive your poster images, recognized poster text, account information, or personal library.

Festival lineup parsing on iPhone and Android

On iPhone, Apple's Vision framework reads a lineup photo on your device, and RaveLog prepares names for you to review before saving. The original photo and full OCR output are not sent to our servers or to Google's Gemini for lineup extraction. After a photo import is reviewed and saved, confirmed or removed artist rows and accepted name corrections may be sent to our Firebase service when poster sharing is on, as described below. If you import a lineup from a web page, RaveLog retrieves the URL you provide and processes the available page text on your device.

On Android, Google ML Kit reads lineup images on the device. The Android app does not send the image or its recognized text to Gemini or another generative-AI service.

Shared poster-learning contributions on iPhone

After you review and save a poster import, RaveLog records confirmed artist names, rows you remove, and corrections you make. Sharing those examples with a RaveLog-operated Firebase service is on by default and can be turned off in Settings under Data & Privacy. When sharing is on, the examples are sent with a pseudonymous installation hash so that you can request removal of that installation's contributions. Poster images, festival names, event dates, and account identifiers are not included. We use the examples to build a shared model from aggregate word counts and spelling corrections. Raw examples are retained for about 30 days and then deleted. The shared model refreshes daily. When you turn sharing off, RaveLog stops future uploads and requests deletion of that installation's stored examples; each of your devices processes that removal when Data & Privacy next opens.

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.

Microphone and Track ID on Android

The current Android release does not include live Track ID, does not ask for microphone permission, and does not record or transmit audio.

Location

If you grant location access, RaveLog uses it for nearby event discovery and optional venue-arrival features. On iPhone, Apple location services perform the device lookup; on Android, Google Play services perform the device lookup. RaveLog may send the resulting city, region, country, or coordinates needed for the event-discovery request through RaveLog-operated services. RaveLog does not use location for advertising or sell it to data brokers. The current Android release does not request Android's background location permission; venue features operate only within the permissions shown by Android. On Android, precise coordinates remain on the device; only the derived city and state are sent to EDMtrain for event discovery.

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.

On Android, Firebase Cloud Messaging processes an installation token and message-routing information for enabled push categories such as set reminders, friend requests, invitations, and festival updates. The app uses the token only to deliver RaveLog notifications to that installation.

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 require an account for core local logging on Android.
We don't use microphone or location data for advertising.

Deleting an account

Android users can delete an account from RaveLog's Account settings or request deletion at ravelog.net/delete-account. That page explains what is deleted, what may remain locally on a device, and the limited records that may be retained for security or legal reasons.

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: support@ravelog.net.