MathYTB privacy policy

Effective 6 October 2026.

This policy explains what data MathYTB accesses, how it uses that data, where the data is stored, and who it is shared with. MathYTB is a personal application: its only user is its owner, who signs in with their own Google account to publish videos to their own YouTube channel.

1. Data MathYTB accesses

When the owner signs in, MathYTB asks Google for two permissions (OAuth scopes):

With these permissions MathYTB handles the following data:

MathYTB does not access the owner's email, contacts, comments, subscribers, analytics or any other Google data, and it never accesses any other person's account or channel.

2. How MathYTB uses the data

The data is not used for advertising, profiling, analytics or any purpose other than publishing the owner's own videos.

3. Where the data is stored

MathYTB runs only on the owner's own computer. The sign-in tokens are stored in a local file on that computer, readable only by the owner. MathYTB has no server and no database: it sends data only to Google's YouTube Data API, over an encrypted (HTTPS) connection.

4. Sharing

MathYTB does not sell, share, transfer or disclose any data to anyone. The only recipient of any data is YouTube itself, which receives the videos and details the owner chooses to publish.

5. Retention and deletion

Sign-in tokens are kept on the owner's computer until the owner deletes them or revokes access. Published videos stay on YouTube until the owner deletes them there. Access can be revoked at any time from Google Account permissions, after which MathYTB can no longer access the channel.

6. Google API Services User Data Policy

MathYTB's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Use of YouTube through MathYTB is also subject to the YouTube Terms of Service and the Google Privacy Policy.

7. Children

MathYTB is not directed at children and collects no data from anyone, including children.

8. Changes

Any change to this policy will be published on this page, with a new effective date.

9. Contact

Questions about this policy can be sent to the owner through GitHub.