A report starts review; it does not prove the target violated policy.
If an event is listed on ClaraWide, its official vendor application and booth payment happen only through the Vendor Application / Event Signups section on that ClaraWide event page. Do not use outside forms, DMs, comments, QR codes, payment handles, or third-party links claiming to be the official signup/payment route. Those may be scams—report them to ClaraWide.
Report what happened. ClaraWide reviews the story—not just who complained first.
Reports can preserve surrounding context so reviewers can understand whether one person caused the problem, both people participated, or the report does not support a violation. Blocking and reporting are separate controls: block to stop unwanted contact; report when ClaraWide should review conduct.
For messages, review can include enough conversation before and after the reported material to understand the interaction.
If the evidence shows both people threatened, harassed, or otherwise violated policy, both can receive appropriate action.
A user can block someone while order, dispute, safety, or moderation evidence remains available for legitimate review.
Tell ClaraWide where the problem happened.
This foundation records a browser-local safety case. Product, shop, post, profile, and message surfaces can prefill this form.
Your safety reports
Report status does not expose private internal thresholds or unnecessary information about another person’s account.
Blocking is a boundary—not a deletion button.
Blocking should stop ordinary social contact and hide eligible social interaction. Existing order obligations, dispute evidence, safety records, and legally required records remain intact.
What happens after a report?
ClaraWide keeps the relevant content/version, target, reporter, timestamp, reason, surface, and evidence needed for review.
A message report can include surrounding conversation instead of only one sentence. Reviewers can expand farther back when the situation requires it.
The reviewer asks what the target did and what the reporter did. A mutual fight can produce action for both people.
Serious threats, stalking, doxxing, fraud, or coordinated abuse can justify immediate restrictions. Lower-severity patterns may escalate with repetition.
Outcomes can include no violation, target violation, reporter violation, both violated, or further review. Evidence and action history stay auditable.
Users should be able to ask for review. Overturned automated or human decisions should stop counting as active strikes and become quality-improvement data.
High-severity content can be intercepted before delivery/public display, preserved internally for evidence, and escalated without exposing the target to the harmful content.
