Guide overview
Fan Seasons are public-facing community spaces. Safety starts with clear rules: what fans can show, what invites mean, what access requires and how creators handle moderation.
Set rules for privacy, moderation, visibility, access boundaries and safe fan recognition.
Fan Seasons are public-facing community spaces. Safety starts with clear rules: what fans can show, what invites mean, what access requires and how creators handle moderation.
Each section keeps Fan Passport identity, recognition, access and paid support clearly separated.
Fans should understand whether their name, badges, Community Rank, supporter history or Community Recognition entry is public, private, creator-visible or anonymous public. Avoid surprising fans with public display.
A badge or supporter-history record should not automatically mean paid access. Keep recognition, Community Rank, Supporter Status and active-access status clearly separated.
Leaderboards, comments, public Passports and community messages should have moderation expectations. Use reporting, blocked terms and creator review where available.
Imported emails and supporter records should be masked or handled carefully during review. Do not expose raw imported data publicly.
Fans should know what they are buying before checkout. Direct support is support only. Paid creator offers can unlock access when the offer says so.
The product should support anonymous or private visibility where possible, especially for Community Recognition and Fan Passport identity.
No. Imported emails and private supporter records should not be exposed publicly.
Yes, creator grants can be used when appropriate, but they should remain explicit and auditable.
Next step
Explain invite links, supporter history, visibility and creator-scoped Fan Passport identity.
See what has a ClaimYourRank fee, what stays free and how access is created.
Bring Patreon, Ko-fi, Gumroad or CSV supporter history into a Fan Passport claim flow safely.