Clipper Privacy Policy
Clipper ("the app") is a private, single-user software tool operated by its owner to publish short video clips to the owner's own YouTube channels. It is not offered to the public and has no users other than its owner. This policy describes what data the app accesses through Google APIs and how that data is handled.
YouTube API Services
Clipper uses YouTube API Services to access the owner's YouTube channels. By using the app, the owner agrees to be bound by the YouTube Terms of Service. Google's own handling of data is described in the Google Privacy Policy.
Data the app accesses
With the owner's consent through Google sign-in, the app uses the YouTube Data API to:
- upload videos to the owner's YouTube channels and set their title, description, tags and privacy status;
- schedule an uploaded video to go public at a chosen time, and change its title or description afterwards;
- set a video's thumbnail to the cover image the app made for it;
- delete a video the app uploaded, when the owner takes a clip down;
- read the status, processing state and view, like and comment counts of the videos the app uploaded, and the name of the channel that signed in.
With the same consent the app uses the YouTube Analytics API to read, for the owner's own channels only, watch time, average view duration, shares and subscribers gained for the videos it uploaded.
The app does not read the owner's email, contacts, watch history, or any other Google data, and it never accesses any account other than the owner's.
How the data is used
Uploaded videos are clips the owner has created and approved. Video ids, statuses, counts and analytics are stored to track what the app has posted and to measure which clips perform well. Nothing is used for advertising, profiling, or resale, and nothing read from YouTube is altered or shown out of context.
Where the data is stored
The Google OAuth token for each channel and all ids, statuses, counts and analytics are stored locally on the owner's own computer in a private database. Nothing received from Google APIs is sent to any server operated by the app's owner or by any third party.
When the owner turns on cross-posting, the app sends the clip video files it made, with their captions, to Buffer, which posts them to the owner's own TikTok, Instagram and Facebook accounts. Those files are the owner's own content; no data received from Google APIs goes to Buffer or any other service.
Sharing
The app does not share, sell, or transfer Google user data to anyone. It uses a single Google Cloud project and does not spread its API use across projects to obtain more quota.
Limited Use disclosure
Clipper's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
Data is kept only as long as the owner keeps the app installed. Access can be revoked at any time at myaccount.google.com/permissions, which invalidates the stored token immediately. Stored YouTube data (video ids, statuses, counts and analytics) can be deleted at any time by deleting the app's local data folder on the owner's computer; the app keeps no copy anywhere else and holds no data about any YouTube user other than its owner. The app does not use cookies and runs no web tracking.
Changes
If this policy changes, the updated version will be posted at this address with a new effective date.
Contact
Questions about this policy can be sent to clipperoverlord@gmail.com.