These guidelines explain what your app needs in order to be approved for the Fanvue App Store, and what you’ll need to maintain after launch to stay listed.
Our goal is to make the review process predictable and transparent. Every app is reviewed against the same requirements, so you’ll always know what we’re looking for and what needs to change if your submission isn’t ready yet.
If your app doesn’t meet one or more of these requirements, we’ll reference the relevant section below as part of our review feedback. Once you’ve addressed the feedback, you’re welcome to resubmit.
Before you submit, make sure you’ve checked:
- ✅ 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 screenshots, 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
Your App Store listing must always be safe for work. This includes:
- App name
- Description
- Logo
- Screenshots
- Promotional material
These surfaces are visible before a user has chosen to view your app, so they must never contain explicit or adult content.
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.
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
Your app shouldn’t encourage creators or fans to leave Fanvue for another creator platform. This includes links, onboarding flows, or promotional messaging directing users to competing services.
Before submitting, your app should 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, please 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 won’t be able to complete your review.
2.3 Listing quality
Your listing should accurately represent your product.
Required:
- English language
- Accurate description
- Accurate pricing
- At least two screenshots showing the product in use
Recommended:
- 3–5 screenshots
- Highlight your primary workflows
- Avoid login screens or splash screens as previews
2.4 App naming
Choose a name that’s unique, clear, and easy to understand. 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 should provide a dependable experience. Apps shouldn’t 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 should always know how to get help if needed. 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 should happen through Fanvue.
3.3 Pricing
Paid plans are priced through Fanvue within the platform’s supported range. Today this means setting up paid plans at one or more tiers; on-demand credit purchasing may follow later. Pricing and plan details must be accurate, with no hidden charges.
3.4 Commercial transparency
Creators should receive exactly what they pay for. Avoid misleading pricing, unexpected restrictions, or undisclosed limitations.
4. Design & quality
Apps listed in the Fanvue App Store should provide a polished experience that reflects well on both your product and the Fanvue ecosystem.
4.1 Useful apps
Your app should 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 AI-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; nothing clipped or overflowing.
- Spacing — deliberate, consistent padding and margins; not cramped or random.
- Typography — legible, with a clear hierarchy and a coherent type system (roughly 2–3 weights/sizes), not clashing fonts.
- Imagery — crisp, appropriately sized assets; not tiny, low-resolution, or obvious low-effort “AI slop.”
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 — clear plan highlights and differences, not an unstructured wall of text.
- Standard listing layout — follow the conventional listing structure; existing approved apps are the reference.
- Logo — high-quality and on-brand, not a generic AI placeholder.
- Previews — high-quality images that show the real app in use, and that are SFW.
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, AI-slop imagery) are a rejection.
The Fanvue component library is an optional fast path to a clean, on-brand UI. Partners may keep their own branding, not every issue is component-level.
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, 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 should 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 should 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.
6.3 Link back to the App Store
Your app’s homepage must link back to the Fanvue App Store. This can point to your app’s listing once you’re approved.
Common rejection reasons
A quick map from the issues we see most often to the section that governs them. Check your app against these before you submit.
| Reason | Section |
|---|
| Invalid / missing / non-owned URL | 6.2 |
| App doesn’t use the Fanvue API | 6.1 |
| Not really an app (funnel / landing page / single-creator) | 4.1 |
| Template / copycat / AI-slop | 4.2 |
| Off-platform payments / external checkout | 3.1, 3.2 |
| Explicit content in the store listing or marketing | 1.1 |
| Broken auth / test credentials don’t work | 2.2 |
| Fewer than two previews / previews don’t show the app | 2.3 |
| Naming (implies another platform, typo) | 2.4 |
| Listing not in English | 2.3 |
| Links to / promotion of other platforms | 1.6 |
| No discoverable support channel | 2.6 |
| Typos, poor layout / spacing, low-quality UI | 4.3, 4.4 |
Ongoing compliance
Apps must stay compliant over time, not just at submission. As the App Store grows we may introduce new requirements, and they can apply to apps that are already listed, we may ask for fixes or suspend a listing that no longer meets the bar. Material changes will be communicated to builders. Updates to an already-approved app are reviewed more lightly than new submissions and approved quickly when they look reasonable. 
