Appealing a moderation decision

If a moderator declined a clip, performer profile, or your whole creator application, you can ask for a senior re-review. This isn’t a special form or a dedicated email — it’s a normal support ticket framed as an appeal. This guide explains the three pipelines an appeal can run on (clip / performer / account), the difference between “changes requested” (resubmit) and “rejected” or “suspended” (appeal), what evidence to include, the realistic outcomes, and the rare cases where an appeal goes beyond support to a formal data-protection or platform-policy escalation.

1. First — make sure you’re appealing the right outcome

There are four moderation outcomes you can land on. Only two of them are actually appeals:

• Changes requested — the moderator wants edits. This isn’t an appeal; it’s a do-over. Read the moderator’s note, make the edits, click Update clip and resubmit (clip) or update-and-resubmit on the performer profile / application. Most metadata-only edits clear within minutes of resubmission.
• Rejected — the moderator denied the submission for a reason they consider non-fixable by simple edits. An appeal here asks a senior moderator to reconsider.
• Disabled (clips only) — like rejected, but specifically for an already-public clip the team has taken down. Same appeal path as rejected.
• Suspended — the moderator has revoked your active creator status (whole storefront, or a specific performer). The heaviest outcome. Appeals here are taken seriously but the bar is the highest.

The wording in the moderator note tells you which outcome you have. If the note describes “the following changes are needed before this can be approved” you’re at Changes requested — resubmit, don’t appeal. If the note describes “this is declined because…” you’re at Rejected — and an appeal is the right next step if you disagree.

2. The three pipelines

Each pipeline has its own status enum and its own “rejected” semantics:

Clips

• Statuses: Draft → Submitted → Changes requested / Approved / Disabled.
• The clip-specific appeal flow is covered in detail in Why was my clip rejected §6.
• Most appeals on this pipeline are about Disabled clips where the creator believes the cited content-rule doesn’t apply.

Performers

• Statuses: Draft → Docs uploaded → Pending review → Changes requested / Approved / Rejected / Suspended.
• A rejected performer cannot be linked to clips for publishing — all clips that need them stay held.
• A suspended performer is one that was previously approved but had their status revoked, usually after a content issue surfaced post-approval.

Creator application (your whole account)

• Statuses: Submitted → Documents requested → Documents in progress → Documents uploaded → Verification pending → Verification in progress → Pending review → Changes requested / Approved / Rejected / Suspended.
• A rejected application means you can’t begin creating yet — your account remains in a fan-only state.
• A suspended application revokes your existing creator status — the storefront and active sales are blocked.

You can have actions running on more than one pipeline at once — e.g. one clip Disabled while your other clips and your application remain Approved. Treat each as a separate appeal.

3. Where to file the appeal

Every appeal goes through the standard support channel:

1. Open a ticket from Contacting support.
2. Pick the matching category:
   • Clip rejected or Disabled → Account admin (clip-level moderation).
   • Performer rejected or suspended → Account admin.
   • Creator application rejected → Account admin.
   • Whole creator account suspended → Account admin, marked urgent.
3. Use the subject line “Appeal: <clip URL or applicant ID> — <short reason>”. Concrete subjects help the team route the ticket to the right senior reviewer first time.
4. Provide the evidence in §5 in the ticket body.

There is no dedicated appeals@ mailbox — sending an appeal to the general support address works exactly the same. The ticket goes to the same queue.

4. Timeline expectations

• First response within the standard support window (typically 1 working day).
• Senior moderator review usually within 2–3 working days for clip-level appeals, 3–5 working days for performer and application appeals.
• Suspended-account appeals can take longer — sometimes a week or more — because the senior reviewer is also pulling the audit history of the decision. We don’t unsuspend on the same day except in the case of a clear platform error.
• If you haven’t heard back at all within the support window, reply on the same ticket asking for an ETA. Don’t open a second ticket — that just creates two parallel queues.

5. What to include in the appeal

A senior reviewer is going to re-open the original decision and compare your evidence to the moderator’s notes. The more concrete your appeal, the faster the re-review:

• The exact thing being appealed. Clip URL (the edit URL is fine) / performer profile ID / application ID. The team can find it from your account, but stating it directly saves a hop.
• The verbatim moderator note you received. Copy-paste from the on-page panel or the email. This anchors your appeal to the specific reason the moderator cited; reviewers can immediately see whether your appeal addresses that reason or talks past it.
• Your specific disagreement. Which part of the moderator’s reasoning you think is wrong, and why. “I disagree with the disabled status” alone isn’t enough — say “the note cites X, but X is not actually present because [reason]”.
• Evidence supporting your view, where relevant. A timestamp range in the clip (“at 03:14–03:20 the moderator’s reading appears to be of A, but the visible content is B”). A licensing receipt for music the moderator flagged. A verification confirmation from the performer’s ID provider if a performer’s status was rejected on docs.
• What you’re asking for. Reconsider and approve; reconsider with a request for guidance on what would be allowed; reconsider for a specific narrower scope (e.g. “the main clip is fine, only the trailer was the issue — can I re-cut just the trailer”).

Don’t include any prohibited content in the ticket itself. Screenshots that illustrate context are fine if they don’t themselves break the rules. The support team can pull the original from their side — your job in the ticket is to make the case, not to deliver the file.

6. What happens during the senior review

A senior moderator:

• Re-watches the clip (or re-reviews the performer profile / application).
• Reads the original moderator note plus your appeal.
• Cross-checks against current policy, the specific rule that was cited, and any related precedent.
• Sometimes consults with the legal or platform-policy lead, particularly on borderline content or impersonation / IP claims.

The reviewer then either:

• Upholds the original decision. Your appeal is denied. The reviewer will explain why — usually a more detailed version of the original note, often referencing the specific policy line that’s at issue. You may get a path forward (“if you edit X, we’d reconsider”).
• Overturns the original decision. Your clip / performer / application is moved back into the queue and the status flips to whatever the corrected outcome is. If the original outcome was a suspension, you receive a separate notification once the account is reinstated.
• Partially overturns. The reviewer agrees the outcome was too strict but a softer outcome is still warranted — e.g. “Changes requested” instead of “Disabled”. The clip moves to Changes requested with a fresh note describing the narrower issue.

If the appeal is upheld and your storefront / clip / account was income-affecting during the suspension, you can ask in the same ticket what we can do to make you whole (e.g. extending an affected promotion window, refunding subscribers who didn’t get the service they paid for, etc.). We handle this case-by-case.

7. Realistic outcomes — what appeals succeed at, and what they don’t

To set expectations honestly:

• Misclassification (the moderator’s note is about something not actually present, or about the wrong file): high success rate. Senior reviewers welcome these — a wrong decision overturned is a free quality-check on the moderation team.
• Procedural error (the wrong clip was disabled, a performer was rejected without their documents having been reviewed, a status was set during a known incident): high success rate. We want to find and fix these.
• Policy reinterpretation (the content is what the moderator says it is, but you think the policy should be read differently): low-to-moderate success rate. We re-read the rule with you. Sometimes the rule was applied too strictly and we overturn; sometimes the rule means what we thought and we don’t.
• Disagreement with policy itself (you accept the moderator’s reading of both the content and the rule, but you think the rule shouldn’t exist): not an appeal we can grant. The right channel for “the rule itself should change” is feedback, not an appeal — see Contacting support with category Feature request.
• Clear policy violations (illegal content, IP infringement we’ve verified, severe TOS breaches): the appeal won’t be upheld and reapplications are unlikely to land differently. The appeal does still get the courtesy of a written response.

8. After an appeal is denied

If the senior reviewer upholds the decision, you have a few remaining options:

• Adjust and resubmit (where possible). If the reviewer’s response suggests “this would clear if you change X”, do that and resubmit. This is essentially a Changes-requested route arriving after the fact.
• Escalate to platform-policy. If you believe the underlying policy is being applied inconsistently across creators, you can ask for a platform-policy review. Open a fresh ticket under Account admin with the subject “Policy review request” and reference the appeal ticket. The review team reads the ticket trail and either updates the policy (in which case affected decisions are revisited) or confirms the policy is being applied as intended.
• Formal complaint to a supervisory authority. For decisions you believe touch on rights protected by EU law (GDPR, the DSA, equal-treatment), you can also escalate to your national data-protection or platform-regulation authority. In Germany the relevant DPA is the BfDI; the DSA national coordinator differs by country. We’d much rather resolve at the appeal stage, but the formal route exists.
• Walk away. Sometimes the answer is the platform isn’t the right fit for the kind of content you want to publish. If you want to wind down see Deleting your creator account.

9. Common mistakes that hurt appeals

Resubmitting without addressing the moderator’s note. A clip flipped back to Pending without an actual change usually flips right back to Changes requested or Disabled. The fix is to address the cited reason; if you genuinely believe there’s nothing to fix, the path is an appeal in writing, not a silent resubmission.

Re-uploading the same clip under a different title. The moderation team detects this and treats the re-upload as a continuation of the original decision rather than a fresh case. It also reads as a circumvention attempt, which doesn’t help your appeal.

Writing an angry ticket. Senior moderators read appeals carefully and a hostile tone doesn’t make your case stronger — it just makes the team less inclined to give you the benefit of the doubt on borderline calls. Stick to facts.

Filing many appeals at once. If a batch of clips was actioned, file ONE ticket covering all of them with each clip URL listed. Multiple parallel tickets fragment the review and slow everything down.

Asking the support team to share which moderator decided. We don’t share that — moderators are not personally identified to creators, for safety reasons. The appeal goes to a different senior reviewer regardless.

Sending the actual prohibited content as evidence. If the original decision was about a prohibited element, sending the same content again — even framed as evidence — doesn’t help. Senior reviewers can pull the original from the moderation system; they don’t need you to resend.

10. Special case — DMCA / IP appeals

If your clip or performer was actioned in response to a third-party copyright or impersonation claim (not a platform-rules decision), the appeal path has an extra step. Beyond the standard support appeal:

• The original claim was lodged via the [email protected] formal channel. We have a copy on file.
• You can submit a counter-notice through the same email address. The counter-notice is a formal legal document with specific required information; it isn’t just “I disagree” — it has to contain your contact details, a signed declaration, and the specific clip / element you’re claiming the rightful interest in.
• When a valid counter-notice arrives, we notify the original claimant. They have a window (typically 10–14 calendar days under DMCA-like procedures, which we adapt to EU law) to either accept the counter-notice or escalate to court.
• If they don’t escalate, we restore the content. If they do, the content stays down pending the court decision.

For the creator-side view of how copyright takedowns are handled, see DMCA — handling takedown notices on your content.

Related

• Why was my clip rejected — the clip-specific deep-dive, with §6 covering clip appeals.
• Prohibited content — the rules a moderator is checking against.
• DMCA — handling takedown notices — the creator-side view of copyright actions.
• Contacting support — where appeals are filed.
• What happens after you report — the symmetric case (you reporting someone else’s content). Useful context if your appeal involves a third party who reported you.