Privacy Policy

Last updated 6 September 2026

Summary

sleepforge runs on the machine of the person who installed it. It has no server, no database and no analytics. It collects nothing about you, because there is no “you” other than the operator running it on their own computer, acting on their own account.

What data is involved

When the operator authorises sleepforge with their Google account, Google returns an OAuth token. That token is written to a file on the operator's own computer and used for one purpose: uploading videos to the operator's own YouTube channel.

The token never leaves that machine. It is not transmitted to us, to any server we control, or to any third party. There is no server to transmit it to.

Scope requested

sleepforge requests a single scope: https://www.googleapis.com/auth/youtube.upload.

This permits uploading new videos and setting their metadata and thumbnail. It does not permit reading, editing or deleting existing videos, and it does not grant access to analytics, comments, subscriber lists, watch history, or any other account data. sleepforge requests no other scope.

What is uploaded to Google

Only content the operator generated: a video file, its title, description and tags, and a thumbnail image. Uploads default to private visibility. Making a video public is a separate, manual action taken by the operator in YouTube Studio.

What is not done

Retention and deletion

The OAuth token persists on the operator's machine until deleted. To revoke access, the operator can delete the token file, or remove sleepforge at myaccount.google.com/permissions. Revoking through Google invalidates the token immediately and irreversibly.

Limited Use disclosure

sleepforge's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Changes

Any change to this policy will be published on this page with a revised date above.

Contact

booms.satya@gmail.com