Privacy.

LAST UPDATED 12 MAY 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.

What we collect

Account data. If you sign in with Apple or via an email magic link, our backend (Supabase) stores:

• The unique user ID assigned by Apple, or your email address.
• Your display name (only if you provide one).

Your festival data. Tied to your account if signed in, otherwise stored only on this device:

• The list of artist IDs you've saved.
• Free-text notes you write on an artist's page.
• Your local display name, crew code, and friend-share preferences.

Spotify data (only if you connect Spotify). We use Spotify's standard OAuth (PKCE). Plursky reads:

• Your top artists, followed artists, saved tracks, and recent listening — to match the EDC lineup against your taste.
• Your Spotify profile (display name, country, premium status, avatar) — shown only to you in-app.

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 in-browser 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.

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:

• Your display name, the stage you tap "GO LIVE" on, and a random per-device color.
• Your saved artist IDs (so the lineup can show "3 in your crew" badges).
• Any chat message you send in the crew thread — stored in Supabase, readable by anyone who holds the same crew 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.

What we don't collect

• No analytics SDKs, no Google Analytics, no Mixpanel, no anything similar.
• No advertising identifiers (IDFA, etc.). Plursky displays no ads.
• No payment data — Plursky is free.
• No browsing history outside the app.
• No microphone, no camera, no contacts, no health data.

Who we share data with

We share what's necessary with the following service providers, and nothing more:

• Supabase — hosts the backend database and the Sign in with Apple verification. supabase.com/privacy
• Spotify — only if you connect; data flows directly browser ↔ Spotify. spotify.com/legal/privacy-policy
• Apple — for Sign in with Apple identity tokens. apple.com/legal/privacy
• YouTube — fetched read-only for artist trailer thumbnails. policies.google.com/privacy

We do not sell your data to anyone, ever.

How long we keep it

Account data + saved sets stay in Supabase until you delete your account. 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. Location data is never stored, anywhere.

Deleting your account

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; contact us if you want them purged.

Children

Plursky is not directed at children under 13. Most supported festivals are 18+ or 21+ events.

Changes

If we change this policy, we'll update the date at the top. Significant changes will be announced in-app.

Contact

Questions or deletion requests: hello@plursky.com.