A setting that isn't a setting
At first sign-in, each account answers one question — is this account for a man or a woman — and the answer locks. It isn't a toggle to flip later; it's an account fact the server enforces on every list, every search, every suggestion, and playback itself.
Why server enforcement matters
Client-side filters can be bypassed by anyone with a browser console. FilteredTube's separation happens before content ever leaves the server: what doesn't belong on an account is never sent to the device at all. We keep the methods private; the outcome is the point.
This architecture also protects the experience itself. Because the separation happens before content leaves the server, there is nothing on the device to toggle, clear, or outsmart — and nothing awkward to stumble over in a shared kitchen. Each account simply lives in its own correct world. Families who have tried filter apps that hide content client-side know the difference immediately: hiding can be unhidden; never-sent cannot. It is the standard applied the way standards should be — quietly, completely, and without asking the user to be the enforcement.
At a glance
Key takeaways
- One locked question at setup; the server does the rest.
- Content that doesn't belong is never even transmitted.
- Outcomes public, methods private — as it should be.
Continue with FilteredTube
Explore the focused player.
Search Torah and Jewish music inside the reviewed FilteredTube experience, or read how official embeds and licensed media remain separate.