Open Tools
//- MARKETPLACE - SUBMIT A CORRECTION

Submit a Correction: Help Us Get It Right

Spotted something wrong on this site — a rule we stated backwards, a status that has changed, a claim we marked as confirmed that is only reported? This page explains what to include, and what happens next.

What We Don't Build
Data Status Legend
Is It Down Right Now?
Legitimacy & Safety
All Tools
HOW TO SEND A CORRECTION
//- 01 - WHY WE WANT THEM

WHY WE WANT CORRECTIONS

Because this site’s only asset is being right. A guide that states a Marketplace rule wrong is worse than no guide at all — a reader acts on it, and pays for it. Corrections are not complaints to us; they are how the site stays accurate between our own reviews. Every correction that checks out makes the page better for the next reader.

Being right is the only asset.
//- 02 - WHAT TO INCLUDE

WHAT A GOOD CORRECTION INCLUDES

Three things, and a correction is complete:

  • The page and the claim. Which page, and the exact sentence or figure you believe is wrong. ‘The fee page says 15%’ is findable; ‘your site is wrong about fees’ is not.
  • What it should say — and the source. The corrected figure or wording, and where it comes from: ideally an official Ubisoft page or announcement. We change claims against sources, not against other opinions.
  • When you saw it. Rules and status change. The date you saw the old information helps us tell a site error apart from a Ubisoft change that happened since.
Page, claim, source, date.
//- 03 - HOW THEY ARE REVIEWED

HOW CORRECTIONS ARE REVIEWED

We check the claim against the source. If the source is official and the claim on our page is wrong, the page is corrected and the fix is part of the page from then on. If the correction relies on a video, a screenshot or forum talk, the claim may be downgraded from ‘confirmed’ to ‘reported’ rather than replaced — that distinction is the whole point of our Data-Status Legend. And if we check and the page turns out to be right, we will say so and show the source we relied on.

Checked against the source.
//- 04 - WHAT IT IS NOT

WHAT A CORRECTION IS NOT

It is not a support channel for your Ubisoft account. We cannot unban, refund, restore or unlock anything — we have no access to accounts and no special line to Ubisoft. It is not a place to submit your own prices, offers or listings. And it is not a route to get a claim marked ‘confirmed’ without an official source behind it: the bar for that label does not move for anyone, including us.

Not a support channel.
//- 05 - FASTEST EFFECT

THE CORRECTIONS WITH THE FASTEST EFFECT

Not all corrections are equal, and the ones below jump the queue because readers act on them directly:

  • A changed rule. Fee, access conditions, resale hold — if Ubisoft has changed one and we still state the old version, that is the most urgent kind of error on this site.
  • A changed status. The Marketplace reopening, or closing again, makes every status page wrong at once until it is fixed.
  • A wrong status label. A claim we marked ‘confirmed’ that rests only on reporting — downgrading it protects readers from planning around an unproven claim.
  • A broken safeguard claim. Anything in our scam or safety guidance that no longer matches how the real Marketplace behaves.

If your correction is one of these four, say so in the first line — ‘changed rule’, ‘changed status’ — and it will be checked before routine fixes like typos and stale wording, which still get fixed, just in order.

The four urgent kinds.
//- 06 - AFTER YOU SEND

AFTER YOU SEND: WHAT ACTUALLY HAPPENS

Once a correction arrives, it joins a simple queue: read, checked against the source, and then applied, downgraded, or answered with the source we relied on. There are no ticket numbers and no automated replies — this is a small site, and the same people who write the pages check the corrections.

Applied corrections simply become part of the page; we do not keep a public changelog of every fix, because the page itself is the record — a reader landing on it today should meet the corrected version, not a history of our mistakes. If a correction changes something material — a rule, a status, a confirmed-versus-reported label — the affected pages are updated together, so the site never states two versions of the same rule.

And if your correction turns out to be wrong, nothing bad happens to anyone: we reply with the source we checked against, and the page stays as it was. The worst outcome of sending a correction is an explanation; the best is a fix every future reader benefits from. If you are still deciding whether it is worth sending, it is — accuracy is the entire product here, and readers who check us are part of how it stays that way. You can read what corrections are not for on What We Don’t Build.

Read, checked, applied or answered.
//- 07 - FREQUENTLY ASKED QUESTIONS

Straight answers

WHAT TO SEND

Three things. The page and the exact claim — which page, and the sentence or figure you believe is wrong. What it should say, and the source — ideally an official Ubisoft page or announcement, because we change claims against sources, not opinions. And when you saw it — rules and status change, and the date helps us tell a site error apart from a Ubisoft change that happened since.

For a claim to be replaced or marked confirmed, yes — the correction needs a source, ideally an official Ubisoft page or announcement. If the evidence is a video, a screenshot or forum talk, the claim may be downgraded from ‘confirmed’ to ‘reported’ rather than replaced. The bar for the confirmed label does not move for anyone, including us.

Yes — and that is one of the fastest-effect corrections there is. A changed status makes every status page wrong at once until it is fixed, so flag it in the first line with ‘changed status’ and it will be checked before routine fixes.

Yes. A wrong status label is one of the urgent kinds: a claim we marked ‘confirmed’ that rests only on reporting gets downgraded, which protects readers from planning around an unproven claim. That distinction is the whole point of our Data-Status Legend.

The ones readers act on directly: a changed rule (fee, access conditions, resale hold), a changed status, a wrong status label, and a broken safeguard claim in our scam or safety guidance. Say which kind it is in the first line — ‘changed rule’, ‘changed status’ — and it is checked before routine fixes like typos and stale wording.

HOW CORRECTIONS ARE HANDLED

We check the claim against the source. If the source is official and the claim on our page is wrong, the page is corrected. If we check and the page turns out to be right, we say so and show the source we relied on. If your correction turns out to be wrong, nothing bad happens: we reply with the source we checked against, and the page stays as it was.

Corrections are read, checked against the source, and then applied, downgraded, or answered with the source we relied on. There are no ticket numbers and no automated replies — this is a small site, and the same people who write the pages check the corrections.

No. Applied corrections simply become part of the page; the page itself is the record. A reader landing on it today should meet the corrected version, not a history of our mistakes.

No. A correction is not a support channel for your Ubisoft account. We cannot unban, refund, restore or unlock anything — we have no access to accounts and no special line to Ubisoft.

No. It is not a place to submit your own prices, offers or listings — and it is not a route to get a claim marked ‘confirmed’ without an official source behind it.

Scroll to Top