Record policy

How a handle lands here, and how it comes off.

Most of what follows is enforced in code rather than promised in prose. The factual-basis gate, the investigation window, the status flow, and the one-time grace are all implemented, so a moderator cannot quietly step around any of them. Where a rule is a review standard applied by a person instead, this page says so.

The full legal documents live separately: terms of use, privacy, and removal and takedown requests.

Roles

Two roles, and they are kept apart.

The record covers sellers and it covers buyers. Every rule below applies the same way to both: the same investigation window, the same factual-basis gate before anything publishes, the same dispute route, the same one-time clearing.

An entry is a handle acting in a role

An entry is never about a person. It is about one handle, on one platform, in one role. The same account is routinely both a buyer and a seller, and being a bad buyer says nothing about how that account sells. So a handle that is reported in both roles gets two separate entries with two separate audit logs, and we do not merge them, cross-link them, or add them up. There is no combined record of a person on this site and there is not going to be one. Every entry states which role it covers, so you can always tell which one you are reading.

What a seller entry is about

How they sell: what was listed, at what price, described how, and whether what arrived matched it. Gouging, fakes and proxies, misstated grades, shill bidding, resealed packs, bait and switch, taking payment and not shipping, refusing a refund on an item that was misdescribed.

What a buyer entry is about

What they did after the sale. The core case is a buyer who receives a card and then tells the platform they did not: the payment is clawed back, the card is already gone, and the seller is out both. The same shape covers a false not-as-described claim, a chargeback after delivery, returning a different or damaged card, claiming the package was empty, refusing delivery and then filing a dispute, and keeping the item and the refund.

What a buyer report has to show

Reporting a buyer for a false non-delivery claim sits close to alleging fraud, so the evidence standard is stated rather than left to judgment. On top of the factual-basis gate that every entry has to clear, a buyer entry publishes only where the file has at least one of these:

Delivery confirmation from the carrier or the platform showing the item reached the address the buyer gave, dated against the claim.
The platform's own case outcome: the dispute, claim, or chargeback and how it was decided.
The buyer's own acknowledgement in writing, in a message or a public comment, that they received the item.

A seller's account of the conversation, on its own, is not enough to publish a buyer entry. This one is a review standard applied by a person, not a check the code performs: the code requires a recorded factual basis, and it is the reviewer who holds that basis to the three sources above.

Still reported conduct, not a verdict

A buyer entry says what was reported and shows what we checked. It does not say anyone committed fraud, and it is not a finding that they did. Read it the way you would read a seller entry: evidence you can look at yourself, so you decide how much weight it carries.

The rules

Evidence is the standard for publishing

The form takes a report without screenshots, because a real account of what happened is worth having even when the screenshots are gone. What it does not do is publish one. Nothing a stranger submits appears automatically, and nothing appears at all until our own investigation has recorded a checked source behind it, which a report nobody can verify will not survive.

Handles, not people

We identify a seller by their public handle or storefront and their public selling conduct, and a buyer by the public handle they bought under and what they did about that purchase. We do not publish legal names, addresses, phone numbers, employers, or any other private information, and we reject reports that include them.

A full, dated audit log

Each entry carries a dated log of every report against that handle in that role. We show when something was reported and never who reported it. Reporter identity is not published, not shared, and not collected in the first place, which holds for a seller reporting a buyer as much as for a buyer reporting a seller.

Red flag, not a verdict

An entry means proceed with caution, here is why, shown next to the evidence so you can reach your own conclusion. It is not a claim that anyone committed a crime and not a determination of guilt.

Disputes are welcome

Anyone with an entry can dispute it, buyer entry or seller entry, same route and same standard. A person reviews every dispute. Nothing about an entry changes on the strength of the form alone - the form takes no proof of who is filing it, so a submission cannot be allowed to move a published entry by itself. When the review starts, the entry is marked disputed and stays that way while the evidence is re-checked. If it holds up the entry stays. If it does not, the entry comes down and the log records that rather than hiding it.

One chance to come off

A fair reason gets a handle cleared and its entry removed: a mispriced card or comps not run on the seller side, a claim opened before the package turned up and then made right on the buyer side. That is a one-time grace. Repeat the same conduct and the handle comes back with a re-listed entry, for good. The system will not clear the same handle twice.

Investigation

What happens in the 3 to 5 days after a report.

A report is a starting point, not a finding. Between submission and publication we do our own work, and what gets published rests on that work rather than on the reporter's word. Reports that do not survive it are dismissed and never appear.

When the report is about a seller

The reported listing or streamWe go to the source named in the report and record what is actually there: the asking price, the description, the terms, and the dates.

The same handle across its other listingsOne bad price can be a mistake. We look at the seller's other active and completed listings to see whether the reported behavior is a pattern or a one-off.

The same seller on other channelsSellers commonly run the same storefront across several platforms. We check the other public channels that same storefront operates to see whether the conduct repeats there.

Public price historyFor pricing reports we compare against public sold history so over-market is a measured statement rather than an opinion.

Anything that contradicts the reportWe record what cuts against the report as well as what supports it. A report that does not hold up is dismissed and never published.

When the report is about a buyer

The delivery record for that saleTracking, the carrier scan, and the delivery confirmation the seller was given. This is the fact the whole report turns on.

What the buyer actually claimed, and whenThe wording of the claim and its timing against the delivery date, taken from the platform case rather than from the seller telling us about it.

How the platform ruledA marketplace or card issuer that already found for the buyer is evidence against the report, and it is recorded as such.

Other reported sales involving the same buyer handleOne lost parcel is a lost parcel. A pattern across unrelated sellers is a different thing. We look only at other reports about this handle acting as a buyer.

Anything that contradicts the reportA parcel really can go missing after a delivery scan, and a buyer who says so is not a fraudster. If the claim looks legitimate the report is dismissed.

On a buyer report the sources are different. The work is the same shape and the same window, but what gets checked is the tracking and delivery record, the platform case or chargeback and how it was decided, what the buyer said in writing, and whether other sellers have already filed the same claim against that handle here. Those records are not public: they come out of the transaction the reporting seller was part of and had every right to hand us. The limits below still hold in full. We do not go looking for anything private about a buyer beyond the transaction that was reported, and we do not contact them, the other sellers they bought from, or anyone else. The standard a buyer report has to meet before it can publish is set out under roles.

Limits we hold ourselves to

We look only at public conduct in a marketplace transaction: listings, storefronts, public streams, public sold history, and the delivery and dispute record of the sale being reported.
We never publish a person's legal name, address, phone number, employer, or any other private detail, and we do not go looking for them.
We do not contact a seller's customers, family, or employer.
We record observations, not conclusions about anyone's character or intent.
Where a finding has a public source, we cite it so a reader can check it themselves.

Occasionally we publish faster. If the findings are conclusive before the 3 day mark, an entry can be published early. When that happens it is stated in that handle's audit log, with the actual number of days, so the record never implies a longer review than it got.

Status flow

What each status means.

Reported

Evidence received and reviewed. Not yet contested.

Disputed - under review

The handle contested this. The evidence is being re-checked.

Confirmed

Reviewed and the evidence holds.

Cleared - came off

Came off the list. Not shown publicly.

Re-listed - repeat

Back on after repeating the same tactic. The one-time grace is spent.

Cleared handles are removed from the record entirely and their entry page stops existing. They stay in the totals so the numbers remain honest, but the handle is no longer named. A clearing applies to the entry that was cleared: if the same account also holds an entry in the other role, that one is untouched, because it was never part of the same question.

Terms

Terms of use, in short.

The full terms are at /legal/terms. That page is the canonical version and governs if anything below differs from it. What follows is the plain-language summary of the same rules, kept here next to the policy it describes.

What this site is

CardConduct is an independent, community-run record operated by StephensCode LLC. It publishes reports about the public conduct of public trading-card handles on both sides of a sale, across all card games: how a seller sells, and what a buyer did about a purchase they made. Entries reflect reports submitted by the public together with our own review of the evidence and the sources we checked.

Opinion and evidence

Entries are statements of caution and opinion based on the disclosed evidence shown with each one. The underlying screenshots, observations, and sources are published so readers can evaluate them independently and reach their own conclusions. Nothing on this site states that any person or business has committed a crime, and nothing here is a legal finding. That applies to a buyer entry as much as to a seller entry: reporting that a buyer claimed a delivered card never arrived is an account of what was reported and what we checked, not an accusation of fraud.

Accuracy and corrections

We investigate before publishing and re-investigate on dispute, but reports come from the public and evidence can be incomplete or mistaken. If you believe an entry is wrong, file a dispute and it will be re-checked. We correct or remove entries that do not hold up, and the audit log records the correction rather than erasing it. If the entry is not yours and you want something removed, the route is /legal/takedown.

Privacy

We do not ask reporters for their identity and do not store it. We store the submitted report text, the attached screenshots, and a salted hash of the submitting network address used only to throttle abuse. Dispute contact details are stored so we can reply, are used for nothing else, and are never published. The full detail is at /legal/privacy.

Submitting a report

By submitting a report you confirm that:

Your report is truthful and describes conduct you actually observed.
The screenshots you attach are genuine and unaltered.
You are reporting public marketplace conduct, a seller's selling or a buyer's handling of a purchase, not a private dispute or a grudge.
You are reporting the handle in the role it actually acted in, and not using a buyer report to attack a seller you disagree with or the other way around.
You have not included anyone's legal name, address, or other private details.

Reports that are fabricated, altered, retaliatory, or that expose private information are rejected, and the submitting source may be blocked.

No affiliation

CardConduct is not affiliated with, endorsed by, or sponsored by any marketplace, card manufacturer, game publisher, grading company, or creator. Partner creators may link to this record; none of them control what goes on it. All trademarks belong to their respective owners.

No warranty

This site is provided as-is, for informational purposes, with no warranty of any kind. Decisions about who to buy from, and who to ship to, are your own. StephensCode LLC is not liable for any loss arising from use of this site.

Contact

Anyone named in an entry, seller or buyer, should use the dispute form. It routes straight into the review queue and is the fastest way to get an entry re-checked. Replies are written by a person, not sent automatically, so allow up to 5 days for one. For anything else, email info@stephenscode.dev.

Removal requests from anyone the entry is not about go through /legal/takedown. Canonical documents: terms and privacy.