ChannelForge Privacy Policy

Last updated 27 August 2026

Scope

This policy explains how ChannelForge ("the app") accesses, uses, stores and deletes Google and YouTube data for accounts and channels explicitly connected by the app's operator.

Data ChannelForge accesses

How Google user data is used

Google user data is used only to provide ChannelForge's channel-management, publishing, analytics and reporting functions to the account holder who authorized access. The app does not use Google user data for advertising, does not sell it, and does not share it with data brokers or unrelated third parties. It is not used to train generalized artificial intelligence or machine-learning models.

ChannelForge's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and security

ChannelForge is a local desktop application. OAuth client secrets and refresh credentials are stored in the Windows Credential Manager under the operator's Windows account. Channel records, analytics, queue state and operational history are stored in a local database controlled by the operator. ChannelForge does not place OAuth credentials in this website or in a public source repository.

Retention and deletion

Channel data is retained while the channel remains connected or while the operator needs its operational history. Removing a channel from ChannelForge deletes its stored refresh credential and channel-scoped application records. The operator may also request deletion using the contact address below.

Revoking access

Access can be withdrawn at any time from Google Account permissions. Revocation prevents ChannelForge from obtaining new access tokens. The channel can also be removed inside ChannelForge to delete its locally stored credential and channel-scoped records.

Changes

This policy will be updated here if ChannelForge's data practices materially change.

Contact

Privacy questions or deletion requests: deident03@gmail.com