Trust & moderation
Safety on Bazario, in plain terms.
What is not allowed, what our automated checks actually look at, and exactly what happens when you report something — with a reason, a review, and a right to appeal at every step.
Prohibited conduct
These categories are what the report form asks you to choose from. Each one maps to a named reason in the review record.
Misrepresented items
Condition, authenticity or photos that do not match the item — for example a jacket listed as "like new" that arrives damaged.
Off-platform payment pressure
A buyer or seller pushing you to pay outside the protected payment — by bank transfer, gift card or a link sent in a thread.
Harassment or threats
Abusive, threatening or repeatedly unwanted messages in any thread, offer or review exchange.
Impersonation & fake accounts
Accounts posing as another person, as Bazario staff, or duplicating a real seller's listings and photos.
Prohibited goods
Items that may not be sold on Bazario at all — recalled products, weapons, and anything illegal to ship where you or the buyer live.
Review & offer manipulation
Fake orders to farm reviews, offers placed with no intent to pay, or retaliation through the review system.
Report from where it happened
Reports are contextual: you start them on the thing itself, so the record keeps its source attached. Every path below opens the report flow on that context.
Reporting is an account action — you will be asked to log in so the report, its review and any appeal stay linked to you.
What automated checks look at — and what they never do.
Bazario runs automated contact-pattern checks to catch off-platform payment pressure and scam behavior early. Here is the exact boundary of that system.
The checks inspect
- Patterns, not prose. Repetition and timing signals — e.g. one account sending the same external contact detail to many threads in a short window.
- Known risk markers. Links to external payment pages, gift-card requests and phone-number-shaped strings that move a deal off the protected payment.
- Account signals. Brand-new accounts contacting many sellers, or accounts already named in open reports.
A match creates a contact-pattern warning — a flag for review, not a verdict and never an automatic punishment.
The checks never
- Read private messages in bulk. There is no standing scan of conversation content. Nobody's inbox is mined for keywords.
- Judge intent. The system flags a pattern; a human reviewer decides what it means, with the reasoned context attached.
- Act alone. No listing is removed and no account is restricted by the automated check itself. Enforcement is always a separate, recorded human decision.
When a report is filed, a reviewer sees only the message or listing the report is about — the reasoned context — not the rest of the conversation.
Static seed fallback: this policy page is seeded static content. If live policy data cannot load, you see exactly this text, unchanged; no section silently disappears.
What happens after you report.
Four steps, each one a durable record. The original listing or message stays preserved as the source, so every decision can be audited against what was actually reported.
Live example — Report #RPT-204
Review pending · appeal availableSource — preserved, immutable
Wool trail jacket — listing lst-1003
Seller: Wilson Vintage · Reported by Jane Doe
Reason: contact-pattern warning — off-platform payment pressure. The listing snapshot is frozen at report time; neither party can edit what the reviewer sees. No private message content is shown outside this reasoned context.
- Reason
- Evidence
- Review
- Outcome & appeal
- Aug 4, 2026Reason recorded. Jane Doe selected "off-platform payment pressure" on listing lst-1003. Source snapshot frozen.
- Aug 4, 2026Evidence attached. The reported thread excerpt — only the reasoned context — linked to the report. Nothing else from the conversation.
- Aug 6, 2026Review opened. A moderator is comparing the evidence against the preserved source. Both parties can see the report status: review pending.
- NextOutcome, then appeal window. The decision will name its reason and stay on the record; either party may appeal within 14 days, against the same preserved source.
Report, enforcement, appeal — three separate records.
They are easy to confuse, so we keep them apart. Each is its own auditable entry with its own author, reason and timestamp; none overwrites another.
Record 1
The report
Filed by a buyer or seller, with a named reason and the preserved source. A report never changes anything by itself — it opens a review.
Example: #RPT-204 · review pending
Record 2
The enforcement action
A human decision after review: dismiss with a reason, warn, remove a listing, restrict or suspend an account. The action always cites the report and the reason it rests on.
Always names its reason — never silent
Record 3
The appeal
Either party may appeal within 14 days of the decision. A different reviewer re-reads the case against the same immutable source, and the appeal outcome is recorded alongside — it never edits the original entries.
14-day window · second reviewer
Status is never conveyed by color alone: every report, action and appeal shows its state in words ("review pending", "appeal available", "decision upheld") next to any indicator.
The urgent-safety boundary
If someone is in immediate danger, this page is not the tool.
Bazario's moderation handles marketplace conduct — listings, orders, messages and accounts. Threats to physical safety, emergencies or crimes in progress belong with your local emergency services first. Once you are safe, the help route below reaches our team directly; urgent-safety messages are read before everything else in the queue, by the operator's own configuration.
For anything on the marketplace itself — a worrying thread, a suspicious meetup arrangement, a listing that should not exist — report it from the listing, order or thread so the record keeps its context.
Help is an account-linked channel: log in and your message attaches to your orders and threads automatically.