Last updated: 1 November 2026

This is the privacy policy for Creative Workspace, the private content tool that runs behind radioactive-chicken.com. It covers one thing: what that tool does with Google and YouTube data when it uploads a video to a YouTube channel. It does not cover the public blog at radioactive-chicken.com.

Who is responsible for this application

The application is Creative Workspace. The developer and operator is the owner of radioactive-chicken.com, a personal blog and hobby site, not a company. There is one operator, and there is one person with access to the data described on this page.

Official contact for everything on this page — privacy questions, access requests, deletion requests and complaints: [email protected] (written out, for anyone reading this by machine: webmaster at radioactive-chicken dot com). A real person reads that inbox.

What this application does

Creative Workspace prepares an article for publication and, if you ask it to, uploads a video file to a YouTube channel you have authorized. The title, description, tags, category and visibility are written and reviewed by a person before anything is sent. Videos are uploaded as private drafts. The application never publishes anything publicly on YouTube. That decision belongs to the channel owner, made on YouTube itself.

YouTube API Services

Creative Workspace uses YouTube API Services. By using the YouTube features in Creative Workspace, you agree to be bound by the YouTube Terms of Service.

YouTube’s own handling of your data is described in the Google Privacy Policy. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The YouTube API Services are also governed by the YouTube API Services Terms of Service and the YouTube API Services Developer Policies.

What Google user data this application accesses

When you grant authorization through Google’s OAuth consent screen, Creative Workspace accesses exactly this:

• The identity of the Google Account that granted the authorization — the account’s basic profile identifying information, so the application knows which account it is acting for.
• The YouTube channel that account owns, so the application knows where an upload is going.
• Permission to upload videos to that channel, which is the scope youtube.upload.

That is the complete list. Creative Workspace does not request access to your Gmail, your Google Drive, your Contacts, your Calendar, your Google Photos, or any other Google service. It does not request permission to read your YouTube watch history, your subscriptions, your playlists or your comments. It never asks for, collects or stores your Google Account password or any other YouTube login credentials.

What Google user data this application stores

• OAuth access and refresh tokens. These are what keep the authorization alive between sessions. They are credentials, and they are treated as credentials.
• The video file being uploaded and the metadata you approved for it.
• The YouTube video ID returned after a successful upload, so the article it belongs to can point at its own video.

Nothing else from your Google Account is stored. The application keeps no copy of your channel’s videos, no copy of your comments, and no copy of your subscriber or analytics data.

How Google user data is used

It is used to do the thing you asked for and nothing else:

• To authenticate to YouTube as the authorized channel and perform the upload you requested.
• To apply the metadata you reviewed to that upload.
• To record the resulting video ID so the upload can be referenced from the article it was made for.

There is no secondary purpose. There is no profiling, no behavioural analysis, no scoring, and no building of a database about you. The data is not used to provide or improve features for anyone other than the account that authorized it.

How Google user data is protected

This is a small personal tool, so the protection measures are simple, and they are all in force:

• All traffic between the application and Google’s APIs, and between your browser and the application, travels over HTTPS with modern TLS. Nothing about your account is sent over an unencrypted connection.
• OAuth tokens and other stored data live server-side only. They are never written into client-side JavaScript, never placed in URLs, and never exposed in browser storage.
• The stored data sits on a single private server administered by one person, protected by account-level authentication. There are no third-party staff, contractors or support vendors with access to it.
• Server access is restricted to that single operator account, and the server software is kept current with security updates.
• Tokens are deleted when the authorization ends or when you revoke it, whichever comes first, rather than left to sit on disk.
• There is no endpoint in this application that returns Google user data to any third party, because no such feature exists.

Who Google user data is shared, transferred or disclosed to

One recipient, and only because an upload cannot happen without it:

• Google and YouTube. When you start an upload, the video file and the metadata you approved are transmitted to YouTube API Services. That transfer is the function you asked for. What YouTube then does with it is described in the Google Privacy Policy.

Beyond that, no one. Google user data is not sold, rented, licensed or handed to any third party. It is not transferred to data brokers, information resellers, advertisers, ad networks, analytics companies, credit or lending services, or any party conducting surveillance. It is not disclosed to other users of this site. The one theoretical exception is a legally binding court order or equivalent lawful demand, which has not happened and would be answered honestly if it ever did.

What this application never does with Google user data

These uses are prohibited, and none of them take place:

• No targeted, personalised, retargeted or interest-based advertising, and no user advertising at all.
• No sale to data brokers or provision to information resellers.
• No use in determining credit-worthiness, and no lending use of any kind.
• No building of databases or audience segments for any of the above.
• No use to develop, improve or train generalised machine-learning or artificial-intelligence models, personalised or non-personalised. Google user data is not a training set, and it is not fed to any model.
• No resale or redistribution of the data in any form.

Retention — how long data is kept

• OAuth access and refresh tokens: kept only while the authorization behind them is active. They are deleted when you revoke access, and they are deleted if they stop working.
• YouTube API data cached by the application: deleted or refreshed within 30 calendar days, as the YouTube API Services Developer Policies require. Nothing from the API is held indefinitely.
• The YouTube video ID and the uploaded video file: kept as part of the article record for as long as the article exists, because that is what makes the article coherent. They are removed when the article or the video is removed.

When a retention period above expires for a given type of data, the data is deleted. It is not archived elsewhere first.

Deletion — how to have your data removed

You may request deletion of any data this application holds about you, at any time, for any reason, with no justification required. Email [email protected] with the subject line “data deletion” and say which Google Account is involved.

• Stored data is deleted within 7 calendar days of the request, which is the deadline the YouTube API Services Developer Policies set and the one we hold ourselves to.
• You get a reply confirming the deletion once it is done.
• If you would rather not email, revoke the application’s access from your Google Account and the tokens are invalidated immediately. See the next section.

One thing to be clear about: deleting data held by this application does not delete anything on YouTube. Videos, comments, playlists and channel data that exist on YouTube have to be deleted on YouTube itself, by the channel owner, through YouTube’s own controls.

Revoking access

You can revoke Creative Workspace’s access to your Google Account at any time from the Google security settings page. Once you revoke it, the stored tokens stop working and the application can no longer act on your behalf. YouTube may also revoke access to YouTube API Services at any point, independently of anything here.

Cookies, advertising and third-party content

Creative Workspace’s YouTube features set no cookies of their own and serve no advertising. No third party serves content or ads through them. If a YouTube video is embedded somewhere on radioactive-chicken.com, that player is served by YouTube, and YouTube collects data under its own policies, which this policy does not control. The site also sits behind Cloudflare, which processes requests as any content delivery network does, under Cloudflare’s own privacy terms.

Children

Creative Workspace is not directed at children, is not intended for use by anyone under 13, and has no features aimed at them. Its use is limited to the channel owner and to people the owner has explicitly authorized.

Your rights and complaints

You can ask what data is held about you, ask for a copy of it, ask for it to be corrected, or ask for it to be deleted. Email the address above and the request is honored. If you are not satisfied with the answer, you are entitled to complain to your local data protection authority, and nothing here is meant to take that right away from you.

Changes to this policy

If this policy changes, the date at the top changes with it. If what is accessed, stored, used or shared ever changes, that change is disclosed here before the new use begins, and users are asked to consent to the updated policy before their data is used in any new way.

Not affiliated with YouTube or Google

YouTube and Google are trademarks of Google LLC. Creative Workspace and radioactive-chicken.com are not endorsed by, sponsored by, or affiliated with YouTube or Google.