Privacy policy
Privacy Policy
Summary
Plain Receipts Uploader is a private tool used by one person, the owner of the Plain Receipts YouTube channel, to upload and manage videos on that channel. It uses YouTube API Services.
It accesses only that channel's own data, uses it only to upload and check the channel's videos, keeps it on the owner's computer, and does not sell it or share it with advertisers.
Who this policy covers
This policy covers the Plain Receipts Uploader app and this website. The app is not offered to the public: the only Google account that signs in to it is the account that owns the Plain Receipts channel. By signing in to the app, that user agrees to this policy, and to the YouTube Terms of Service.
Google's own handling of your data is described in the Google Privacy Policy.
Permissions requested
The app asks Google for two YouTube permissions (OAuth scopes):
https://www.googleapis.com/auth/youtube.upload: shown by Google as “Manage your YouTube videos”. Used to upload videos and set their thumbnails.https://www.googleapis.com/auth/youtube: shown by Google as “Manage your YouTube account”. Used to change settings on an existing video (for example, making it public), to read videos' status and settings, to list recent uploads, and to add captions or playlist entries.
The app does not ask for access to Gmail, Google Drive, contacts or any other Google service.
What Google and YouTube data the app accesses
| Data | Used for |
|---|---|
| The signed-in channel's ID | Confirming that a video belongs to the Plain Receipts channel, and finding its list of uploads. |
| Titles and IDs of the channel's most recent uploads (up to 50) | Checking that a video is not uploaded twice. |
| Details of videos the app uploaded or is asked to update: title, description, tags, category, language, privacy setting, processing status, length, picture quality, thumbnail sizes, region and age restrictions, and the AI-content disclosure | Confirming that an upload finished and that its settings match what was intended, before and after it is made public, and keeping the upload log's record of the video current. |
The app does not read comments, messages, subscriber lists, analytics or revenue reports, and it does not access any other channel or Google account.
The app also sends the channel's own content to YouTube: video files, thumbnails, captions and the text settings listed above.
How the data is used
Data obtained through YouTube API Services is used only to:
- upload videos to the Plain Receipts channel and set their details;
- avoid duplicate uploads;
- check that each upload and each change to a video's visibility worked as intended;
- keep the upload log's record of each video current (see below).
It is not used for advertising, profiling, selling, or training AI models.
Sign-in tokens and how they are stored
When the channel owner signs in through Google's own sign-in page, Google issues an OAuth token. The token lets the app act on the channel without a new sign-in every time.
- It is saved as a file on the owner's computer, inside the tool's folder. It is not uploaded to any server, website or cloud storage by the app.
- That folder is excluded from version control (Git), so the token is not committed or published with the tool's code.
- The tool does not display the token in its output or logs.
- The file is protected by the computer's user-account permissions. The app does not add its own encryption to the file, so anyone with access to that computer account could read it.
- The app's Google client configuration file is kept outside the tool's project folder.
The token stays on the computer until it is deleted or until access is revoked (see Your choices). Google may also stop accepting it, for example after six months without use.
What is stored locally, and for how long
- The sign-in token, as described above.
-
An upload log on the owner's computer, used to prevent duplicate uploads. For each upload it
records two kinds of information:
- The channel's own records: a fingerprint (hash) of the video file, the title the owner chose, whether the upload succeeded, and when. These are kept until the owner deletes them.
- Data from YouTube: the video ID YouTube assigned, any error message YouTube returned, and the video's current title, privacy setting, upload and processing status, picture quality and length. Only the latest version is kept. Each refresh replaces it, and no history of it is built up.
- Publishing records in the owner's project files, such as checklists, reports and approval notes. These hold only the channel's own information: what was made, approved and sent, file fingerprints, and what the owner saw in YouTube Studio. They refer to a video by a short name in the upload log rather than by its YouTube video ID, and they hold no data from the YouTube API.
How data from YouTube is kept current, or deleted
- A maintenance check runs once a day on the owner's computer while it is on and the owner is signed in to it. If it was missed, it runs at the next opportunity.
- When the app's access still works, the check reads each stored video back from YouTube and replaces the stored data with the current version. A video that YouTube no longer returns on the channel has its YouTube data deleted.
- Only a successful read counts as a refresh. If the read fails (for example, because access was revoked or the sign-in expired), nothing is extended. Data that has not been refreshed for 29 days is deleted by the next check, or the next time the app opens its upload log, whichever comes first. If the computer is off at that point, the deletion happens when it is next running.
- Duplicate protection keeps working after YouTube data is deleted, because it relies on the file fingerprint, which is the channel's own record.
No YouTube data is stored on this website or on any other server run for the app.
Sharing and disclosure
- The app does not sell, rent or trade any data, and does not share it with advertisers or data brokers.
- Requests go directly from the owner's computer to Google's YouTube Data API over encrypted (HTTPS) connections.
- To confirm that a public video can be watched by anyone, the app also makes one request to YouTube's public embed-information service (oEmbed) without signing in. That request contains only the public video link.
- AI assistant. The channel owner runs the tool with the help of an AI coding assistant, Claude Code by Anthropic. The assistant can read the tool's on-screen output, which can include video titles, video IDs and upload status. This is covered by Anthropic's own terms and privacy policy. Claude Code also keeps its own session history on the owner's computer, which can contain that output. The tool does not display sign-in tokens in that output.
- Data may be disclosed if required by law.
This website
This website has no sign-in, sets no cookies, and loads no analytics, advertising or third-party scripts. It is hosted on Cloudflare Pages. Like any web host, Cloudflare processes standard technical information (such as IP addresses) to deliver the pages, under Cloudflare's privacy policy.
Your choices: revoking access and deleting data
- Revoke access at any time on the Google security settings page (Third-party apps and services). Choose “YT Automation” and remove its access. The app then can no longer act on the channel, and the stored token stops working.
- The app has a command that deletes all YouTube data from the upload log immediately, and the owner can delete the token file and the upload log at any time. A request to delete stored data, sent to the contact address below, is carried out within 7 days.
- If access is revoked, the app can no longer refresh what it stored, so the YouTube data in the upload log is deleted once it has gone 29 days without a refresh, as described above.
- Videos already uploaded stay on YouTube until they are removed in YouTube Studio. The app does not delete them.
Children
The app is a private tool for one adult channel owner. It is not directed at children and does not knowingly collect children's data.
Changes to this policy
If the app's use of data changes, this page will be updated and the “Last updated” date above will change.
Contact
Questions about this policy, or requests about data: plainreceipts.contact@gmail.com