Kingy AI Trust Center
Every claim needs the right kind of evidence.
This policy explains what a source can prove, how it is labeled, when corroboration is required, and why access is not the same as verification.
Source hierarchy
Kingy AI uses the strongest available evidence for the claim being made. A source can be authentic and still be insufficient: a launch post proves that a company announced something, not that the product performs as claimed. The source label should tell readers whose evidence they are seeing.
| Source class | Examples | What it can support | How it is labeled |
|---|---|---|---|
| Direct observation | Kingy-controlled test, demo, interview, or recorded workflow | What occurred under the stated conditions | “Kingy tested,” “we observed,” with date, version, access, and limits |
| Primary public source | Documentation, model card, changelog, filing, repository, official pricing | What the source states at the recorded date | Linked and attributed to the issuing organization |
| First-party statement | Executive comment, press release, supplied case study | The speaker’s or company’s claim | “The company says,” “vendor-reported,” or a direct attribution |
| Independent secondary source | Reputable reporting, academic analysis, specialist research | Corroboration, context, or a separately reported fact | Named and linked where practical |
| Community signal | Public issue, forum discussion, social post, user report | A lead or documented user experience, not category-wide proof | Attributed and bounded to the observed report |
Verification rules
- Prefer the original document over a recap.
- Use a stable public URL when available and record the access or review date for changeable pages.
- Cross-check high-impact claims such as pricing, availability, benchmark leadership, customer adoption, funding, and legal status.
- Distinguish announced features from available features, and previews from general availability.
- Do not convert a company-supplied screenshot, customer list, or benchmark into an independently verified fact.
- When a claim cannot be verified, omit it, qualify it, or explain the uncertainty.
Links, archives, and changing pages
Links should point to the exact supporting page rather than a home page or search result. Fast-changing pricing, documentation, availability, and changelog pages should be paired with a source review cutoff or access date. If a stable archive is legally and technically available, it may be retained for verification; private or restricted material is not republished without authorization.
Unnamed and confidential sources
Anonymous sourcing is exceptional, not routine. Kingy AI should know the source’s identity, understand the source’s access to the information, seek corroboration, explain why anonymity is justified, and describe the source as specifically as safety permits. Ground rules must be agreed before disclosure. Confidentiality does not protect a source from fact-checking.
AI-generated and synthetic material
Synthetic media, AI-generated screenshots, and model-generated statements are not evidence of real product behavior unless the production conditions are central to the test and fully described. Editorial illustrations should not impersonate real interfaces, customers, benchmarks, or documentary scenes.
Source corrections
A source who believes evidence was misquoted, superseded, or misunderstood should provide the exact passage, the primary record, and the requested correction through the corrections process. Newer evidence does not automatically make an earlier statement false; the article may need an update note, clarification, or correction depending on what the record shows.