Privacy

Short version: this is a gift to the playa, not a business. There are no ads, no third-party trackers, and nothing is sold or shared. The site does keep a small set of anonymous tallies of what gets opened — written out in full below — and none of them can be tied back to a person.

What gets counted

Two kinds of tally, and that is the whole list.

Per recording, in Released since the burn. How many times its link has been opened, and how many people hearted it. That is a tally on the recording, never on you. What gets sent is the link and the word “click” or “heart” — no account, no session, no cookie, no IP address, nothing that could be traced back to a person. The heart counts are shown publicly on each row, which is the point: they float the sets people actually want to the top. The open counts are not shown; only I can read those, and all they tell me is which sets to go looking for more of. The hearts you place also live in your own browser, and clearing your browser data removes them.

Across the rest of the site. A running count of which parts get used — a page load, a camp opened, a playlist opened, a filter switched on, a search term. Each one is a single number in a bucket, stamped with the hour on the server, with no column anywhere for a person: no user, no session ID, no cookie, no IP address, no browser fingerprint. Two visits an hour apart are indistinguishable from two different people, and one person's path through the site cannot be reconstructed from them, by me or by anyone else. Only I can read these, and they exist so I know which camps and features are worth the time.

Where a visit came from. Once per visit, one more count of the same kind: the name of the site or app that sent you (“instagram”, “google”), or the short tag on a link I shared (“?via=story”), or “direct”. Only that name, never the full address of the page you came from, and nothing about you. The tag is removed from the address bar as soon as the page opens.

What you type into search

This one changed in September 2026, and it is the only thing on the site that stores words a reader wrote, so it gets its own section. When you search, the words are counted the same way everything else is: the term, the hour, a number. No user, no session, no cookie, no IP address. Two people searching the same thing are one count of two, and there is no way to tell which search came from which visit, or which searches came from the same person.

A term is only counted once, when the search ends: you pick a result, press Enter, or leave the box. Half-typed words are not kept, and the same term from one visit is counted once. It is trimmed to 60 characters and lower-cased. Terms that matched nothing on the site are counted separately, because that list is the whole reason this exists: it is how I learn which camp, which DJ or which set people came looking for and did not find, which is what I go and add next.

Search here is a search of this site's own lineups and recordings, nothing more. Please do not type anything personal into it; it was not built to hold that, and nothing typed there is ever sold, shared or sent anywhere other than the counter described above.

If you never sign in

Nothing that identifies you reaches any server — only the anonymous tallies above, which add 1 to a counter and record nothing else. The lineups and links are baked into the page itself. The sets you heart, and which theme you picked, are saved in your own browser's local storage — on your device, readable only by this site, and gone the moment you clear your browser data. So is a count of how many times you pressed Listen, and on how many days, which is only used to decide whether to show you the small “give back” card. It never leaves your browser.

If you give back

Entirely optional. Pressing Give takes you to Stripe's own checkout page (or to PayPal or Venmo, if you pick those). They handle the payment under their own privacy policies; this site never sees your card or bank details. Like any payment, Stripe shows me the amount and the email you give it for the receipt. I use that only to say thank you if you write to me, and for nothing else.

When Stripe sends you back here, the site counts one gift, and which of the three amounts it was, in the same anonymous way as everything else. It does not record who gave.

The Give button also hands Stripe a short tag with the gift: the amount you picked, which button you pressed, and how this visit began (for example, a story link or a Google search). It lets me see which parts of the site lead to gifts. It says nothing about who you are, and it is kept only in this tab until you close it.

If you sign in with Google

Signing in is optional. Its only purpose is to let the same plan open on your phone and your laptop. When you do, this is what gets stored:

• Your email address and a user ID, from Google. Not your contacts, files, calendar or anything else — the app asks Google for the basic profile scopes and nothing more.
• The slots you hearted: camp, night, artist, time and location.

That lives in a Postgres database hosted by Supabase, with row-level security so your rows are readable only by your own logged-in session. Nobody else can query them, and there is no admin screen that lists them.

If you join the updates list

Also optional, and separate from signing in. Lineups keep getting confirmed right up to gate open, so you can leave an email address and get a note when a new camp lands.

• Only your email address is stored, with the date you confirmed it. No name, no IP address, no open tracking, no click tracking, no pixels.
• It is double opt-in: the address does nothing until you tap the link in the first email. If someone types your address in by mistake, ignoring that email is enough.
• The list is not readable by the app. It sits behind row-level security with no policies at all, so only the server-side function that sends the mail can see it. It is never exported, sold, or shared.
• Every email carries a one-tap unsubscribe link that needs no login. Sending goes through Resend, which handles the delivery.

You will get a note when a camp lineup is added, and nothing else — no digests, no reminders, nothing from anyone else, ever.

If you send in a set

The form asks for the link to your recording and where you played it. Your Instagram and your email are optional, and the email is used only to ask you about that set.

• Photos and video are optional too: up to three photos and one video per set. They go into private storage at Supabase that only Ron can open, and they are used for one thing: posting about your set on Playa Set Library’s social media, tagging you and the camp. They are only kept if you tick the box that says so.
• Want them taken down, from a post or from storage? Email ronkashani@gmail.com and they go.

What this site loads from elsewhere

• Google Fonts serves the typefaces, so Google sees the request for them.
• SoundCloud, YouTube and Mixcloud links are ordinary outbound links. Nothing auto-plays, so those sites hear nothing about you until you choose to click through.
• Playlists. When you open one of the playlists, SoundCloud’s own player loads inside the page, and SoundCloud handles what you play under its own privacy policy, cookies included. Nothing from SoundCloud loads until you open a playlist.
• The sign-in code is fetched from a public CDN only if you open the sign-in panel.
• Stripe, PayPal and Venmo are ordinary outbound links too. Nothing from them loads on this site until you press Give.

Deleting your data

For the browser-only copy: clear your site data, or un-heart everything. For the updates list: tap unsubscribe in any email. For an account, or to have the email row deleted outright rather than just marked unsubscribed, email ronkashani@gmail.com and it goes, permanently, no questions.

Changes

If this ever changes materially it will be because the app gained a feature, and it will say so here. The updates list will never be used for anything but new lineups.

Last updated 30 September 2026