API Access & Usage Policy Updated
We’ve updated our API Access & Usage Policy so that it clearly sets out the rules for everyone building on the Fanvue API, and so that it reflects how apps connect to Fanvue today.
What’s changed?
Introduction and Definitions
- Made clear that the Policy, and Fanvue’s content policies, apply to every app built on the API, whether or not it is listed on the Fanvue App Store.
- Updated the Policy to reflect that API access is through OAuth, and added definitions for App, App Builder, Client Credentials and App Configuration.
Section 4 - Permitted Use
- Added Section 4.2, confirming that content created, published or sent by an app must follow our Community Guidelines and Acceptable Use Policy.
- Added Section 4.3 on AI disclosure, covering AI-generated media, AI chat and personas, the likeness of real people, and content involving minors.
Section 5 - Prohibited Use
- Refreshed the list of prohibited conduct to reflect OAuth access, and clarified that users connect to apps through the Fanvue App Store or “Connect with Fanvue” rather than by registering an app themselves.
- Clarified that redirect URIs and webhook endpoints must point to services the app builder controls.
- Added Section 5.2, listing types of apps that are not permitted, including gambling, “nudify” and non-consensual deepfake tools, content leaking tools, verification bypass tools, training AI models on Fanvue content or data, and escort services.
Section 10 - Security Requirements
- Updated security guidance for client secrets and OAuth tokens.
Why?
These updates make it easier for app builders to understand what is and isn’t allowed, and help keep creators and fans safe when they connect apps to their Fanvue account.