Trust & intentional access

Adult content flags, age verification, and verified creators—so access stays intentional and sellers can show who’s charge-ready.

Primary action: Creators marking adult hubs → listing readiness · Learners → age verification when opening adult hubs

Adult flags and Explore defaults

• 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

• 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.

Step-by-step: Adult content & age verification.

Verified creators

A verified badge can appear when Stripe Connect is charge-ready (charges_enabled). Completing Connect / monetization setup is the path. Product or FAQ copy may mention Stripe Identity as part of Connect verification—the badge you see for sellers is tied to being able to take charges.

• Helps buyers trust who you are on profile / paywall.
• Does not boost Explore ranking.

Setup: Your profile & sharing · Turn on paid access.

Aura vs the badge

• Aura — Scarce community endorsement for hubs (not money). See How Aura works.
• Verified badge — Seller charge-ready signal from Stripe Connect.

They answer different questions. Neither is a ranking guarantee.

Legal and policy surfaces

• In-app adult content policy: app.kahana.io/legal/adult-content
• Related hub/creator policies also live under /legal/… in the app.
• Site security overview: Security.

What’s next

• Browse Explore — discovery and adult filter context.
• List a hub on Explore — listing readiness including adult yes/no.
• Buying & access.

Open Explore