How we comply
HotChili Analytics, LLC · VerityIndex · Posture as of May 17, 2026
We posted the source of this page — our reply to YouTube's API compliance team — so prospective beta users and journalists can read the boundary directly. The short version is below; the long version is our May 11, 2026 compliance response and the May 17, 2026 follow-up (Stage B no-persistence architecture).
1. Single GCP project
All YouTube API Data v3 calls originate from GCP Project 504013801019. No alternate projects, no personal API keys, no third-party proxies.
2. YouTube branding (III.F.2)
All "Watch on YouTube" affordances use the official YouTube logo SVG (red play tile, white triangle, wordmark) at a minimum of 20px height on a white background, per YouTube brand guidelines.
3. Derived metrics & visible LLM disclosure (III.E.4.h)
We do not show numeric percentage scores ("X% True") on public gallery or public HTML/Markdown reports. Public surfaces use five categorical editorial verdicts:
Highly Likely True · Likely True · Mixed / Uncertain · Likely False · Highly Likely False
Visible notice (YouTube API compliance team V.2): Verdicts and commentary are independently generated by an LLM and analyzed by HotChili Analytics, LLC (VerityIndex); they are not official YouTube data. This notice appears above the fold on every report and on every public surface that displays a verdict.
4. Editorial disclaimer (footer)
Every report carries:
Independent editorial research by HotChili Analytics, LLC. Not provided, endorsed, or calculated by YouTube or Google.
5. Data retention — no covered YouTube API data is stored
As of the May 17–18, 2026 architectural update, the VerityIndex frontend no longer persists YouTube-derived statistics or metadata for the surfaces that display them. Video titles, channel names, and thumbnails are fetched live via the public YouTube oEmbed endpoint at render time and cached only in the user's browser for one hour. View counts and other YouTube statistics are neither requested nor displayed.
Our backend analysis pipeline likewise does not store any YouTube API metadata covered by
the YouTube API Services Developer Policies' retention rules. Multimodal analysis runs
directly against the audio track, on-screen visual frames, and publicly available transcript; the
covered API fields are not cached. The 30-day rolling-purge job (purge-youtube-data-daily,
03:00 UTC) remains scheduled as a defence-in-depth safety net and writes a daily "no-op" audit row
to compliance_audit.jsonl, but no longer has anything to delete.
| Item | Posture |
|---|---|
| Frontend display of YouTube titles / thumbnails / statistics | Live oEmbed at render time; no server-side persistence |
| Backend YouTube API metadata (snippet, statistics, etc.) | Not stored; analysis uses audio + visual + transcript directly |
| Purge endpoint (defence-in-depth, retained) | POST /api/v1/batch/admin/purge-youtube-data (supports dry_run=true) |
| Cloud Scheduler safety-net job | purge-youtube-data-daily, 03:00 UTC — runs as no-op |
| Audit log | compliance_audit.jsonl — daily "nothing to purge" entry preserved for audit continuity |
6. Closed-beta access control
New accounts require explicit admin approval before any analysis can be submitted. Default visibility for completed reports is private. The public gallery contains exactly one curated demo video. All YouTube-derived artefacts live under user-scoped GCS paths with cross-user access blocked at both storage and API layers.
7. Managed Gemini DeepResearch — ToS rider
Every managed Gemini DeepResearch run requires the user to acknowledge a ToS rider at submission time:
DeepResearch will run a deep-dive citation pass against this analysis using HotChili Analytics' Gemini DeepResearch pipeline. You acknowledge that you remain bound by the YouTube Terms of Service and that any redistribution of this enhanced report is your responsibility under those terms.
The acknowledgement event (user_id, video_id, analysis_id, timestamp, IP, user agent) is written to compliance_audit.jsonl. The DeepResearch call only fires if that write succeeds.
8. Quoted from the May 11, 2026 response
"Every item in your May 6 notice is live in production. Three observability items remain in flight on a queued backend rebuild and will be confirmed in a follow-up note. We remain available for a compliance review call at your convenience."
← Home · For beta researchers · For analysts · Terms · Privacy