LAST UPDATED 26 AUGUST 2026
Plursky is a festival companion app supporting EDC, ACL, and more. We try to collect the minimum personal data needed for the app to work, and we never sell it. This page explains exactly what gets stored, where, and why.
Account data. If you sign in (Apple or Spotify), our backend (Supabase) stores:
Your festival data. Tied to your account if signed in, otherwise stored only on this device:
Spotify data (only if you connect Spotify). We use Spotify's standard OAuth. Plursky reads:
Plursky writes to one of your Spotify playlists (named "Plursky" or "My EDC Lineup") only when you tap "BUILD MY PLAYLIST." Your Spotify access token lives in your browser's local storage — it never leaves your device except to talk directly to Spotify.
Location. If you open the Map tab and grant permission, your device's GPS coordinates are used only on the device to draw your dot on the venue map. Coordinates are never sent to our servers, never logged, never shared with anyone — not even your crew. One exception path, by your choice only: if you enable cloud backup for Moments, the photo/video files you back up are stored as captured, including any location metadata embedded in the file itself (see "Moments" below).
Crew & friends. If you join a crew using a 6-character code, the following is broadcast in real time to other crew members on the same code:
The crew code is a shared secret; treat it like a password.
Notifications. If you enable set reminders, Plursky schedules them locally in your browser. We do not run a push-notification server — no one at Plursky can send you a notification.
Moments: photos and videos you add. When you add photos or videos from your camera roll or camera to Memories, Plursky reads them — and the metadata embedded in them (capture time, and GPS coordinates if the file has them) — on your device only, to place each moment on the right set, stage, and night. Nothing uploads by itself. If you turn on backup ("Back up my weekend"), the files you back up are stored in our backend (Supabase) in a private bucket, as captured — including whatever metadata the file carries. Artist/setlist-matching runs on the device against festival data bundled with the app; the setlist lookups it may trigger send only an artist name and festival id, never anything about you.
Microphone & song recognition. Plursky only listens when you explicitly start Shazam ("CATCH THIS SONG" live listen, or identifying a song in a video you added). Recognition happens through Apple's Shazam service: an acoustic fingerprint (not a recording of your voice or the venue) is matched against Apple's catalog. We never receive or store the audio itself; we store only the result (song title + artist) and only for that moment.
Apple Music (only if you connect Apple Music). MusicKit runs on your device. Plursky reads your library's artists list and your storefront region — to match the lineup against your taste — and writes one or more playlists only when you tap the build button. Your Apple Music tokens live on your device; they never pass through our servers.
Plursky+ (paid features). Purchases are handled by Apple's App Store and RevenueCat. When you buy or restore Plursky+, RevenueCat stores a purchase identifier for your app install so we know what you're entitled to (backup of photos/videos is the Plus feature today). We never see, process, or store your card number, Apple ID payment details, or billing address. The app is otherwise free.
We share what's necessary with the following service providers, and nothing more:
We do not sell your data to anyone, ever.
Account data + saved sets stay in Supabase until you delete your account. Backed-up Moments media stays in its private bucket until you delete it in-app or delete your account, either of which removes it. Crew chat messages persist in Supabase indefinitely (because late joiners need to see the thread) — they aren't tied to your account, but they do carry your display name. Your live location is never stored, anywhere.
Inside the app: Me → Cloud account → DELETE ACCOUNT. This hard-deletes your auth record and your user_data row from our backend. Crew chat messages you've sent are not automatically removed because they belong to the crew thread; backed-up Moments media is deleted — the delete flow purges your media from its private bucket before removing your account. For crew messages, contact us and we'll purge them.
Plursky is not directed at children under 13. Most supported festivals are 18+ or 21+ events.
If we change this policy, we'll update the date at the top. Significant changes will be announced in-app.
Questions or deletion requests: hello@plursky.com.