Privacy policy

Information accessed and collected

The application uses YouTube API Services. With authorization, it accesses channel IDs, names, channel statistics and upload inventories; video IDs, titles, descriptions, publication dates, durations, visibility information, thumbnail URLs and statistics; and available channel or video analytics.

Analytics may include views, watch time, average view duration, traffic sources, audience country breakdowns, impressions and click-through rates, device and operating-system breakdowns, playback locations, and estimated revenue. Available daily reporting files may contain additional metrics associated with these report types. These are channel analytics, not a list of individual viewers.

The application stores Google OAuth access and refresh tokens and desktop OAuth client credentials to maintain the authorized connection. It does not collect the Google account password or read Gmail messages. Google handles sign-in on its own pages.

Permissions and purpose

Data is used to identify the selected channel, collect its performance history, investigate content experiments, and review performance across channels the operator manages.

• youtube.readonly: read channel and video information.
• yt-analytics.readonly: read activity analytics and access reporting services.
• yt-analytics-monetary.readonly: read available monetary analytics, including estimated revenue.

These are Google OAuth scope names under https://www.googleapis.com/auth/. The app creates analytics reporting jobs when needed; it does not modify YouTube content.

Storage and security

The desktop app saves analytics and collection snapshots in a local SQLite database and credentials in local JSON files on the operator’s computer. It may retrieve channel thumbnail images for the connection screen. The app does not itself encrypt these local files; access depends on the computer’s security and file permissions. Requests to Google use HTTPS.

The current collector does not send credentials or analytics to this website or to an app-operated cloud database. Any computer backups, synced folders or files copied by the operator are separate copies that also need protection.

Sharing and AI-assisted analysis

The current app has no automatic AI-service integration and does not automatically send analytics to an AI provider. The operator may deliberately share selected analytics files with a third-party analysis service, including an AI assistant, for requested research. Such a transfer is a separate operator action and is subject to that provider’s data-handling settings and terms. Credentials should not be included in analysis files.

The operator does not sell collected Google user data or use it for advertising targeting. Google user data is used for the disclosed research functions, not to train a generalized AI model. Any transfer of Google API data must comply with the Google API Services User Data Policy, including its Limited Use requirements.

Retention, revocation and deletion

The current version retains local snapshots across downloads and has no automatic retention cleanup. Retention is managed manually by the operator; revoking access does not erase files already downloaded.

You can revoke authorization through Google Account third-party connections. Select the corresponding OAuth application and remove its access. This prevents further authorized retrieval with that connection unless you authorize it again.

To remove all locally collected data, close the desktop app and delete its local database and saved credential files, along with any separately saved reports, exported copies or backups you wish to remove. For channel-specific deletion or help identifying the relevant files, contact lorenzkeelprime@gmail.com. The current app does not provide a channel-specific deletion button. Deleting local files does not delete videos or records held by Google.

Website visitors and support messages

This static website has no sign-in, analytics scripts, advertising, contact forms or application-set cookies. Cloudflare hosts the site and may process network information such as IP addresses and request metadata to deliver and secure it. See Cloudflare’s privacy policy.

If you contact the support email, your email address and message are processed to answer your request. Do not email passwords, client secrets or authorization tokens.

Google’s policies and future changes

Google processes information under the Google Privacy Policy. Use of YouTube is also governed by the YouTube Terms of Service.

This page will be updated when the application’s data practices change. New uses of authorized data require appropriate disclosure and consent before they begin.