Adult flags and Explore defaults
Adult hubs can list, but they do not sit in the default catalog the way general hubs do.
- Creators mark hubs that are adult (18+) as part of listing readiness (isAdultContent).
- Explore can include, exclude, or show only adult hubs when you use the adult filter. Default browsing keeps adult hubs out.
- Adult hubs stay out of SEO indexing: not in the sitemap and not in bot HTML.
Age verification
Access to adult hubs stays behind login and date of birth—not a checkbox for guests.
- Adult access requires login plus date of birth. There is no anonymous “I’m 18” unlock.
- When you verify, the app stores verification if your DOB proves you are 18+.
- Anonymous APIs do not grant READ on adult hubs. You must be authenticated.
Verified creators
Creators can show a verified check when Stripe Connect is ready to accept charges (charges_enabled). You may see it on a profile or paywall.
Product UI and FAQ often say Stripe Identity. The shipped condition is Connect charge-readiness. The badge is not Kahana editorial endorsement, not a background check beyond that readiness, and not an Explore ranking boost.
Aura vs the badge
Aura is community recognition for hubs—a signal of what people find worth learning from. It is not a Kahana safety certification.
The verified badge is about commerce readiness: whether a seller can take charges through Stripe Connect. Different job from Aura.
Legal
Policies for adult content, hub access and privacy, creator monetization, and content protection live in the app under /legal/….
Related
Rules and steps: Adult content & age verification. Adult defaults shape Explore. Sellers show up on profiles and turn on paid access via optional earning. Aura stays the community quality signal.
Browse with intention
Explore the public catalog, or Create a hub with the access settings that fit what you share.