Using CF and YouTube
Terms of use
CF — Content Factory is a local Windows desktop app privately used by its sole owner and operator. This site provides information about CF; it has no app download or login. Access for a YouTube reviewer can be arranged with the operator.
YouTube features and your agreement
CF uses YouTube API Services for channel verification, creator-approved video uploads, optional public-video discovery when an API key is configured, and optional requested Analytics. By using CF, you agree to be bound by the YouTube Terms of Service. Also read the Google Privacy Policy and CF privacy policy.
CF's source requires agreement to a configured public privacy-policy version before the workspace opens; changing that version or address calls for renewed agreement. This behavior has not yet been tested end to end with a live Google account. The owner can use manual YouTube Studio without connecting a CF API grant.
The owner controls imported, created, and uploaded media and must have the needed rights to videos, sound, images, and text. Uploads must follow the YouTube Terms of Service and Community Guidelines. CF's suggestions are for review. The owner chooses the destination channel, file, title, description, visibility, audience setting, disclosures, and final upload action for each API upload. Until YouTube approves this project's API Services compliance audit, CF limits API uploads to private visibility. Public, unlisted, and scheduled API publication are unavailable in the current app.
An upload can transfer before YouTube finishes processing it. Check the result in YouTube Studio. CF cannot promise publication, continued availability, or a particular view count. Deleting a CF project or disconnecting CF does not delete YouTube-hosted videos.
Account and deletion controls
Settings offers Revoke access and delete API data to ask Google to revoke CF's saved grants and delete associated API data from the active workspace, current recovery snapshot, and credential vault. Delete local API data only removes those CF records without requesting Google revocation; use it after revoking CF from Google's security permissions page. Finish or cancel an active transfer before either action. If revocation is uncertain, CF keeps a reminder to check Google permissions and pauses API actions until that check is recorded. Recording a check does not itself prove revocation.
The separate Clear selected Studio sign-in control attempts to clear one selected local browser profile and its linked manual confirmations. It does not revoke an API grant. Independent backups and recovery proofs require manual review. The privacy policy explains retention, the seven-day deletion-request process, Google-side revocation, and the limit when the PC or Data drive is unavailable. These controls have not yet been validated with a real grant, private upload, or signed-in Studio session.
For questions or a deletion request, contact Idi0tDev42@gmail.com.