Privacy Policy
This policy explains how Headstory Animation ("we", "us") handles information in two places: Headstory Uploader, a private desktop tool that publishes and measures the videos of our YouTube channel, and this website.
In short
- Headstory Uploader uses YouTube API Services.
- Its only user is the owner of the Headstory Animation channel, signed in with their own Google Account. It has no other users and never accesses anyone else's account or personal information.
- It works only with the channel's own videos and the channel's own aggregated statistics.
- Sign-in tokens and data stay on the owner's computer and in the owner's private backup. Nothing is sold, shared or used for advertising.
- Access can be revoked at any time at https://security.google.com/settings/security/permissions.
1. YouTube API Services and Google
Headstory Uploader uses YouTube API Services to upload and manage videos and to read statistics of the Headstory Animation channel. By using Headstory Uploader you agree to be bound by the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy (http://www.google.com/policies/privacy).
Headstory Uploader's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
2. Who uses Headstory Uploader
Headstory Uploader is not a public product. It is run only by the owner of the Headstory Animation YouTube channel, on the owner's own computer, to manage that one channel. Nobody else signs in to it, and it does not collect information about viewers, subscribers or any other person.
3. What information the tool accesses
When the channel owner signs in with Google, the tool requests these permissions and receives the following information:
- Sign-in tokens issued by Google, which let the tool act for the channel owner (permissions
youtube.upload,youtube.force-ssl,youtube.readonlyandyt-analytics.readonly). - Basic channel information: the channel's ID and title, used to confirm that the tool is signed in to the correct channel.
- The channel's own videos: the list of videos and their details (IDs, titles, descriptions, publication dates, subtitles, thumbnails, playlists) and their public counts such as views and likes.
- The channel's own statistics from YouTube Analytics and YouTube reporting: aggregated numbers such as views, watch time, average view duration, audience retention, traffic sources, totals by country and region, shares by age group and gender, devices and operating systems, playback locations, impressions and click-through rate, subtitle usage, likes, comments and subscribers gained or lost. These figures are totals, averages and percentages; they do not identify individual viewers, and the tool does not request any information about individual viewers.
The tool does not read the text of comments, messages, the list of subscribers, the owner's email, contacts or any other Google data, and it does not request monetary or revenue data.
The tool also sends to YouTube the content the channel creates: video files, titles, descriptions, translations, subtitles and thumbnails.
4. How the information is used
- To upload the channel's own videos and keep their details up to date.
- To measure how the channel's videos perform, so that we can plan and improve future videos.
- To confirm that the tool is signed in to the right channel and that its access is still authorized.
The information is not used for advertising, profiling, selling, credit or lending decisions, or any purpose other than those listed above.
5. Where it is stored and how it is protected
- Sign-in tokens are stored as files in a private folder of the owner's user account on the owner's computer. They are never published, shared, or uploaded to any website or cloud storage.
- Video details and statistics are stored in a database on the owner's computer. A copy is kept in the owner's private, access-restricted cloud backup so that it can be restored after a computer failure.
- All communication with Google uses encrypted connections (HTTPS). Access to the computer and to the backup is protected by the owner's own account credentials.
6. Sharing
We do not sell, rent, trade or otherwise share information obtained through YouTube API Services with anyone. The information is processed only by:
- Google, which provides YouTube API Services; and
- service providers that work only on the owner's instructions, such as private cloud backup storage and data-analysis software used by the owner. They are not allowed to use the data for their own purposes.
We may disclose information if the law requires it. Headstory Uploader does not allow any third party to serve content or advertisements.
7. How long information is kept, and deletion
- Sign-in tokens are kept for as long as the owner uses the tool.
- Statistics are kept for as long as they are needed to plan the channel's videos. The tool refreshes the stored video details each time it runs, and in any case at least every 30 days, and it confirms at least every 30 days that its access is still authorized.
- If access is revoked, the tool can no longer read or change anything. We then delete the stored tokens and all data obtained through YouTube API Services as soon as possible: within 7 calendar days from the working copies and within 30 calendar days from backup copies.
- You can ask us to delete stored data at any time by writing to the address in Contact; we will do so within 7 calendar days.
8. How to revoke access
Access given to Headstory Uploader can be revoked at any time on the Google security settings page: https://security.google.com/settings/security/permissions. Choose "Headstory Uploader" and remove its access.
9. Cookies and information on devices
Headstory Uploader stores its sign-in tokens and its database only on the owner's own computer, as described above. It does not place cookies or similar technology on anyone's device.
This website uses no cookies, no analytics, no advertising and no third-party scripts. Our web host, currently GitHub Pages, records visitors' IP addresses for security purposes under the GitHub General Privacy Statement; we do not receive or use that information.
10. Children
Headstory Uploader and this website are not directed at children and do not collect information from children.
11. Changes to this policy
If we change how Headstory Uploader uses Google user data, we will update this page before the change takes effect and change the dates at the top.
12. Contact
Questions or complaints about this policy or about Headstory Uploader: 0n17work@gmail.com