TeenTidal
Explicit content filtering that can't be disabled.
The Gap
You share a family Tidal subscription. Your child has their own device. Tidal's explicit content toggle can be re-enabled by anyone, from within the app, in seconds. iOS Screen Time restricts explicit content in Apple Music — but that control stops at Apple's own apps. For third-party streaming, no structural mechanism exists. The gap is architectural, and it needs an architectural answer.
No structural mechanism exists to permanently filter explicit content in Tidal when a child uses their own iOS device unsupervised. This is a platform gap — not a configuration issue.
TeenTidal applies two independent content filters on every request. Every API call the client makes excludes explicit content at the request level — explicit tracks and video content are never requested from the server. On return, a deny-by-default rule inspects every response and drops any item where the explicit flag is missing, null, or true. Nothing slips through by omission. There is no settings screen to override this. The filtering is load-bearing structure, not a preference.
Parental controls in TeenTidal shape the listening environment without monitoring what's played. Set permitted hours, daily listening limits, and route-aware volume caps aligned with WHO and AAP hearing-safety guidelines. The parent dashboard shows how much and when — aggregate duration, session times, volume levels. It never shows what. The child's taste remains their own.
TeenTidal has no backend, no cloud sync, no analytics, and no telemetry. The privacy policy is short because there is genuinely nothing to disclose.
TeenTidal is a proper streaming app — ReplayGain loudness normalisation, a real-time audio visualiser, and the full clean Tidal catalogue at your fingertips. Your child gets a genuine music experience; video content is excluded, explicit content is absent, and everything else works exactly as they'd expect.
Currently in private development, pending the Tidal developer programme.