The "Report this class" button on every class detail page is for flagging a class that violates community standards. It is different from a review (which is a public opinion) and a dispute (which is a financial complaint about a specific booking).
When to report
Report if you encounter:
- Misleading information: a class listed as suitable for beginners that is clearly advanced; a class with a fake location.
- Unsafe practices described in the class details or experienced first-hand.
- Discriminatory language: classes that exclude on the basis of race, gender, religion, sexual orientation, etc.
- Predatory pricing or false advertising: drastically misleading pricing, hidden fees, deceptive promises.
- Content that violates our community guidelines.
- Impersonation: someone running a class under a name or photo that is not theirs.
- A class that you suspect is a front for something other than what is described.
Reporting is not for:
- "I did not like the teacher's style." That is a review.
- "I want a refund." That is a dispute (after talking to the host).
- "The class was bad." Review.
- "The class started late." Review, unless a pattern (in which case a report).
- Disagreements with the host about a policy that was clearly stated upfront. Not a report.
When in doubt, leave a review. Reports are for things that warrant moderator attention.
How to report
You need to be logged in to report. The "Report this class" button is on every class detail page, near the bottom or in the action menu.
Click 'Report this class'
A dialog opens. If you are not signed in, the dialog prompts you to log in first. Anonymous reporting is not supported because it is a high-volume abuse vector.
Pick a reason
A dropdown with the categories above (misleading info, unsafe, discriminatory, predatory pricing, community guidelines violation, impersonation, other).
Describe what you saw
A required text field, minimum 20 characters, maximum 2000. Be specific. Include names, dates, what was said or written, what you witnessed. "I went on March 4 and the teacher said X" is far more actionable than "the teacher is bad".
Submit
The report is recorded with status OPEN. Our admin team gets an email immediately. You get a confirmation that the report was received but no public acknowledgement (we do not surface "reported" status on the class).
What we do with reports
A human on our team reviews every report. We typically respond within 24 business hours.
Possible outcomes:
| Outcome | What it looks like |
|---|---|
| Dismissed | The report does not meet our threshold for action. The class stays up; we may or may not message the host. |
| Mentor warning | We message the host explaining what was reported. No public visibility. |
| Class hidden | The specific class is unpublished. The host can edit and resubmit. |
| Mentor suspended | The host's account is paused. They cannot host new classes until we resolve. |
| Mentor banned | Rare. For severe violations (impersonation, fraud, predatory behaviour). The account is closed; existing bookings get refunded. |
We do not surface the outcome publicly. You as the reporter do receive an email acknowledging the report was received but we do not always disclose what action was taken (sometimes because the resolution is private to the host, sometimes because an investigation is still open).
If a report results in a refund to you (e.g. the class never happened because the host got suspended), the refund processes through the dispute flow, not the report flow. Reports and money are separate concerns.
What the host sees
Hosts get notified that a report was filed but they do NOT see your name or the report text. They see a generic "a user reported your class". This protects reporters from retaliation while still letting hosts know there is a concern.
If our investigation requires us to share specifics with the host (e.g. "a student reported your March 4 class started 40 minutes late and was clearly not the class described"), we do that without naming you unless you give explicit permission. In practice we summarise.
Reports vs reviews
Reviews are the right vehicle for opinions and experience. Reports are the right vehicle for policy violations. The two can overlap (a class that is genuinely dangerous deserves both a negative review AND a report) but they serve different roles.
If you only file a review when something is dangerous, future students may book before they see the warning. If you only report and never review, the host's average rating does not reflect the issue.
Reports vs disputes
Disputes are about money for a specific booking. Reports are about content / safety of the class itself.
If you booked a class that turned out to be a scam, file BOTH:
- A report on the class (alerts our team to investigate the host).
- A dispute on your booking (gets your money back).
Common questions
Can I report a class without booking it? Yes. The "Report this class" button is on every class detail page, not just on bookings you have made.
Can I report a mentor's whole profile, not a specific class? Reports are tied to a class. If your concern is about the mentor more broadly, file a report on any of their classes and explain in the description. We will look at the whole profile when investigating.
Will the host find out it was me? We do not tell them. We work hard to keep reporter identity private. We are not perfect (a host who looks at the obvious pattern of "the only person who attended my March 4 class" could potentially guess) but we never directly identify reporters.
Can I see my report history? Not currently. There is no "my reports" page. We do send you an acknowledgement email which serves as your record.
Are reports public? No. Reports and their content are private. Only admin sees them. The investigation outcome may eventually surface publicly (a banned mentor's profile becomes inactive, for example) but the report text itself does not.
Next steps
- If your complaint is about money for a specific booking, see Disputing a booking.
- If your complaint is about experience and you want it public, see Leaving a review.
- For our standards generally, see Community guidelines.