Privacy Policy
Last updated: 3 September 2026
This policy covers two separate things: the website you are reading, and the private production tooling that Riddled History uses to publish to YouTube. They are described separately because they handle data very differently.
The website collects nothing
riddledhistory.com is a set of static pages. It has no accounts, no login, no comment system and no contact forms.
Specifically, this site does not:
- set cookies, or use local storage or any similar tracking mechanism
- run analytics of any kind
- embed third-party trackers, advertising or social widgets
- ask you for, receive, or store any personal information
Our hosting provider records ordinary web server logs, such as IP addresses and requested pages, as an automatic part of serving the site securely. We do not use those logs to build profiles of visitors, and we do not combine them with any other information.
The production tooling and your Google data
Riddled History is produced with private, purpose-built software that connects to Google’s APIs on behalf of the channel operator’s own Google account only.
This is the important part: the application has exactly one user, its operator. It is not published, not distributed and not offered as a service. There is no circumstance in which it accesses your Google account, your YouTube channel or your data. If you are reading this because you were sent here from a Google consent screen, you are the operator, or the consent screen has been reached in error.
The application requests the following Google OAuth scopes, each for a specific and limited purpose:
| Scope | What it is used for |
|---|---|
youtube.upload |
Uploading finished videos to the operator’s own channel |
youtube |
Setting a video’s title, description, thumbnail and visibility on that channel |
youtube.readonly |
Listing the channel’s own videos so the tooling knows what has already been published |
yt-analytics.readonly |
Reading the channel’s own performance figures, such as view counts and audience retention, to inform editorial decisions |
How that access is handled:
- Credentials stay local. OAuth tokens are stored on the operator’s own machine and are never transmitted to any third party, embedded in any published output, or committed to any code repository.
- The data stays local. Analytics figures retrieved from YouTube are used only to guide the channel’s own editorial decisions. They are not sold, shared or published in identifiable form.
- No other person’s data is touched. The tooling reads and writes only the operator’s own channel.
- Access can be withdrawn at any time from the operator’s Google account permissions page.
Riddled History’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Third-party services used in production
Making a video involves sending our own material — research queries, scripts we have written, and narration text — to third-party services, including AI providers for narration and imagery and public archives for source material. None of this involves any data belonging to visitors to this website, because none is collected.
Children
This site is not directed at children and collects no information from anyone, including children.
Changes
If this policy changes, the revised version will be posted here with an updated date above.
Contact
Questions about this policy, or about a source used in a video, can be sent to contact@riddledhistory.com.