Privacy policy
Last updated: 13 November 2026
Why Then is a small independent studio that makes history videos for YouTube. This policy covers two things: this website (why-then.magorski.com) and the Why Then publishing tool, an internal tool the studio uses to publish videos on its own YouTube channels through the YouTube Data API.
Who we are
Why Then is responsible for the data described here. You can reach us at magorski@gmail.com.
The publishing tool and YouTube API Services
The publishing tool uses YouTube API Services. It is not a public app: nobody outside the studio can sign in to it, and it only acts on YouTube channels the studio owns. Those are the English channel Why Then and its language channels in German, Spanish, French, Portuguese and Hindi.
By using the Why Then publishing tool, you agree to be bound by the YouTube Terms of Service and to this privacy policy. Google's handling of your data is described in the Google Privacy Policy.
What the tool does with YouTube data
When the studio signs in with its own Google account, the tool asks for permission to manage that account's YouTube channel. It uses that permission to:
- upload the studio's videos and their translated language versions;
- set titles, descriptions, tags, language settings, publish dates and privacy settings on those videos;
- upload thumbnails;
- upload and manage subtitle tracks, and translated titles and descriptions, on the studio's own videos;
- create playlists and add videos to them;
- post the studio's own comments (such as a pinned comment with sources) on its videos;
- update the channel's own description and branding.
The tool reads the studio's own channel, video and playlist details, including public view counts, to keep track of what it has published. After posting a comment it reads the video's most recent comment threads to check the comment appeared; those threads can include comments by other people. The tool does not store them, and it does not collect or keep data about viewers, commenters, subscribers or any other YouTube user.
What is stored, and where
- Authorisation credentials. The credentials Google issues when the studio grants access are stored securely on systems the studio controls. They are used only to make requests to YouTube and are never shared.
- Video records. The studio keeps basic details of the videos it has published, such as video IDs, titles, descriptions and status, so it can manage them later.
Nothing is stored on this website, and nothing is stored anywhere else.
Sharing
We don't sell, rent or share data from YouTube API Services with anyone. We don't use it for advertising, and we don't combine it with data from other sources.
Deleting data and revoking access
The studio can revoke the tool's access at any time on the Google security settings page. After revoking access, the studio deletes the stored credentials and the YouTube API data associated with them. If you have a question about data relating to you, email magorski@gmail.com and we will answer, and delete anything we hold, within 30 days.
This website
This website sets no cookies and uses no analytics, trackers, adverts, embedded videos or third-party fonts or scripts. Like any web server, ours records each request (IP address, time, page and browser type) in a log. We use these logs only to keep the site secure and working, and we don't share them.
Children
This website and the publishing tool are not directed at children and collect no information from them.
Changes
If this policy changes, we will update this page and the date at the top.