Skip to main content
Your app must meet these requirements to be approved for the Fanvue App Store, and keep meeting them to stay listed. If it misses one, review feedback cites the numbered section, and you resubmit once you’ve addressed it. Section 7 applies to each fan experience, which Fanvue reviews separately. Before you submit, check that:
  • Your app is production-ready and accessible via your own URL
  • Fanvue OAuth is working correctly
  • You’ve provided working review credentials (if required)
  • Your listing includes preview images, a description and support information
  • Your app uses Fanvue Payments for any paid features
  • Your Privacy Policy and Terms of Service are publicly available

1. Safety & content

Creators trust the Fanvue App Store with their businesses. Apps must protect creators and fans, comply with our platform policies, and avoid exposing users to harmful or unexpected content.

1.1 Safe-for-work listings

Everything a user can see before they open your app must be safe for work. This covers your:
  • App name
  • Description
  • Logo
  • Screenshots and preview images
  • Promotional material
Every creator and fan browsing the store sees these surfaces before they open your app. They must never contain explicit, adult or sexually suggestive material. The bar. Your listing must sit comfortably in a mainstream, general-audience app store. If you’d hesitate to show a preview to a broad audience, leave it out. Not permitted on any listing surface, including for apps aimed at adult creators:
  • Nudity or partial nudity
  • Lingerie, underwear, swimwear or bikinis
  • Sexualised AI-generated imagery
Use instead. Show the product doing its job: the real interface, screens, workflows and outputs. Where a person appears (for example in a creator profile or a generated image), they must be fully clothed in everyday attire and shown in a non-sexual context. This rule covers the listing only. What your app does in-product is covered by 1.2 and Fanvue’s content policies.

1.2 User-generated content

If your app lets creators or fans generate, post, send or exchange content, you are responsible for moderating that content appropriately. Your app must:
  • Respect Fanvue’s content policies
  • Not bypass Fanvue moderation systems
  • Provide a reporting mechanism where appropriate

1.3 Prohibited behaviour

Your app must not encourage, facilitate or provide instructions for harassment, exploitation, doxxing, self-harm, violence, hate, discrimination or any illegal activity.

1.4 Platform integrity

Apps must work with the Fanvue platform, not around it. Your app must not bypass or interfere with:
  • Moderation systems
  • Rate limits
  • Platform safeguards
  • Security controls

1.5 Honest representation

Your app must accurately represent:
  • Who built it
  • What it does
  • What data it accesses

1.6 No promotion of other platforms

Your app must not encourage creators or fans to leave Fanvue for another creator platform. This includes links, onboarding flows or promotional messaging directing users to competing services.

2. Performance & completeness

Before submitting, your app must be complete, stable and ready for creators to use.

2.1 Production ready

Before submitting:
  • Remove placeholder content
  • Remove empty pages
  • Remove dead links
  • Fix known bugs
  • Ensure the app works reliably
Apps with obvious crashes or incomplete functionality won’t be approved until these issues are resolved.

2.2 Review access

If your app requires authentication, provide everything our reviewers need to test it. This includes:
  • Working Fanvue OAuth
  • Test credentials (where required)
  • Setup instructions
  • Any special configuration required during review
Without working access we can’t complete your review.

2.3 Listing quality

Your listing must accurately represent your product. Required:
  • English language
  • Accurate description
  • Accurate pricing
  • 1 to 8 preview images. Reviewers expect at least two that show the product in use.
Recommended:
  • 3 to 5 preview images
  • Highlight your primary workflows
  • Avoid login screens or splash screens as previews

2.4 App naming

Choose a name that’s unique and clear. App names must not:
  • imply or reference another platform, for example names built around the word “only”, or names that borrow another platform’s branding;
  • use another company’s or product’s name or imagery;
  • contain typos or misspellings.

2.5 Reliability

Your app must provide a dependable experience. Apps must not regularly:
  • crash
  • freeze
  • display blank screens
  • leave users stuck on permanent error pages
Where something does go wrong, provide clear error messages and a path to recovery. Fanvue may request fixes, or suspend a listing, for stability or performance issues that materially affect creators.

2.6 Support

Creators must always know how to get help. Provide:
  • Support email or help centre
  • Onboarding or setup documentation
  • Security contact for vulnerability reports

2.7 Accuracy & integrity

Your app must deliver the features described in its listing and marketing. Claims must be factual and not misleading, and any data it synchronises or displays must be accurate. It must not introduce hidden functionality, unexpected charges, or behaviour that differs materially from what the creator has consented to.

3. Business & payments

If your app charges creators, payments must go through Fanvue.

3.1 Fanvue payments only

All paid functionality must use Fanvue Payments. External payment providers aren’t permitted.

3.2 No external checkout

Don’t send creators to another website to pay for features. All purchases must happen through Fanvue.

3.3 Pricing

Price paid plans through Fanvue, at one or more tiers, within the supported range. See Pricing plans. Pricing and plan details must be accurate, with no hidden charges.

3.4 Commercial transparency

Creators must receive exactly what they pay for. Avoid misleading pricing, unexpected restrictions or undisclosed limitations.

4. Design & quality

Apps listed in the Fanvue App Store must provide a polished experience that reflects well on both your product and the Fanvue ecosystem.

4.1 Useful apps

Your app must solve a genuine problem for creators. Examples we’d approve:
  • Analytics
  • CRM
  • Automation
  • AI tools
  • Scheduling
  • Creator productivity
Examples we wouldn’t:
  • Landing pages
  • Sales funnels
  • Collections of links
  • Single-creator websites
  • Placeholder applications

4.2 Originality

Build something original. We won’t approve apps that are:
  • obvious template exports
  • generic generated products with minimal refinement
  • near-identical copies of existing apps

4.3 Interface quality

We don’t expect every app to look identical, but we do expect a professional experience.
  • Layout. All content fits within bounds at the sizes we display, with nothing clipped or overflowing.
  • Spacing. Padding and margins are deliberate and consistent, not cramped or random.
  • Typography. Text is legible, with a clear hierarchy and a coherent type system (roughly 2 to 3 weights and sizes), not clashing fonts.
  • Imagery. Assets are crisp and appropriately sized, not tiny, low-resolution or low-effort generated imagery.

4.4 Listing and content quality

  • No typos in the listing, in-app copy, pricing and plan names. Typos in pricing are a common, avoidable failure.
  • Structured pricing. Plan highlights and differences are clear, not an unstructured wall of text.
  • Standard listing layout. Follow the conventional listing structure, using existing approved apps as the reference.
  • Logo. High-quality and on-brand, not a generic placeholder.
  • Previews. High-quality images showing the real app in use, meeting the safe-for-work bar in 1.1.

4.5 How we apply this bar

An isolated listing typo or a minor spacing nit on an otherwise solid app is accept-with-fixes: we approve and ask you to fix it, rather than rejecting. Repeated or pervasive quality problems (overflowing layouts, template sameness, multiple typos, low-effort generated imagery) are a rejection. The Fanvue component library is an optional fast path to a clean, on-brand UI. You may keep your own branding.

5. Privacy & security

Creators trust apps with sensitive business information. Your app must protect that data appropriately.

5.1 Privacy

Your app must have a publicly accessible Terms of Service and Privacy Policy and be GDPR compliant. Collect only the data it needs, and restrict internal staff access to creator data to those who need it to operate or support the app.

5.2 Data deletion

Creators must be able to request deletion of their data at any time. Honour deletion requests promptly.

5.3 Security & authentication

  • Your app must never ask a user for their Fanvue password.
  • Request only the OAuth scopes you strictly need for the documented features.
  • API secrets must be stored securely on a server and never exposed in client-side code; use a secrets manager and rotate if compromised.
  • All endpoints, web pages and OAuth redirect URIs must use HTTPS with valid TLS certificates and no browser warnings.
  • Handle session tokens (access, refresh and session tokens) securely as sensitive data; don’t log sensitive tokens or personal data.
  • Your app must be free of malware, spyware, ransomware and any code that performs hidden, unexpected or malicious actions (e.g. crypto-mining, ad-injection).

5.4 Intellectual property

Only use brands, names and assets that you have permission to use.

6. Integration & listing

6.1 Genuine Fanvue integration

Your app must provide meaningful functionality built on the Fanvue API. We verify API usage during review.

6.2 Valid, owned URL

Your app must be hosted on a working domain that you own. Placeholder sites, parked domains and Fanvue domains aren’t accepted. Your app’s homepage must link back to the Fanvue App Store. This can point to your app’s listing once you’re approved.

7. Fan experiences

Fanvue reviews every fan experience before fans can see it, separately from your app. This section applies to each experience a creator publishes through your app: the title, description, cover, delivery mode, external link and what fans reach by opening it. A rejected experience carries the section numbers in reviewRejection.reasonCodes. Fix it and publish it again for another review; see Review.

7.1 Illegal content

An experience must not contain, depict or link to illegal content, or content that breaks Fanvue’s content policies. This covers the experience itself and anything it embeds or plays. An experience must not send fans off Fanvue to content that Fanvue’s content policies prohibit. This covers externalUrl, links inside the experience and links in its title or description.

7.3 Misleading listing

The title, description and cover must describe what fans get when they open the experience. The experience must deliver what they promise, at the access mode and price the creator set, with no hidden charges.

Common rejection reasons

Check your app, and each experience it publishes, against the issues we see most often before you submit.

Ongoing compliance

Your app must stay compliant after approval, not just at submission. New requirements can apply to apps that are already listed, and we tell you about material changes. We may ask for fixes or suspend a listing that no longer meets the bar. The safe-for-work bar in 1.1 applies to existing listings too. If we ask for updated assets, supply them promptly. A listing that is not corrected may be suspended or delisted.