How Kingy AI handles evidence, disclosure, reporting, and editorial control.
This is the due-diligence page for sponsor claims, material relationships, source labels, usage rights, review boundaries, and campaign reporting.
Useful sponsorship begins with defensible claims.
Demo-led coverage
Product workflows, use cases, outputs, and buyer context take priority over generic promotional language.
Supported claims
Material claims should be demonstrable in the product, documented by an appropriate primary source, or framed with their limits.
Clear disclosure
Paid, affiliate, gifted, or otherwise material relationships should be disclosed clearly where required and appropriate to the format.
Creator voice
Sponsors may provide factual corrections and claim support. Kingy AI retains audience-first editorial judgment and does not sell undisclosed praise.
No guaranteed outcomes
Views, clicks, conversions, rankings, sales, pipeline, ROI, or other performance outcomes are not guaranteed.
Written scope
Deliverables, review boundaries, schedule, investment, usage rights, exclusivity, tracking, and reporting are agreed before production.
Match the claim to evidence strong enough to support it.
Claims about price, availability, performance, benchmarks, funding, customers, integrations, security, compliance, model capability, or market position require appropriate current support. If a limitation matters to the viewer’s interpretation, the limitation belongs in the framing.
Appropriate support can include
- Visible behavior in the product under stated conditions.
- Current official documentation or a primary announcement.
- A source-backed benchmark with method, date, and scope.
- Sponsor-supplied private context labeled as sponsor-supplied.
Kingy AI will not treat as proof
- Marketing adjectives without a testable basis.
- A legacy library label as proof of a commercial relationship.
- A modeled estimate as a measured campaign result.
- An unattributed screenshot, testimonial, customer logo, or performance claim.
Disclosure should be understandable where the audience encounters the endorsement.
Kingy AI applies the disclosure requirements relevant to the campaign and format. The FTC’s endorsement and influencer guidance addresses material connections and clear disclosure. For paid outbound links, Google Search Central documents rel="sponsored" as the preferred qualification for advertisements or paid placements.
Operational boundary: A disclosure label does not prove accuracy, performance, or endorsement quality. Claims still require support, and links still require the relationship-appropriate treatment.
Every number keeps its source class.
Platform-reported, Kingy-measured, sponsor-supplied, and modeled values are not interchangeable. Reports should retain the source, observation or measurement date, definition, and known limitations.
Platform-reported
Publication details and public view counts observed on the platform, with a source and observation date.
Kingy-measured
Controlled inventory and tracked-link values where Kingy tracking is configured and the data is available.
Sponsor-supplied
Private conversions, pipeline, sales, or other business context supplied by the sponsor and labeled as sponsor-reported rather than independently verified.
Modeled
Scenario estimates calculated from buyer-entered assumptions in the ROI calculator—not forecasts or promised campaign outcomes.
Availability boundary: A report may include publication, public views, tracked-link activity, and sponsor-supplied conversion context when configured and available. No private metric, attribution window, report cadence, benchmark, or outcome is promised by default.
Terms that must be agreed—not assumed.
Usage rights
Advertising, landing-page, sales, investor, retargeting, clip, or paid-media use requires written scope. Publishing a video does not grant unlimited reuse.
Review boundaries
Factual corrections and claim support can be reviewed. A standard revision count or sponsor control over creator voice is not published here.
Timing and availability
No standard production lead time or availability promise is published. Timing depends on fit, access, complexity, evidence, and agreed scope.
Public inventory is useful without becoming a sales claim.
The Public Proof library contains 132 distinct public video records. That inventory is not a claim about the number of sponsorship campaigns, current clients, testimonials, endorsements, or measured outcomes. Legacy Sponsor and Client labels describe source-library fields and do not independently establish paid consideration or current commercial status.
Bring the product, claims, access needs, and measurement plan into the fit review.
The fit review is the place to surface evidence gaps and scope questions before a campaign is represented as available or agreed.
Evidence operations, reporting, privacy, and corrections.
Effective July 16, 2026 · Last reviewed July 30, 2026 · Responsible owner: Sponsor Operations. Questions can be submitted through the Sponsor Fit Review.
Metric dictionary
Every reported value has a definition, unit, source class, owner, as-of date, and refresh cadence. Missing values remain unavailable rather than estimated.
Evidence ownership
Audience Operations owns channel snapshots; Sponsor Operations owns the delivery ledger; Editorial owns case-study publication approval.
Reporting windows
Campaign passports support 7-, 30-, and 90-day snapshots. A window can be reported, not due, or not available.
Correction policy
Corrections are append-only and record the timestamp, affected field, prior value, replacement, reason, and owner.
Inventory boundaries
The canonical Public Proof library contains 132 video examples. Separately, WordPress currently holds 141 private-by-design delivery control records covering 141 distinct video IDs, plus 142 private-by-design proof-case control records. These controls are internal records, not public posts; their private status is intentional. The case-publication inventory currently contains 0 approved linked public editorial pages, 125 active blocked proof-case candidates, and 1 superseded/withdrawn private control case. Superseded cases remain in the audit inventory but no longer govern a public page. These inventories measure different things; none establishes payment or campaign outcomes.
Relationship and disclosure matrix
| Record class | What may be stated | Required evidence |
|---|---|---|
| Legacy Sponsor label | Source-library label only | No payment, contract, or outcome inference |
| Legacy Client label | Source-library label only | No paid-relationship inference |
| Verified paid sponsorship | Material relationship and scoped deliverables | Private contract/scope evidence plus public disclosure check |
| Editorial-only coverage | Independent editorial relationship | Editorial record and no material-support conflict |
Source classes and data use
Platform-reported
Public or native platform values such as video publication state and view counts.
Kingy-measured
First-party inventory, tracked-link, or reporting values maintained by Kingy AI.
Sponsor-supplied
Private funnel, conversion, pipeline, or revenue values supplied by the sponsor and kept separate.
Modeled estimate
Planning outputs calculated from assumptions; never presented as measured campaign results.
Privacy, creative, and accessibility operations
Inquiry and sponsor-supplied data are stored privately and are not published as proof without authorization. Sponsor-form records may include the submitted fields, UTM/source values, mail-attempt logs, and limited operational metadata such as request IP for routing, abuse prevention, and audit. Access to sponsor-form data is limited to authorized operations personnel. Access, correction, deletion, and retention requests go through the Sponsor Fit Review contact path. Records may be preserved when required for security, dispute resolution, reporting, or legal obligations. Public case studies require claim support, a clear disclosure decision, story-specific imagery, exactly one featured hero, distinct supporting imagery, descriptive text alternatives, keyboard-operable controls, and desktop/mobile rendered review. This operating standard is not a claim of certification or guaranteed performance.
Evidence-passport demonstration
The sample below is explicitly synthetic. It demonstrates the schema and source classes; its values are not Kingy AI campaign results, benchmarks, forecasts, or guarantees.
View synthetic JSON sampleDownload synthetic CSV sample
Change log
| Effective date | Version | Change |
|---|---|---|
| July 30, 2026 | 0.4.8 | Replaced unapproved numeric retention promises with access-controlled, request-based interim language and explicit preservation exceptions. |
| July 30, 2026 | 0.4.7 | Removed copied metric fallbacks and made public, schema, and admin consumers withhold unavailable canonical values. |
| July 28, 2026 | 0.4.6 | Added an audited supersession state, separated superseded cases from active blockers, and added a report-only monitor for published posts whose active Sponsor Evidence case does not pass. |
| July 28, 2026 | 0.4.5 | Switched the private control-record and case-gate inventories from stale registry fallbacks to live WordPress-derived counts, and clarified that the control records are private by design. |
| July 21, 2026 | 2026-07-21.1 | Established the canonical inventory boundaries and separated the public proof library from internal delivery, proof-case, and publication-gate controls. |
| July 16, 2026 | 2026-07-16.2 | Added private reporting-window automation, versioned observation imports and exports, role-based evidence controls, and the fail-closed case-publication workflow. |
| July 16, 2026 | 2026-07-16.1 | Established the internal delivery ledger, source classes, 7/30/90-day passport model, correction history, and inquiry workflow identifiers. The unsupported 190+ claim remains withdrawn. |