Privacy Policy for PixelCursor Analytics

Last updated: October 15, 2026

This policy covers PixelCursor Analytics, including its local analytics and private-upload tools, operated by PixelCursor for its own YouTube channel. It also describes visits to these documentation pages.

Information accessed and purpose

With the channel owner's Google OAuth consent, the analytics tool accesses channel and video identifiers, video titles and aggregate YouTube Analytics data such as views, watch time, average viewing duration, retention, likes and subscriber gains. The operator uses these reports to understand channel performance and improve video production. The tools do not request viewer identities, Google passwords, Gmail or contacts.

The upload tool reads the authorized channel identity and upload status. It transfers operator-selected video files, thumbnails and metadata, including titles, descriptions, tags, language, audience and synthetic-content declarations, to YouTube. Uploads are private; public publication is performed separately by the owner in YouTube Studio.

Permissions and control

Analytics requests the yt-analytics.readonly and youtube.readonly permissions. Uploads use a separate authorization with youtube.upload and youtube.readonly. The underlying Google permissions may permit more actions than the toolkit performs. The toolkit does not provide a command to publish videos publicly or delete YouTube videos.

Local storage and security

OAuth client configuration, access and refresh tokens, and resumable-upload state are stored on the operator's computer. Credential and upload-state files are restricted to the local user and kept outside source repositories. Reports, selected media and production metadata are also stored locally. Reports include their reporting dates. This public website does not host tokens, private reports or uploaded media.

Sharing and third-party processing

Requests and selected uploads are transmitted to Google and YouTube over HTTPS to provide the requested features. At the operator's direction, relevant report excerpts may also be processed by an AI assistant used in the production workflow, such as OpenAI or Anthropic, to help interpret channel results. This is limited to the authorized analysis task; Google credentials are not intentionally supplied to these services. Their applicable account terms and data controls also govern that processing.

Google user data is not sold, used for advertising or supplied for training general-purpose AI models by this toolkit. Its use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The tools use YouTube API Services. Google's processing is described in the Google Privacy Policy. AI-service policies are available from OpenAI and Anthropic.

Retention and deletion

Credentials are retained while the integration is used. Upload state is retained to resume transfers and prevent duplicate uploads. The operator reviews locally saved API data and authorization at least every 30 days and refreshes or removes data as required by YouTube's policies. This is a locally managed workflow, not an automatic background deletion service.

The owner can remove local credentials, upload state and reports at any time. Deletion requests are handled as soon as possible and within seven days. If access is revoked, related stored API data is removed as soon as possible and within 30 days. Operator-created source videos are distinct from retrieved API reports. Deleting local files does not delete videos or data held by YouTube, or copies previously supplied to another service; those must be managed with the respective service.

Revoke access

Use Google Account connections to revoke PixelCursor Analytics access. Revocation prevents further authorized API access but does not itself erase existing local reports or publish/delete any video.

Visiting this website

These static pages use no analytics scripts, advertising trackers, embedded YouTube players or cookies. The hosting server processes connection data, including IP address, request path, time and browser information, to deliver and protect the website. Access logs are rotated daily with 14 rotated files retained. External links connect to their respective providers only when followed.

Contact and changes

For privacy questions or deletion requests, contact the operator through einambitionierterprogrammierer@gmail.com or the support contact displayed in Google's consent screen. Please do not send passwords or access tokens by email. The owner of this personal-use installation can also delete local data directly.

Changes to these practices will be reflected here. New purposes or permissions require renewed consent where applicable.