Clip Factory Privacy Policy
Clip Factory is an internal video processing and publishing tool. This policy explains how its operator uses the tool, how YouTube authorization is handled, and how locally stored authorization can be removed.
Google Privacy PolicyYouTube Terms of Service
YouTube API Services and permissions
Clip Factory uses YouTube API Services. Google handles sign-in and permission approval. The application requests exactly these two OAuth scopes:
Used to upload operator-authorized videos to YouTube.
Used only to identify the currently authorized YouTube channel. Its title and channel ID are displayed for the operator to review.
Data use and local storage
OAuth credentials are stored locally on the operator's computer and reused for authorized requests. YouTube/Google passwords are never collected or stored. Clip Factory does not maintain a database of YouTube API Data.
Video content and metadata selected by the operator are sent to Google/YouTube only as necessary to perform the requested upload. This includes the video, title, description, visibility and audience setting. Google processes this information under the Google Privacy Policy.
Clip Factory does not sell user data. It does not share OAuth authorization data with advertisers or unrelated third parties. The public website uses no cookies, trackers or analytics. There are no advertising or analytics cookies in this local tool.
Local media and processing files remain on the operator's computer until removed by the operator. The local tool displays channel identity and upload results for the current interaction. It may write request and error information to its local terminal; revocation tokens and Google's revocation response body are not logged.
Data deletion and revocation
The operator can use the in-tool Revoke YouTube Access feature in the Disconnect YouTube section. The tool displays the authorized channel and requires separate confirmation before programmatically revoking Google's authorization.
After successful Google revocation, locally stored OAuth authorization is deleted. This does not delete videos already stored on YouTube. Local videos, processing history and the OAuth client configuration are not deleted by this control.
If Google does not confirm success, local authorization is kept and an error is shown. If Google confirms revocation but local deletion fails, the tool reports that separately so the operator can remove the saved authorization file manually.
As an additional method, revoke the app's access through Google Security Permissions. After manual revocation, stop the local tool and remove its saved OAuth authorization file and any backup copies. Deleting a local authorization file alone does not revoke Google's grant. Remove any separately created backups yourself; the in-tool control deletes the active authorization file only.
Manage or delete uploaded videos separately in YouTube Studio. For questions about operator-held data or deletion, contact zaderoni1@gmail.com.