Last updated 5 October 2026
Cookie Policy
A service provided by Cody Morrison trading as Rhythm Revolt Records (ABN 13 399 505 837). PO Box 109, Zillmere QLD 4034, Australia.
1. What cookies are
Cookies are small text files a website stores in your browser. We use a small number of our own cookies to keep you logged in and to count visits and clicks on label pages. We don't use cookies to show you ads, and there are no advertising cookies on the droplr.fm marketing site.
2. Cookies droplr.fm sets
| Cookie | Purpose | Type | Lasts |
|---|---|---|---|
dfm_session | Keeps customers logged in to the dashboard. Only set when you log in. | Strictly necessary | 30 days |
dfm_anon | A random ID set when you first open a label's release, bio or link page (not on droplr.fm's own marketing or account pages). It connects a page view to a later click or pre-save, so the label can see which visits turned into pre-saves. It doesn't contain your name, email or IP address, and isn't shared with other sites. | Analytics (first-party) | 1 year |
dfm_src | Remembers which campaign link (for example an Instagram-specific link) brought you to a release, so the label can see which campaign worked. | Analytics (first-party) | 30 days |
All droplr.fm cookies are HTTP-only, so scripts on the page can't read them. They're only sent to droplr.fm or the label's custom domain.
3. Label pixels on public pages
Labels on paid plans can add their own tracking pixels to their public release pages:
- Meta Pixel (Facebook and Instagram ads). See Meta's Privacy Policy.
- TikTok Pixel. See TikTok's Privacy Policy.
- Google Analytics 4. See Google's Privacy Policy.
When a label has added one, that company's script loads on the label's page. It may set its own cookies (such as _fbp, _ttp or _ga) and receive information about your visit and which button you clicked, which the label uses to measure and target its ads. The label and that company are responsible for that data, not droplr.fm. No pixel ever loads on the droplr.fm dashboard or marketing site. The only third-party content on either is an embedded video player — in the dashboard, and on a news post on this site — and in both the player loads only once you press play on it. See Embedded video.
4. If you're a label using pixels
Privacy laws in some places, including the EU, UK and parts of the US, require notice and sometimes prior consent before advertising or analytics pixels run. If you add pixels, you're responsible for meeting those requirements for your audience, as set out in the Terms. If you aren't sure, leave pixels off for campaigns aimed at those regions.
5. Embedded video
Some pages show a video that is hosted on YouTube: the "Watch the guide" cards in your dashboard, the news posts on this site, videos an artist or label adds to their bio page, and remix contest entries on a public release page where the entrant's track allows a player.
- A guide card, and the player on a news post, show a still picture and a play button. The player — and anything it stores — only loads when you press play. Until then nothing from Google runs on the page, though the still picture itself is fetched from YouTube's image servers, which is a request for a picture and sets no cookies.
- A video on a bio page works like a guide card, with one difference: its still picture is a copy stored on droplr.fm, so nothing at all is fetched from Google until you press play.
- We load those players from
youtube-nocookie.com. Google describes this as not setting cookies used to build an advertising profile from a video you watch. It is not the same as setting nothing: Google still receives the request, and it may store something in your browser for playback itself. - A contest entry's player loads as you scroll to it rather than on a click, so on those pages the connection happens without one.
Blocking third-party content in your browser, or using a content blocker, stops these loading. Everything else on the page keeps working.
6. The installed app and notifications
If you add droplr.fm to your phone's home screen, your browser also stores things that aren't cookies:
- A service worker and a small cache, so the app opens quickly.
- A push subscription, if you turn notifications on. That's an address at your device's push service plus the keys used to encrypt messages to it. We store it against your login so we can send you notifications, and delete it when you turn them off.
Removing the app from your home screen, or clearing site data in your browser, clears these. None of it is used for advertising, and none of it runs on the public release or bio pages fans see.
7. Controlling cookies
- You can block or delete cookies in your browser settings. Blocking
dfm_sessionmeans you can't log in. Blocking the analytics cookies doesn't stop links or pre-saves working. - Many browsers block third-party tracking by default. You can also use Meta ad preferences, Google ad settings and the Google Analytics opt-out add-on.
Questions: privacy@droplr.fm.
Questions about this document? Email privacy@droplr.fm. All contacts are on the Legal page.