LaptopMedia YouTube Privacy Policy

Effective date: 15 October 2026

This policy describes the LaptopMedia YouTube desktop tool operated by LaptopMedia Ltd. It is separate from the website Privacy Policy and Cookie Policy, which cover visits to LaptopMedia.com.

Our app overview explains the tool’s current features and permitted use.

Data used by the tool

The tool uses YouTube API Services with your authorization. It processes:

• The video file and metadata selected for upload.
• The connected channel’s identifier and name.
• Information about the relevant video’s identifier, visibility, embedding availability and processing status.
• Local job records, including upload identifiers, URLs, checksums and verification results.
• OAuth access and refresh tokens used to carry out the authorized workflow.
• Temporary upload state used to resume interrupted uploads.

The current requested scopes are youtube.upload and youtube.readonly. They are used for uploading approved content and verifying the channel and upload.

The tool does not request access to Gmail, Google Drive or YouTube Analytics, or collect your Google password.

How data is used and shared

The tool sends the selected upload content and API requests directly to Google/YouTube. Local data is used to perform authorized uploads, check their results and prevent accidental duplicate uploads.

Access to local records is limited to the operator and people or tools expressly authorized to assist with that workflow. Unpublished video details should be treated as confidential when choosing an assistant or sharing a job record.

We do not sell Google API data or use it for advertising profiles. Google API data may be used only for the disclosed, authorized workflow. Its use and transfer are subject to the Google API Services User Data Policy, including the Limited Use requirements.

Google’s own processing is described in the Google Privacy Policy.

Storage and safeguards

The tool runs on the authorized operator’s workstation. Tokens and resumable upload credentials are saved in a private local runtime directory, separate from version-controlled source.

The tool restricts those files with operating system permissions and uses HTTPS for Google API communication. It does not publish tokens in embed codes or public job receipts.

These measures do not mean the app itself encrypts local token files. Workstation and backup security remain important.

This local API client does not use website advertising cookies for YouTube authorization. Visiting these public information pages may still involve the website technologies described in the separate site policies linked above.

Retention and deletion

Authorization tokens are kept only while needed for the actively authorized workflow. Stored YouTube API information is refreshed or deleted within 30 days, unless a different retention rule is expressly permitted by YouTube’s policies.

Source footage and operator-authored production documents are separate from information retrieved from YouTube.

You can request deletion of the tool’s locally stored authorization and associated API data through Contact Us. Mention “LaptopMedia YouTube — data deletion” and the relevant channel. Do not send a password or token.

We will complete the deletion as soon as possible, and within seven calendar days of the request. We also remove associated API data within seven calendar days after we learn that authorization has been revoked or can no longer be confirmed.

Deleting local tool data does not delete videos or other information already stored by YouTube. Manage or delete those separately in YouTube Studio.

Disconnecting Google access

You can revoke the tool’s access through Google account permissions. Select the relevant application and remove its access.

To request local cleanup as well, contact us using the procedure above. Deleting a local token file alone does not revoke a permission still granted at Google.

Contact and changes

For questions, complaints or data requests, use Contact Us and identify “LaptopMedia YouTube”.

We will update this policy when the tool’s actual data practices change. New features requiring additional Google access will require the appropriate disclosure and consent. This policy is not advance permission for unimplemented integrations.