Accuracy before volume.

Publisher: PokeTeamOn

Last reviewed: September 3, 2026

1. Product behaviour must match the product

When a page explains a PokeTeamOn feature, the description should match the behaviour users can inspect in the current supported product. We do not describe planned functionality as if it were already available, and we do not turn a limited check into a broader competitive claim.

2. Facts, assumptions, and limitations are different things

Factual inputs such as selected format, species, moves, typing, or calculated values should be distinguished from assumptions required by a diagnostic rule. A limitation should not be hidden merely because it makes a conclusion sound less decisive. When the tool cannot establish something from supported evidence, the editorial explanation should not pretend that it can.

3. No fabricated battle conclusions

PokeTeamOn does not publish invented match results, fabricated testing sessions, fake player experiences, or unsupported claims that a team will win because a diagnostic rule returned a particular finding. Examples may be used to explain a concept, but examples must be presented as examples rather than disguised as observed competitive results.

4. Sources should be appropriate to the claim

Source verification depends on the subject. Product-behaviour claims should be checked against the product and its locked contracts. Pokémon facts, rules, and third-party data should be checked against the relevant source material before publication. PokeTeamOn should not cite a source merely because it ranks well in search results.

Detailed data-source, dataset, sprite, and credit information is maintained in dedicated transparency documentation so users can distinguish product rules from third-party source material.

5. Original explanatory writing

Guides and explanations should be written for the PokeTeamOn workflow and should add useful interpretation, examples, limitations, and connections to the tool. We do not plan to mass-publish thin pages whose only purpose is to target small keyword variations, and we do not copy another publisher's guide structure or wording as a substitute for original explanation.

6. Corrections and updates

If a material factual error, attribution problem, or inaccurate description of current product behaviour is identified, the page should be reviewed and corrected. Changes in supported formats, datasets, mechanics, or product contracts can also require an update even when the original statement was accurate when written.

7. Publisher identity and credentials

PokeTeamOn is the publisher identity for this project. The site must not invent tournament records, professional credentials, certifications, official Pokémon status, or personal experience that has not actually been established. Authority should come from transparent product behaviour, careful sourcing, and correct explanations rather than fabricated biography.

8. Commercial separation

The current staging build does not contain active advertising. If monetization is enabled later, advertising must not silently change deterministic product results, editorial conclusions, or the order of repair candidates. Advertising disclosures will be updated when advertising actually becomes part of the production site.

9. How to report a problem

Corrections, attribution concerns, privacy questions, and reproducible product issues should use the verified public channel on the Contact page. The About page explains the product and publisher identity, while the Privacy and Terms pages cover current operational boundaries.