Last updated: 17 October 2026
In short
- We set no cookies ourselves, and this website runs no scripts and has no analytics, advertising or forms. Our host may set one security cookie, see section 2.
- Our app for YouTube works only with our own channel. Nobody else can sign in to it.
- We never sell data and never use it for advertising.
- Questions: regfromplanning@gmail.com
1. Who we are
Reg from Planning is the YouTube channel @RegFromPlanning, a small independent project. Reg is an AI character. The people behind the project produce and check every episode. In this policy, “we” means the people who run the project.
We are responsible for the data described here. You can reach us at regfromplanning@gmail.com.
2. This website
- Nothing to track you. We set no cookies ourselves. No analytics, no advertising, no embedded content from other sites, no scripts and no web fonts. We store nothing on your device.
- Hosting. Our hosting provider, Cloudflare, delivers these pages. To do so, and to protect the site against attacks, it processes technical data such as your IP address, your browser type and the page you asked for. If it suspects automated traffic, Cloudflare may set a strictly necessary security cookie. See Cloudflare’s privacy policy.
- Email. If you email us, we use your address and your message only to reply. Messages stay in our mailbox, which Google provides (Gmail), until we no longer need them. We delete them sooner if you ask.
3. Our app for YouTube
We run a small private app, also called Reg from Planning, that uses the YouTube API Services. It runs only on the project’s own computer and signs in only with the Google account that owns our channel. It is not offered to the public, and nobody else can use it.
YouTube is a Google service. Anyone who uses our app agrees to be bound by the YouTube Terms of Service. The same terms apply when you watch or comment on our videos on YouTube. How Google handles your data is set out in the Google Privacy Policy.
3.1 What the app accesses
| Data | Google permission | Why we use it |
|---|---|---|
| Basic details of our own channel: name, handle, ID, number of videos and subscribers, channel status | youtube.force-ssl |
To check that the app is connected to the right channel |
| Our own videos: titles, descriptions, tags, thumbnails, captions, playlists, and their public counts of views, likes and comments | youtube.force-ssl |
To upload new episodes as private videos, to add thumbnails, captions and playlist entries, to publish episodes and update their details, and to read their public counts for our statistics. A person approves every episode before it is published, and every change to a published episode. |
| YouTube Analytics and Reporting data for our own channel, for example views, watch time, audience retention, impressions and click-through rate, traffic sources, playback locations, device types, likes, shares, subscribers gained and lost | yt-analytics.readonly |
To learn which episodes work and to make better ones. These figures are totals. They do not tell us who watched. |
| Public comments on our own videos, with the commenter’s public channel name | youtube.force-ssl |
To read feedback and to reply. A person approves every reply before it is posted. |
The app accesses no other Google data: no email, contacts, files or payment details, and no private data of other channels or of viewers.
3.2 How we use it
We use this data only to run and improve our own channel, as described in the table above. We do not use it for advertising, we do not sell it, we do not use it to judge anyone’s credit-worthiness, and we do not build profiles of viewers. We do not use it to develop, improve or train general-purpose AI or machine-learning models.
3.3 Who we share it with
- No one who buys or advertises. We do not sell, rent or trade data from Google, and we never pass it to advertising platforms or data brokers.
- AI processing. We use Anthropic’s Claude AI models to analyse our statistics and to draft replies to comments. For each task we send only what it needs, for example totals for an episode, or the text and public name of one comment.
- Our code repository. Copies of the aggregated statistics may be kept in our private code repository, hosted by GitHub, which only the project can access. Access tokens are never stored there.
- Google and YouTube receive what we upload, as part of using their services.
- The law and security. We would disclose data only if the law requires it, or to investigate abuse or a security problem.
3.4 Storage, security and deletion
- The app’s access tokens are stored only in a file on the project’s own computer. They are never placed in our code repository, never shared and never sent anywhere except to Google.
- YouTube Analytics and Reporting data, and statistics such as view, like and comment counts, are kept for as long as we need them to compare episodes. At least every 30 days we confirm that the app’s access is still authorised, as the YouTube API Services Developer Policies require.
- Other data from the YouTube API Services, such as comments and video details, is refreshed or deleted within 30 days.
- If the app’s access is revoked, we delete the data it has stored from the YouTube API Services within 30 days.
- If you would like us to delete data about you, for example one of your comments that the app has stored, email us and we will do so within 7 days. To remove the comment from YouTube itself, delete it on YouTube.
3.5 Revoking access
In addition to the deletion rules above, the owner of a Google account can revoke the app’s access to their data at any time on Google’s security settings page: security.google.com/settings/security/permissions, also available at myaccount.google.com/permissions. Only our own channel’s account uses the app, but the option is always there.
3.6 Limited Use
Reg from Planning’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Advertising and content from others
Neither this website nor our app shows advertising or lets third parties serve content. YouTube may show adverts on our videos under its own terms. We have no control over that.
5. Cookies and your device
We place nothing on your device. We set no cookies ourselves and use no local storage. Our app runs only on our own computer and stores its data there. For Cloudflare’s security cookie, see section 2.
6. Children
Our videos are not made for children, and we do not knowingly collect data about children.
7. Your rights
Depending on where you live, you may have the right to ask what data we hold about you, to have it corrected or deleted, to object to its use, and to complain to a data protection authority. Email us and we will answer within 30 days.
8. Changes
If we change how we handle data, we will update this page and the date at the top before the change takes effect.
9. Contact
Questions or complaints about privacy: regfromplanning@gmail.com.