February 5, 2026 - API Access & Usage Policy Updates

We’ve updated the API Access & Usage Policy with the following changes:

  • Expanded data protection section clarifying responsibilities for App Builders, users authorising Third-Party Applications, and handling of third-party user data
  • Added liability limitations for external integrations and downstream data processing
  • Updated permitted operations to accurately reflect all read and write capabilities now available through the API

🔗 API Access & Usage Policy


21st January 2026 – API Access & Usage Policy Update

We’ve updated the API Access & Usage Policy to protect creators from social engineering attacks targeting Third-Party Application credentials.

What’s Changed?

Definitions

  • Added definitions for Third-Party Application and Application Credentials to clarify OAuth-related terminology.

Section 5 - Prohibited Use

  • Explicitly prohibited creating applications at the request of third parties.
  • Prohibited sharing Application Credentials (client secrets, redirect URIs, webhook callbacks) with others.
  • Prohibited instructing others to create applications or share credentials in violation of the Policy.

Section 10 - Security Requirements

  • Added comprehensive guidance on Third-Party Application security.
  • Detailed steps to revoke access and delete compromised applications.
  • Specific warnings about social engineering tactics, including chatbots asking creators to create apps on their behalf.

Section 11 - Termination, Suspension & Versioning

  • Clarified that Fanvue may take immediate action against accounts involved in credential sharing or facilitating unauthorised access.

Why These Changes?

These updates respond to observed social engineering attempts where malicious services have asked creators to create Third-Party Applications and share credentials, enabling unauthorised access to creator accounts and data.

Need to Check Your Account?

If you have previously created a Third-Party Application at someone else’s request, or shared credentials with a third-party service:

  1. Revoke third-party access: Settings → Account → Third Party Apps Consent → Revoke
  2. Delete any compromised applications: Creator Tools → Build → [Select App] → Delete
  3. Contact support if you believe your account may have been compromised: support@fanvue.com

🔗 API Access & Usage Policy


18th December 2025 – Anti-Slavery & Anti-Trafficking Statement Update

We have comprehensively updated our Anti-Slavery & Anti-Trafficking Statement to meet current UK Modern Slavery Act requirements and reflect our platform-specific safeguards.

What’s Changed?

  • Expanded scope: The statement now covers both corporate supply chain compliance and platform-specific anti-trafficking measures in a single comprehensive document
  • Risk assessment: Detailed breakdown of risks in direct operations, platform content, and supply chain
  • Platform safeguards: Comprehensive documentation of creator verification, content moderation, and community reporting mechanisms
  • Law enforcement cooperation: Clear procedures for reporting and collaboration with authorities and NGOs including NCMEC
  • Governance: Formal board approval and sign-off structure
  • FY2024 reporting period: Updated to reflect the most recent complete financial year

This statement is made pursuant to Section 54 of the UK Modern Slavery Act 2015 and the California Transparency in Supply Chains Act 2010.

🔗 Anti-Slavery & Anti-Trafficking Statement


December 17, 2025 – Age Verification Policy Updated

We’ve updated the Age Verification Policy to reflect the current global landscape for age verification requirements.

What’s changed?

Countries with Mandatory Verification

Added to the list:

  • Australia: eSafety Online Safety Codes now in effect (December 2025)

Updated status:

  • Italy: Enforcement began November 2025 (previously listed as April 2025)
  • Germany: Strengthened enforcement powers from December 2025
  • France: Added detail on “double anonymity” requirement

US States

Now in effect:

  • Missouri (effective 30 November 2025)

The US now has 25 states with active age verification laws.

Upcoming Requirements

  • Spain: Updated status to reflect that legislation has passed and the Cartera Digital age verification system is in development, with full enforcement expected in 2026.

Why These Changes?

These updates ensure our documentation accurately reflects the current legal requirements for age verification across all jurisdictions where Fanvue operates.

🔗 Age Verification Policy


December 17, 2025 – Public Media Standards Added

We’ve added new Public Media Standards to establish clear guidelines for publicly visible creator content on the Platform.

What is Public Media?

Public Media refers to content visible to visitors before they sign in or subscribe, including:

  • Profile pictures
  • Profile banners
  • Intro videos
  • Public bio text

Because this content appears on Fanvue’s public discovery pages, it must meet stricter SFW (safe for work) standards.

Changes Made

Acceptable Use Policy - Section 2.9

  • Added new Section 2.9 “Public Media Standards”
  • Defined what constitutes Public Media
  • Listed prohibited content (nudity, implied nudity, see-through clothing, hyper-sexualised posing, age-baiting language, undisclosed AI imagery)
  • Added specific intro video requirements
  • Established tiered consequences for non-compliance

Community Guidelines - Section 11

  • Added new Section 11 “Public Profile & Discovery Guidelines”
  • Provided user-friendly guidance on what’s allowed and what’s not
  • Clarified what types of content (swimwear, lingerie, boudoir) can still be used when appropriate
  • Outlined consequences for non-compliance

Content Moderation & Protection Policy - Section 1.6

  • Added reference to Public Media SFW enforcement standards
  • Clarified that Public Media is subject to stricter moderation

Consequences for Non-Compliance

  • First offense: Profile disabled from appearing on the Discover section until updated
  • Subsequent offenses: Entire profile becomes inaccessible from public view until updated

These actions do not delete content, ban accounts, or affect earnings from existing subscribers.

Why These Changes?

These updates ensure:

  • Brand Safety: Public-facing content meets mainstream platform standards
  • Compliance: Clearer guidelines for creators on what can appear publicly
  • Discoverability: Creators understand what’s required to appear on the Discover section

🔗 Acceptable Use Policy | Community Guidelines | Content Moderation Policy


October 8, 2025 – Creator Affiliate Programme Restrictions Updated

We’ve updated the Creator Referral & Affiliate Policy to introduce new limitations on the Creator Affiliate Programme.

What’s changed?

Creator Referral & Affiliate Policy – Section 2.2

New affiliate offer limits:

  • Maximum commission rate set to 50% of Fan Payments (previously unlimited)
  • Affiliates can now promote a maximum of 5 different creators simultaneously (previously unlimited)

Creator Referral & Affiliate Policy – Section 2.3

New earnings cap:

  • Total affiliate commission per promoted creator capped at $50,000 USD (previously unlimited)

Why These Changes?

These restrictions help maintain a sustainable and balanced affiliate programme while protecting the platform’s revenue-sharing model. The changes ensure:

  • Fair commission structures for all parties
  • Manageable affiliate relationships
  • Long-term programme sustainability

🔗 Creator Referral & Affiliate Policy


October 8, 2025 – Age Verification Policy Updated

We’ve updated the Age Verification Policy to reflect the current status of US state age verification laws.

What’s changed?

Age Verification Policy – Section 1.2

States now in effect:

  • Added Arizona (effective 26 September 2025)
  • Added Ohio (effective 30 September 2025)

Upcoming states:

  • Corrected Missouri effective date to 30 November 2025 (previously listed as 30 August 2025)

The policy now reflects 24 states with active age verification laws, with Missouri set to become the 25th state in November 2025.

Why These Changes?

These updates ensure our documentation accurately reflects the current legal landscape for age verification requirements across the United States.

🔗 Age Verification Policy


Policy Updates

We’ve updated our policies to clarify requirements regarding face coverings and identity verification on the platform.

Changes Made

Acceptable Use Policy

  • Added new Section 2.8 “Identity Verification & Face Coverings”
  • Clarified that real creators cannot use face coverings that prevent identity verification
  • Listed specific prohibited items (masks, niqab, burqa, etc.)
  • Explained the compliance rationale behind these requirements
  • Noted that AI-generated content has different rules

Community Guidelines

  • Updated Section 5 “AI-Generated Media” with point 6
  • Clarified that AI creators CAN use face coverings, masks, and cultural/religious attire
  • Emphasized that AI content must not mislead users about being real

Content Moderation & Protection Policy

  • Added reference in Section 2 pointing to the Acceptable Use Policy for specific face covering requirements

Why These Changes?

These updates ensure:

  • Compliance: Meeting regulatory requirements to identify all individuals in content
  • Safety: Maintaining platform security and preventing impersonation
  • Clarity: Providing clear guidance for both real and AI creators

New Policy Added

We’ve introduced our API Access & Usage Policy to govern the use of Fanvue’s application programming interfaces. This comprehensive policy establishes clear guidelines for API usage and integration.

What’s covered?

  • Authentication & Authorisation: Requirements for API key usage, scopes, and version management
  • Key Management: Secure storage, rotation, and revocation procedures
  • Technical Requirements: HTTPS-only access, required headers, and error handling
  • Rate Limits: 100 requests per 60 seconds with standard rate limiting headers
  • Permitted Operations: Access to users, chats, creators, insights, and agency endpoints
  • Security Best Practices: Protecting API keys from exposure in repositories or client-side code

Key highlights

  • API keys are non-transferable and limited to one active key per user account
  • Keys cannot be retrieved after creation — store them securely immediately
  • All requests must use HTTPS and include proper authentication and version headers
  • Never commit API keys to public repositories or embed them in client-side code
  • Implement exponential backoff and honour rate limit headers to avoid throttling

Where to Find It

The API Access & Usage Policy can be found in the User Policies section under Website Policies.

🔑 Manage your API keys at fanvue.com/api-keys 📘 API documentation found at [api.fanvue.com/docs/introduction/welcome] (https://api.fanvue.com/docs/introduction/welcome)


Creator Earnings & Payouts - Dormant Balances Update

Complete rewrite of Section 2.8 (Dormant Balances & Unclaimed Earnings) to ensure legal compliance across jurisdictions:

Key Changes:

  • Jurisdiction-specific rules: Separate handling for UK/EEA creators vs US creators vs Rest of World
  • UK/EEA creators: 12-month invoice deadline with proper waiver language and 6-year discretionary reinstatement
  • US creators: Full compliance with state unclaimed property (escheat) laws - funds remitted to state authorities after dormancy period
  • Rest of World creators: Same treatment as UK/EEA (12-month waiver) unless local law requires escheat procedures
  • Proactive reminders: New requirement to send reminders at ~9 and ~11 months before dormancy
  • Clarifications: Creator balances are contractual receivables, not trust or client money
  • Reactivation process: Clear instructions for reactivating dormant balances

This update ensures compliance with both UK contractual limitation laws and US state escheat regulations while maintaining operational efficiency.