You see a Report button, click it, fill in the form, and submit. A short banner reads “Thanks — our team will review.” The modal closes. From your side, that’s the whole flow. This guide explains what’s happening on the other side of that banner — how the report reaches a moderator, what they do with it, the four outcomes a report can end in, and why we don’t email you back about every report.
1. The moment you click Submit
When you submit the report, the form sends it to our moderation team in three places at once:
- A moderation queue. The report becomes a row in a private dashboard at [email protected]. Each row carries who reported, what they reported (the page URL, the creator or piece of content, the surface — a profile, a clip, a feed post, a chat bubble, a comment, a broadcast, etc.), which reason you picked, and the text you wrote in the What happened? field.
- An email to the moderation inbox. A short summary email lands at [email protected] so a human can see the new report without having to log into a dashboard.
- A Slack alert (in some categories). Content reports, bug reports, and a handful of high-priority categories also fire a Slack notification to the right team channel. This is for response speed, not for the public — these channels are internal.
All three happen within seconds of you clicking Submit. You don’t have to wait.
2. What the moderator sees
The moderator opening your report sees:
- Your username (or “anonymous browser” if you were not logged in).
- The exact URL on Lewdden where the Report button was pressed.
- The kind of report — either Content (something on Lewdden that shouldn’t be there) or Bug (something is broken).
- The reason you picked from the four-option list: Illegal / minor / non-consensual content, Copyright / DMCA / impersonation, Harassment / hate / threats, or Spam, scam, off-topic, broken / other.
- The full text you wrote in What happened?.
- For bug reports — the technical context the form attaches automatically: page URL, browser, version numbers, and any recent in-page errors. No personal data, no contents of any other tab, nothing about other sites you’ve visited.
3. Triage — the four possible outcomes
Every report ends in one of four states:
New
The moment the report lands, it sits in New. Nobody has looked at it yet. Reports almost never stay in New for long — usually only the minutes between submission and the first moderator opening the queue.
In review
A moderator has the report open and is investigating. For straightforward cases — clear policy violations, obvious spam — this might last a few minutes. For tricky cases (e.g., a disputed copyright claim, a he-said-she-said harassment thread) it can take longer because the moderator may need to read other context, watch the clip in question, or consult a second reviewer.
Actioned
The moderator decided your report was right and did something about it. Something can mean any of:
- Removing a clip, feed post, comment, or chat message.
- Hiding a piece of content from public view (it stays archived for our records but nobody can see it on the site).
- Warning the creator who posted it.
- Pausing or closing the creator’s storefront.
- Restricting a fan account that was harassing creators.
- Filing a notice with a platform partner if the content was hosted off-site (rare).
- For DMCA / copyright cases, escalating to our legal contact and processing the takedown formally.
You won’t usually be told which of these the moderator chose. The actioned status itself doesn’t email you back (more on that in §5).
Dismissed
The moderator decided your report didn’t reach the threshold for action. Common reasons:
- The content is within our published policy — even if it offended you personally.
- The “harassment” was actually a heated but consensual conversation between two people.
- The “copyright violation” was a fair-use clip, a creator’s own back catalogue, or licensed material.
- The bug report was about the reporter’s own browser cache or extension, not the site.
- The “spam” was a creator promoting their own clips in their own thread (allowed).
A dismissal isn’t a judgement on you — it’s a judgement on whether the specific thing you flagged crosses a line we can act on. If the same thing keeps being flagged by different reporters, the moderator may reopen and look again.
4. How long does it take?
It depends on the reason:
- Illegal / minor / non-consensual content — highest priority. Triaged within hours. We treat these as page-the-team incidents during work hours and we have an on-call path outside work hours.
- Harassment / hate / threats — usually triaged within a day, faster if the report mentions a specific threat or there’s a pattern across the same creator/account.
- Copyright / DMCA / impersonation — usually triaged within a day, longer if we need to verify ownership or contact the rights-holder.
- Spam, scam, off-topic, broken / other — usually triaged within a few days. Lower priority by design, because most of these self-resolve once a single moderator sweeps the surface.
These are typical, not promised. A weekend can stretch the spam / off-topic bucket. A serious incident in the highest-priority bucket may pull moderators off everything else for a few hours.
5. Why we don’t email you back about every report
This is the question we get most often. The short answer is: we don’t email reporters about the outcome of an individual report. Three reasons:
- Privacy. Telling you what we did to the person you reported reveals private moderation actions about that account. They reported things too. We don’t tell the world about the outcomes of theirs either. It’s symmetric.
- Volume. A single bit of content can attract dozens of reports from different people. Emailing every reporter the same outcome creates a stack of mail that doesn’t help anyone.
- Re-litigation. If the moderator decides to dismiss, an automated “we dismissed your report” email tends to invite back-and-forth that doesn’t change the outcome.
What we do do:
- If we need more information to triage your report, a moderator will email you directly from [email protected]. If you ever get such an email, it’ll be a human writing it.
- If the report led to an outcome that affects you specifically (e.g., your own clip is restored after a wrong takedown, or your own account is restricted because of someone else’s report against you), you’ll be told about that change as a normal account-action email.
- If the content you reported is removed from the site, you’ll see it gone the next time you visit the page.
6. What to do — and not do — after submitting
Do block the account if it’s about you personally. Reporting and blocking are independent. A report gets a moderator’s attention. Blocking is the one thing you can do immediately for your own peace of mind — open the chat or profile, click the kebab (⋮), choose Block. They stop being able to message you or see your activity.
Do keep evidence if you can. If something was particularly bad and you took a screenshot before you reported, save it. We don’t ask for it on the form, but if the original post is later deleted by the offender, your screenshot can help an appeal or escalation.
Don’t re-submit the same report twice. A repeat report on the same thing from the same account is treated as one — it doesn’t bump priority. (Repeat reports across different accounts on the same thing do help. They’re a useful signal of how widely something is being noticed.)
Don’t expect a public reply. Per §5, the answer to “did anything happen?” is usually “look at the page again”. If the thing is gone, the report was actioned. If it’s still there a week later, it was either dismissed, or it’s awaiting a slower-priority sweep.
7. The special case — DMCA / copyright
If you’re reporting something because you own the copyright on it and it’s being used without permission, the in-page Report form is the right place to start. But for a formal DMCA takedown notice — the kind you need for legal weight — you need to send a separate email with the specific identifying information lawyers require.
That email goes to [email protected]. The Report modal itself shows a small hint pointing you there for exactly this reason. The formal email path doesn’t replace the Report form, it complements it — file the Report so we have it in the queue, send the formal notice so we have the legal paper trail.
8. The special case — bug reports
The Bug kind on the Report modal goes to a different team — the engineers, not the moderators. The form attaches technical context automatically: which page, which browser, plugin and theme version, recent in-page errors. The body field is your description of what was supposed to happen vs. what actually happened.
Bugs don’t go through the four-state moderation triage above. They go into our engineering tracker and get prioritised against other open bugs. You won’t get an emailed update on a bug report either, for the same reasons as content reports — but if the bug touches your account specifically (e.g., a transaction that didn’t complete), you’ll hear from support separately.
9. If something is wrong with your own report
Rarely, you’ll see one of these errors after clicking Submit report:
- “You’ve sent a lot of reports recently. Try again later.” — you’re rate-limited. This is a safety valve against accidental spam or automated abuse of the report form. Wait a bit and try again.
- “Could not send your report.” — a transient network or server hiccup. Try again. If it keeps failing, see §10.
- “Reports are not enabled right now. Please try again later.” — the report system is briefly off (we do this during maintenance windows). Try again later.
10. When the Report button isn’t enough
If the in-page Report flow isn’t working, or the thing you need to report doesn’t fit on the form (e.g., a multi-creator pattern, a legal matter beyond DMCA, a serious safety concern), reach out via Contacting support and pick the matching category. Support tickets go to humans who can escalate further than the Report queue can.
For genuine emergencies involving immediate physical harm, Lewdden is not the right channel — call your local emergency services. We can act on accounts and content; we cannot replace police or medical help.
Related
- Reporting a creator or content — how to flag something — the form itself, what the buttons say, what to write.
- Contacting support — for things that don’t fit the Report form.
- DMCA — handling takedown notices — the creator-side view of how copyright complaints are handled.
- Prohibited content — the policy lines that determine whether a report is actioned or dismissed.
