Editorial Policy

Scope

This policy covers everything published on candyarcade.xyz: game pages, category pages, guides and articles. It is written to be specific enough to be checkable rather than a list of reassuring adjectives.

Originality

All content on this site is written for this site. We do not copy, paraphrase or rewrite other people's articles, game descriptions or documentation. We do not scrape competitors' sites for topics, content or structure, and we do not run content through a rewriting tool to disguise its origin.

Where a general concept is common knowledge in game design - gravity, collision detection, combo multipliers - we explain it in our own words and, where a specific technical claim is involved, cite primary documentation. Where a mechanic has a long public history, we say so rather than implying we invented it.

Who writes here

Content is written and tested by Alex Morgan, the site's Browser Games Editor, who also builds the games. The author page states what that experience consists of and, equally importantly, what it does not: we do not claim degrees, certifications, awards or institutional memberships, because there are none to claim.

Every article carries a visible byline, a published date and an updated date. If an article is substantially revised rather than lightly corrected, the updated date changes and the change is described at the foot of the article.

How we describe our own games

Most of the writing on this site is about mechanics we implemented ourselves. That creates a specific risk: it is easy to describe the design you intended rather than the code you shipped. Our rule is that any claim about how one of our games behaves is verified against the running game, not against design notes, before publication.

Numbers quoted on game pages - combo thresholds, power-up durations, difficulty step distances, point values - are read from the implementation. When a value changes in a game, the game's page is updated in the same change.

Sources for technical claims

For claims about web platform behaviour we use primary sources: the relevant specification, MDN Web Docs, or the browser vendor's own documentation. We do not cite an article that cites a specification when we can cite the specification.

We do not invent references. Every external link in an article points to a page we have actually read, and if a source later disappears we either replace it or remove the claim that depended on it.

What we do not publish

• Fabricated statistics, studies, survey results or expert quotes.
• Invented player counts, download figures, ratings or reviews.
• Claims of global leaderboards or rankings, which we have no server to support.
• Health, nutritional, dietary or medical claims about sugar or confectionery.
• Financial claims, prize claims, or anything resembling gambling.
• Content about, or targeted at, identifiable private individuals.
• Articles produced purely to occupy a keyword, with no useful content behind them.

Editorial independence

Nothing on this site is paid for by a third party. We do not accept payment for links in editorial content, for positive coverage, or for sponsored articles dressed as independent writing. If that ever changes, any paid placement will be labelled clearly as advertising at the point where it appears, not in a footnote.

If advertising is added to the site, it will be visually separated from editorial content and will never be placed to be mistaken for navigation, for a play button or for a download link.

Publishing cadence and quality

We publish when there is something genuinely useful to publish. Our working ceiling is two articles a day, and we hit it rarely, because most days there is not a second subject worth two thousand words. A thinner article published to keep a schedule is worse for readers than nothing published at all, so the schedule loses.

AI assistance

We use AI tools in the same way we use a code editor, a spell checker or a search engine: for drafting support, for reviewing code, and for catching things we missed. Every published sentence is read, edited and verified by a person, and every factual claim is checked against the implementation or a primary source before it is published.

We do not publish unreviewed generated text. We do not generate articles in bulk to occupy keywords. If an error in our content originated in a tool rather than a person, that is still our error and it is corrected the same way.

Corrections

Factual errors are corrected as soon as they are verified. Minor corrections - a typo, a broken link, a clarified sentence - are made silently and update the page's modified date. Corrections that change the meaning of a claim are noted at the foot of the article, stating what was wrong and what it now says.

We do not quietly delete pages to hide mistakes. If an article is withdrawn because it was wrong in a way that cannot be fixed by editing, its URL explains that rather than returning an error.

Reporting a problem

Corrections, accessibility problems and copyright concerns can be sent to hello@candyarcade.xyz. See the contact page for what to include. Corrections are prioritised over all other correspondence.