Editorial policy and corrections

The storefront mixes automated marketplace data with explanatory content. This policy defines which sources take priority, what the labels mean, how affiliate incentives are separated from factual claims, and how corrections should be handled.

Source and publication standards

Primary sources first

Blizzard support and API material controls claims about the WoW Token, account rules, product availability, and enforcement. Marketplace data controls only the marketplace listing facts visible in a dated snapshot.

Time-sensitive claims carry context

Price, stock, seller status, exchange rate, and offer coverage are snapshot facts. Pages should show the generation time and avoid presenting old observations as current availability.

One checkout offer, one set of facts

Region, realm, faction, quantity minimum, stock, price, referral code, and destination must refer to the same underlying offer. Values from separate faction listings must not be combined into one purchase claim.

Commercial links stay disclosed

Affiliate relationships are disclosed close to outbound actions and on the dedicated affiliate page. Sponsored relationships do not make a third-party claim authoritative.

Language, review, and corrections

What does “vetted” mean?

It means a listing passed the site’s published automated eligibility rules at snapshot time. It does not mean the site manually audited the seller, witnessed delivery, verified Blizzard-policy compliance, or guarantees a transaction.

How are risk claims written?

Operational tips such as keeping marketplace chat or screenshots are described as dispute evidence only. They must not be framed as protection from Blizzard enforcement. Blizzard’s current support guidance is linked directly in the risk guide.

How are material errors corrected?

Wrong account-policy, limit, currency, region, faction, destination, or price claims should be corrected at their generating source, regenerated across affected pages, and recorded in a dated correction note when the error could change a purchase decision. A public correction intake channel is still pending; see Contact.

Is automated or AI-assisted content reviewed?

Automated output is subject to build validation, but automation can still be wrong. Policy and legal-risk statements require direct primary-source support. Generated pages must not invent seller experience, delivery success, or first-hand product testing.

When was this policy last reviewed?

July 11, 2026. Official policy pages can change, so linked Blizzard guidance should be rechecked whenever the site republishes a limit or safety claim.