How DudesChat stays App-Store-safe without selling out

Here's the tension every app like ours has to solve: Apple has rules about what can appear in the App Store, and our community is, let's say, not shy. Most platforms resolve this by either getting kicked off iOS or by neutering themselves into a dating app for accountants.

We're doing neither. The answer is a three-tier content model.

The three tiers

• Daylight — public. Profiles, chat, browse, communities, who's-around. Everything you can open on a phone your mum might glance at. This is what the iOS app shows by default.
• Adult — opt-in. Nudity that isn't pornographic, between consenting adults, in private. Behind an age gate and a two-way opt-in, with a confirmation step, moderation, and report/block. On iOS this is tightly scoped; the full experience lives on Android and the web.
• Explicit — elsewhere. The hardcore archive — the body shots, the cams — stays exactly where it belongs: next door at DudesNude, on the web. The iOS app never renders it; it points you to the door instead.

Why this works

It's not a fudge. The tiers are enforced at the infrastructure level — separate storage, per-build render gates — not by politely asking content to behave. The iOS build cannot show what it isn't allowed to show.

That means we get to ship a genuinely good app on the App Store and keep the community exactly as filthy as it wants to be in the places where that's allowed. Same Dudes. Pants on — at least on the page Apple's looking at.

This applies to words too, not just pictures: "Daylight" covers explicit descriptions, not only explicit images. The classifier and our human moderators work on both.