Privacy Policy
Privacy Overview
We use cookies for functionality, analytics, and ads where permitted.
AdSense Notice
Third‑party vendors, including Google, use cookies to serve ads based on your visits to this and other sites. Google’s use of advertising cookies enables it and its partners to serve ads based on your visit to our site and/or other sites on the Internet.
Opt‑out options: Google Ads Settings or industry choices at AboutAds.
Your Choices
- Use the consent banner (EEA/UK)
- Clear/block cookies in your browser
- Contact us with questions
Updated Oct 01, 2025
Consent & Regional Controls
For visitors in the EEA/UK, a consent banner appears on first load. You can revisit choices anytime via the banner’s ‘Privacy’ link or your browser controls.
Data We Touch (By Category)
- Essential: page loads, navigation, basic preferences.
- Analytics: aggregate traffic patterns to improve layout and content.
- Advertising: ad delivery, measurement, and (where permitted) personalization.
Your Data Rights
- Access/Deletion: email everydayroyalties@gmail.com using the subject ‘Privacy Request’.
- Consent changes: use the banner (EEA/UK) or your browser’s cookie settings.
- Do‑Not‑Track: browsers vary; we honor platform‑level controls where applicable.
Retention
- Analytics event data: kept only as long as needed for trend analysis.
- Server logs (if present): short retention for security and troubleshooting.
Third‑Party Vendors
We rely on widely used providers for ads and analytics. Their policies apply when they process data. See Google’s documentation for Ads and Analytics.
Updated Oct 01, 2025
How this site relates to your listening platforms
This site doesn't connect to your streaming accounts or pull in your listening history. Any playlists you build or songs you search here are things you choose to take back into your own apps.
- No automatic integrations. We don't auto-link to or log what you play on Spotify, Apple Music, or any other service.
- Manual sharing only. If you decide to recreate a playlist based on ideas from this site, that happens inside your own accounts.
- Local reflection. Use the prompts and breakdowns here as inspiration, not as a tracking system.
You stay in control of where your listening data lives and who, if anyone, gets to see it.
If you reach out, what we actually do with your message
When you send feedback or recommendations, you're sharing your perspective and time. That deserves careful handling.
- Use limited to replies and improvements. Messages are used to respond to you and to guide content ideas, not to build marketing databases.
- No selling your contact info. Your email address or name isn't packaged or sold to third parties.
- Clean exits. If future features ever include newsletters or updates, opting out should be simple and respected.
You should be able to share what slow jams mean to you without worrying about your inbox getting overwhelmed later.
What typical web logs might include when you browse
Like most sites, basic technical information may be generated when you visit, even if you never type anything into a form.
- Standard requests. Your browser sends details like the type of device, operating system, and which page you asked to load.
- Approximate timing. Servers may record when a visit happened and how long certain pages took to respond.
- Aggregate patterns. Over time, anonymous patterns—such as which sections get the most visits—can guide which topics get expanded.
These kinds of logs are about keeping the site running and improving its structure, not about building individual listener profiles.
How privacy thinking shapes possible future features
If this site ever adds more interactive tools—like playlist builders or user accounts—privacy will still have to sit at the center.
- Minimal collection. Only gather information that's necessary for a feature to work instead of storing everything by default.
- Clear explanations. Any new feature should include plain-language notes about what's saved and why.
- Easy exits. People should be able to remove or export what they've shared without needing to be experts.
Thinking this way early keeps the focus on music and reflection instead of hidden data decisions.
Using anonymous patterns to decide what to build next
Over time, anonymous analytics can show which sections of the site people keep returning to.
- Popular topics. If posts on production get more attention than others, future deep dives might lean there.
- Navigation paths. Seeing which pages people move between helps highlight which links need to be clearer.
- Drop-off points. Noticing where visitors usually leave can suggest sections that need editing or restructuring.
The aim is to use trends to make the experience smoother, not to track who individual listeners are.
How third-party tools might interact with your visit
Many modern sites rely on outside services for things like fonts, embeds, or basic analytics.
- Embedded content. Video players or audio embeds from other platforms may collect their own usage data.
- Hosted assets. Fonts or scripts served from external providers can receive basic technical information from your browser.
- Separate policies. Those services operate under their own privacy policies, which may differ from this site's approach.
Being aware of this ecosystem makes it easier to understand how the web works beyond a single page.