Skip to main content

🚫 UNDERAGE ROLE-PLAY & IMPLIED MINOR CONTENT

Updated yesterday

What You Need to Know as a Creator on Fanvue

At Fanvue, we support freedom of expression and creativity — but we also have a legal and moral responsibility to keep the platform safe, respectful, and compliant with international laws.


❗ What’s Not Allowed

Even if you’re over 18, you cannot create or post content that:

  • Uses baby voices, language, or captions that suggest you’re underage

  • Depicts yourself as a teenager, schoolgirl, or child-like character in a sexual context

  • Includes clothing, props, or scenarios (e.g. teddy bears, school uniforms, "homework punishment") that imply sexualised minor role-play

  • Suggests you are “young for your age,” “just turned 18,” or uses similar language that could be interpreted as fetishising minors


🚨 Why This Is Illegal (Even If You’re 20+)

Laws in the UK, US, EU and Canada clearly state that content which depicts, simulates, or alludes to minors in sexual contexts is not just inappropriate — it can be criminal:

📚 Legal Basis

  • UK: Protection of Children Act 1978 – bans “pseudo-photographs” (content that looks like a child, even if acted by an adult)

  • US: 18 U.S. Code § 2256 & PROTECT Act – bans realistic simulations of minors in explicit scenarios

  • EU & Canada: Similar prohibitions under child protection and anti-exploitation laws

Even pretending to be underage in a sexualised way is treated as a serious offence by law enforcement and payment processors.


💡 Reminder: Just Don’t Risk It

It’s never worth gambling with your safety, your brand, or your future. If your content could look like it’s sexualising someone underage — it doesn’t belong on Fanvue.


🛡️ We’re Here to Help

If you’re unsure whether something crosses the line, please reach out — we’re happy to review content and provide guidance before it gets published.

We’re so proud to have you as a creator and want to ensure your content thrives — safely and sustainably. 💖

Fanvue Trust & Safety Team
[[email protected]] | [[email protected]]


Did this answer your question?