M.Muzday
Listen. Choose. Make it yours.
All available M.Muzday releases — just €0.50 per track.
Cookie policy
Last updated: 15 September 2026
1. Principle
M.Muzday does not activate optional cookies, local storage or related statistics before consent. Rejecting is as easy as accepting. Strictly necessary functions may operate independently.
2. Storage used
| Name | Purpose | Category | Duration |
|---|---|---|---|
| mmuzday_optional_consent | Stores “accepted” or “declined” so the choice is respected. | Necessary | 180 days |
| music-lang / music-theme | Remembers language and appearance. | Optional | Local storage until deletion or withdrawal |
| Usage statistics | Records visits, plays, listening events and downloads in aggregated form. | Optional/analytics | Only while needed for the stated purpose |
3. Consent and withdrawal
“Accept” permits optional preferences and statistics. “Decline” or closing the banner stores the rejection and optional statistics do not start. Withdrawal applies for the future and does not affect prior lawful processing. Cookies and site data can also be removed in browser settings.
M.Muzday visitor analytics
Only after optional analytics consent, the site records page views and distinct browsers or signed-in accounts. The first-party mmuzday_stats_visitor cookie lasts up to 12 months (HttpOnly, SameSite=Lax). A source category, such as Google or YouTube, is derived from referrer or utm_source. Full referring URLs, search terms, IP addresses, device fingerprints and geolocation are not stored for these analytics. The category is temporarily kept in sessionStorage for internal navigation until the tab closes. Source metadata is deleted after 395 days on the next collection or analytics request. Existing visit and music activity logs are not replaced by this feature.
The counter displays aggregate numbers and does not count image loads as visits. Detailed reports require a server-verified password. The necessary mmuzday_analytics_session cookie lasts 8 hours; only a hash of its random token is stored on the server. Login protection uses an HMAC-derived IP key without storing the original IP; the record is deleted within 30 minutes on the next analytics request. Consent can be withdrawn in cookie settings. No external analytics service is connected.