1. Who is responsible
The party responsible for Branchpoint Earth Pipeline and for the data handled through it is the operator of the Branchpoint Earth channel — the person who runs the desktop application on their own Windows computer and decides what is published on that channel.
This application is not operated by Google, YouTube, or any channel management service. It is not offered to manage channels that belong to third parties.
Contact for privacy questions, complaints, and deletion requests: [email protected].
2. Purpose of this policy
Branchpoint Earth Pipeline is a private Windows desktop tool whose purpose is to prepare publication files and deliver approved content to the Branchpoint Earth channel using YouTube API Services. This policy exists to describe, in concrete terms:
- which data the tool accesses through YouTube API Services;
- what the tool does with that data;
- what is stored locally on the operator's computer;
- what is transmitted to Google/YouTube and when;
- how to revoke access and how to request deletion of the data the tool stores.
Where this policy describes the tool, it describes the version currently in use. It does not describe features that have not been built.
3. Data accessed
When the operator connects an account and uses the tool, the integration module accesses the following categories of data through YouTube API Services:
Channel identification data
The module queries the channel identifier, the channel name, and the channel statistics in order to identify the connected account and verify the identifier of the channel the operator intends to publish to.
Playlists
The module queries playlists on the account, in order to locate the playlist configured for the pipeline or to create it when it does not exist.
Upload identifiers and API responses
When the operator executes an authorized publication, the module receives the identifiers and the API responses associated with the uploads it performs (for example, the identifier of the uploaded video). These responses are used to complete the submission and to record it locally.
Publication content chosen by the operator
The video files, thumbnails, subtitles, and the metadata selected by the operator (title, description, tags, language, visibility, and scheduling) are input to the tool and are transmitted to Google/YouTube at the moment of the authorized publication, as described in the next sections.
The module does not access Gmail, Google contacts, or files stored in Google Drive. It does not read or write anything on YouTube beyond what is needed for the functions described on the home page.
4. How data is used
The data listed above is used only for the following purposes:
- Identify the authorized channel and verify its identifier before any publication is prepared;
- Deliver approved publication packages — the video, thumbnail, subtitles, and metadata the operator approved — to the Branchpoint Earth channel;
- Attach uploads to the configured playlist, after querying or creating that playlist;
- Keep local records of the submissions performed and their scheduling, so the operator has an on-disk history of what was sent and when.
Data obtained from Google is not used for advertising, is not used to build profiles for anyone, and is not used to train artificial intelligence models. The integration module does not sell data obtained from Google.
6. Local storage and security
The tool stores the following items locally, on the Windows installation where it runs:
- the identifier of the connected channel;
- the local records of the publications performed, including scheduling information;
- the OAuth access tokens and refresh tokens used to call YouTube API Services. These tokens are kept in a JSON file inside the application's local installation folder.
The current version does not offer its own encryption of that JSON file. This policy does not claim encryption, certification, audit, or any automatic security feature that the tool does not implement. Protecting the computer, controlling who can log in to it, setting file and folder permissions, and keeping appropriate backups are the operator's responsibility.
No OAuth token, API key, or credential file is included in the code or in the hosting of this public website. Nothing on this site can access the operator's local files.
API calls made by the tool travel over HTTPS to Google's endpoints, as required for the use of YouTube API Services.
7. Retention
Retention is governed by the fact that the tool runs locally and keeps its records on the operator's own computer:
- The channel identifier and the local submission and scheduling records are kept for as long as the tool is in use and the operator wants to keep that submission history.
- The OAuth access and refresh tokens are kept only as long as needed to perform the actions the operator authorizes. They are deleted when access is revoked or when deletion is requested — within seven calendar days, as described in the deletion procedure below — or when the tool is removed from the computer.
- Videos published on YouTube are held by YouTube under Google's own retention policies, which are outside this application's control.
This website stores no application data at all. There is no cloud copy under this application's control.
8. Revoking access
The operator can revoke the permissions granted to this application at any time in Google's account security settings:
https://security.google.com/settings/security/permissions
Revoking access has the following effects, stated plainly:
- It prevents future authorized operations: after revocation, the tool can no longer call YouTube API Services on that account, so no further uploads or playlist changes are possible.
- It does not automatically delete the local files on the operator's computer. The JSON token file and the local submission records remain until they are deleted by the operator or as part of a deletion request.
- It does not remove videos that were already published on YouTube. Published content is removed on YouTube itself, by the operator.
- The current version of the tool does not implement automatic deletion of all local records after revocation. This policy does not describe that capability as existing. After revocation, the operator manually deletes the local tokens and API-derived records within seven calendar days, as described in the next section.
9. Deletion procedure
Deletion requests can be sent to [email protected]. The operator manually deletes the locally stored OAuth tokens and the Google/YouTube API-derived records as soon as possible and within seven calendar days after receiving a deletion request or after access is revoked. This is an operator-run procedure.
The current software does not automatically purge all local records following revocation. The operator confirms completion of a deletion request by email.
This procedure covers authorization tokens, the stored channel identifier and API-derived publishing records. It does not delete original video files, scripts or drafts created by the operator, and it does not remove videos already published on YouTube. Published videos are managed separately in YouTube Studio.
A Data obtained through the API, and OAuth tokens
Within the scope of the procedure above, deletion covers the OAuth access and refresh tokens kept in the local JSON file, the stored channel identifier, and the API-derived publishing records (the local submission and scheduling records). These items are deleted within seven calendar days of a deletion request or of revocation of access.
B Original material and published videos
Deleting the tokens and API-derived records does not delete the operator's original video files, scripts or drafts, and it does not remove videos already published on YouTube. Published videos are managed separately in YouTube Studio; original files remain under the operator's direct control.
If you need both — deletion of the locally stored API data and tokens, and removal of published videos — say so in the request; they are handled as two separate actions.
10. Permissions requested
The integration requests the following permissions when the operator connects an account. They are listed here exactly as defined by Google:
https://www.googleapis.com/auth/youtube.upload- Used to send the approved publication packages (videos and their selected metadata) to the channel.
https://www.googleapis.com/auth/youtube- The YouTube Data API scope for managing the channel's YouTube content — including the playlist queries and creations described above.
-
https://www.googleapis.com/auth/youtube.force-ssl - Allows viewing, editing and permanently deleting YouTube videos, ratings, comments and captions. This permission is broader than the functions implemented by this application. The current integration uses the requested permissions only for the channel identification and publishing functions described in this policy; it does not implement deletion of YouTube content.
These permissions are not read-only. Together they allow broad management of a YouTube account — broader than the functions this tool actually implements. The difference matters: the scope of a permission describes what it could allow; the functions of this tool are only those listed on the home page and in this policy — channel identification, approved uploads, thumbnails and subtitles, playlist handling, and local submission records.
The module that was examined does not access Gmail, does not access Google contacts, and does not access files in Google Drive. The permissions are used only for the functions described here.
11. Limits of the integration
The integration module commits to the following limits, in plain terms:
- It does not sell data obtained from Google to anyone.
- It does not use that data for targeted advertising or for any advertising purpose.
- It does not send that data to train artificial intelligence models.
- It does not transfer that data to third parties, except to Google/YouTube as part of the authorized operations described in this policy.
If the operator uses creative tools separately to produce the material that is published, those tools have their own practices and are governed by their own terms; this policy makes no claims about them. As a rule, they should not receive the integration's OAuth tokens or the private data obtained through YouTube API Services.
12. This website
This website is informational only. It exists to present the application and this privacy policy, including for the purpose of meeting the URL requirements of Google's OAuth configuration. It provides no login, no account creation, no forms that submit data, no chat, and no upload of any kind. It stores no personal data of its own: there is no database, no token storage, and no user tracking.
- Cookies and trackers: these pages set no cookies of their own and include no analytics scripts, advertising pixels, or chat widgets.
- Hosting logs: the pages are served as static files by the hosting platform that publishes this deployment. Like most web hosting, that platform may keep standard technical connection logs — for example IP address, timestamp, user agent, and the requested page — for its own operation and security. This policy does not make claims about the hosting platform's own data practices beyond this fact; the platform's terms govern them.
- External links: this site links to Google properties (the privacy policy, the permissions page, and the YouTube terms). Opening those links takes you to Google's websites, which are governed by Google's own policies.
13. Google's own policies
When the tool uses YouTube API Services, and when content is published on YouTube, data is handled by Google under Google's own policies. This application's policy covers only what this application does. Please also read:
- Google Privacy Policy — how Google handles data in its services;
- YouTube Terms of Service — the terms that govern the use of the tool's integration features;
- Google account permissions page — where access can be reviewed and revoked.
14. Contact
For questions about this policy, for privacy complaints, and for deletion requests covering the data described in section 9, contact the operator at:
Requests received at this address are handled manually by the operator, following the deletion procedure above: the covered local data is deleted within seven calendar days and completion is confirmed by email. A request for deletion of the locally stored data and tokens is separate from a request to remove published videos; if you need both, please say so in your message.
If the application changes in ways that affect the data it accesses, uses, stores, or shares, this page will be updated. The date at the top of this page shows when it was last revised.