Compliance reviewer information
Review Niche Lab
The current client is a local internal research CLI. This page describes the implemented Phase 1 flow, the disabled Phase 2 state, and the evidence required for a future audit submission.
Project details
- API client
- Niche Lab
- Operator
- Kasparas Marcinskas, individual/private person
- Reviewer contact
- marcinskas.kasparas@gmail.com
- Google Cloud project
- The project ID and numeric project number are supplied directly in the application and are not published on this public page.
- Public application URL
- The deployed overview and this reviewer page are the public compliance URLs. The research client itself is not publicly accessible.
- Demo/access details
- No hosted dashboard, public account, login, or demo credentials exist. The current client is a local CLI used only by the operator; reviewer evidence consists of the public disclosure pages, CLI screenshots, state output, and fail-closed gate evidence.
Implemented Phase 1 flow
- Load a typed 42-niche, 126-family taxonomy and quota/policy configuration.
- Plan bounded, one-page public-video searches and skip completed logical work.
- Record every API request and discovery relationship with run, query, rank, family, wave, and UTC provenance.
- Batch-enrich known videos and channels with current public metadata.
- Apply exact date/duration qualification after enrichment and flag live or unusual formats.
- Produce current descriptive inventory, retention, and data-quality reports.
Phase 1 is complete. Aggregate relevance was statistically validated; this does not claim that every candidate was individually reviewed.
Disabled Phase 2 state
Phase 2 has not started. Permission state is not_requested, the approval environment flag is false, no permission record exists, and protected tables are empty.
Comparative ratios, breakout and concentration research, repeated public statistics, velocity, custom scores/rankings, categorization, projections, and extended retention remain disabled. The current project uses only public YouTube Data API metadata and public statistics. See the YouTube API disclosure for the intended request and controls.
Suggested reviewer steps
- Review the homepage, privacy policy, and terms.
- Review current endpoints, data categories, retention, and requested scope on the YouTube API disclosure.
- Confirm the public site contains no login, user account, OAuth consent, cookies, trackers, advertisements, or API credentials.
- Review the supplied command-line screenshots showing Phase 1 completion,
not_requested, and the protected gate failing closed. - Compare the application wording and screenshots with the exact submitted Cloud project and endpoint/quota details.
Evidence checklist
- Homepage screenshot with browser address bar, visible privacy link, and YouTube API identification.
- Privacy-policy screenshot showing YouTube API Services, Google Privacy Policy link, data use, and deletion/retention.
- Terms documentation showing the YouTube Terms of Service link and applicable user agreement statement.
- YouTube API disclosure and reviewer-page screenshots.
- Feature evidence for the Analytics and reporting request and the truthful private single-operator use case. The Internal company tool category should be selected only if the live form confirms it applies to an individual with no company.
niche-lab doctorshowingnot_requestedand fail-closed status.- Phase 1 completion evidence and a protected-capability fail-closed demonstration.
- Retention documentation and an architecture/data-flow view.
Required screenshots must be captured only after a truthful HTTPS deployment and operator facts are supplied. Current official form guidance calls for readable 1,280 x 720 or higher evidence with the browser address bar for web applications.