Last updated 22 August 2026
Privacy policy
This policy describes the current local, single-operator Niche Lab tool and its public compliance site. It does not describe unimplemented future functionality.
Operator
Data controller/operator: Kasparas Marcinskas, acting as an individual/private person.
Privacy and data-rights contact: marcinskas.kasparas@gmail.com
No custom domain is used. The public version of this policy is served from the HTTPS Cloudflare Pages address shown in the browser.
Current service and users
Niche Lab is a private internal research tool used by one individual to support his own YouTube channel. It is not sold, licensed, offered as a service, or made available to customers. It has no public user accounts, subscriptions, customer accounts, or public API features. It does not request Google or YouTube OAuth authorization, collect YouTube login credentials, or access private channel analytics.
The public compliance site is informational. It contains no account creation, login, forms, advertising, behavioral analytics, tracking pixels, or application-set cookies.
Because no external user can currently access API-client features, there is no public onboarding or privacy-acceptance flow. If external access is introduced, users must be presented with and agree to the current privacy policy before API-client features become available.
YouTube API data
Niche Lab uses YouTube API Services for public, non-authorized research. Current API data may include:
- video and channel identifiers;
- video titles, descriptions, publication timestamps, duration, language, and live-broadcast state;
- channel names and public channel metadata;
- current public video and channel statistics; and
- operator-created query, rank, run, request, provenance, and manual-review records.
The tool uses this information to build a reproducible candidate inventory, enforce exact date/duration criteria, monitor metadata quality and freshness, and support an operator's editorial research. It does not sell or share API data with customers or external users.
Storage, refresh, retention, and deletion
- Current metadata
- Public titles, creator/channel names, descriptions, and other standard metadata are refreshed or deleted within 30 days.
- Current statistics
- Public current statistics follow the same 30-day refresh-or-delete rule while Analytics and reporting permission is not accepted.
- Provenance and notes
- Project-generated run IDs, configuration hashes, request records, and manual notes may be retained under project policy when they do not reproduce expired API data.
- Future approved classes
- If YouTube explicitly accepts the requested scope, only accepted public statistical fields and derived metrics may use retention of up to 36 calendar months. Titles, creator names, descriptions, and comment text would remain on the standard refresh/deletion schedule.
Revocation, expiration, a scope change, or failed revalidation disables protected processing and requires applicable retention handling. Current permission state is not_requested; extended retention is not enabled.
Third-party services
Niche Lab uses YouTube API Services and is subject to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.
The public compliance site is hosted by Cloudflare Pages. Cloudflare may process ordinary network information such as IP addresses and request logs to deliver and secure the site. See Cloudflare's Privacy Policy. Niche Lab does not add application analytics or tracking to the site.
No third party currently serves advertisements, analytics, or embedded content through this site.
Requests and changes
There is currently no public user account or authorized user data to export or delete. Questions, complaints, or applicable data-rights requests can be sent to marcinskas.kasparas@gmail.com. A verified request will be handled according to applicable law and the project's deletion obligations.
If OAuth, public accounts, new data categories, advertising, analytics, or cookies are introduced later, this policy and any required consent/revocation flow must be updated before those features become available.