Privacy Policy
This policy explains what data YT-Content-Engine ("the application") accesses, how it is used, and how to remove access. The application is a private tool used only by its operator to manage their own YouTube channel.
YouTube API Services
The application uses YouTube API Services. By using the application you agree to the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.
Data the application accesses
When the operator connects a Google account, the application requests only these permissions:
- YouTube upload (
youtube.upload): to upload approved clips and set their title, description, and schedule. - YouTube read-only (
youtube.readonly): to read the connected channel's details and its uploaded videos. - YouTube Analytics read-only (
yt-analytics.readonly): to read performance metrics such as views and watch time for the connected channel. - Google Drive, app-created files only (
drive.file): to store and retrieve archive copies of recordings that the application itself creates. The application cannot see any other files in Drive.
The application also processes gameplay recordings that the operator uploads to it.
How the data is used
- Recordings are analysed to find highlight moments, turned into clips, and uploaded to the operator's channel after the operator approves them.
- Channel and analytics data are used only to track how published clips perform and to improve which moments are selected.
- Data is not sold, not used for advertising, and not shared with anyone except the service providers listed below, which process it only to run the application.
Limited Use
The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Service providers
- Cloudflare: hosting, databases, and temporary media storage.
- TwelveLabs: video-understanding analysis of gameplay recordings.
- Google: YouTube publishing and analytics, and the Drive archive.
Google account data (channel details, analytics, and access tokens) is not sent to TwelveLabs.
Storage, retention, and security
- Access tokens are stored encrypted as secrets in Cloudflare and are never placed in source code.
- Working copies of media in Cloudflare storage are deleted once they are archived and no longer needed for processing.
- Archive recordings stay in the operator's Google Drive until the operator deletes them.
- Stored analytics and clip records are kept while the channel is active and deleted on request.
Cookies
These public pages set no cookies. The private application dashboard uses only the sign-in cookie needed to restrict access to the operator.
Removing access and deleting data
Access can be revoked at any time from Google Account → Third-party connections. After revocation the application can no longer upload, read analytics, or access its Drive files. To request deletion of stored data, email the address below; it will be deleted within 30 days.
Changes
Changes to this policy are published on this page with a new effective date.