Skip to content

Privacy at MetaDJ.ai

A factual map of what the current app measures, what it keeps in this browser, and what it uses to make Private Listening Rooms work.

Measurement on public pages

On Vercel-hosted deployments, public pages load Vercel Web Analytics and Vercel Speed Insights. MetaDJ.ai also sends bounded product events for public listening and discovery interactions.

The telemetry runtime does not load on Private Listening Room paths. Custom events repeat that pathname check, and the current feature events do not send raw search queries, page URLs, media error text, or private-room activity.

Storage in this browser

localStorage keeps device-local listening preferences and history: repeat, shuffle, mute and volume settings, a resume Quest and position, liked Quest IDs, Blend, the crossfade setting, and the selected Cinema scene.

sessionStorage keeps tab-local playback continuity, the Highlight preference, temporary scroll positions, and a one-per-tab marker when a visit arrives from a retired MetaDJ Music host. If browser storage is unavailable, the listening experience falls back to in-memory state for the visit.

Private Listening Rooms

A successful room unlock sets a signed, HTTP-only session cookie used to authorize the room, its session check, and its protected media requests. Locking the room clears that cookie.

A separate functional navigation-hint cookie lets the shared header show Private and Lock controls before the app hydrates. It does not grant room access, and the authoritative session check can clear it when the room session is no longer valid.

Advertising

MetaDJ.ai does not currently run advertising. The current app code includes the Vercel measurement packages described above and no advertising SDK.

Current runtime checked September 2, 2026. For music use and authorship information, read Rights & AI.