Privacy Policy
Lecture Uploader, a private API client
Last updated 9 September 2026
Who this covers
This policy describes Lecture Uploader ("the client"), operated by John Santerre. The client is not distributed, is not offered as a service, and has no users other than its author. It runs on one personal computer and is invoked manually.
What the client accesses
The client requests a single scope from the YouTube Data API,
https://www.googleapis.com/auth/youtube.upload, which permits it to upload
video files to the authorising account's channel. It requests no other scope.
Using that scope, the client does exactly one thing: it uploads a video file from the author's computer, together with a title, description, tags, and a privacy status, and records the resulting video identifier so that a course website can link to it.
What the client does not do
- It does not read, collect, or store viewer data, watch history, comments, or subscriber information.
- It does not retrieve or store YouTube Analytics data.
- It does not search YouTube, index channels, or download videos.
- It does not access any channel other than the one that authorised it.
- It does not transmit any data to any third party, and there is no server involved.
- It does not display advertising and it is not used for any commercial purpose.
What is stored, where, and for how long
Two items are stored, both on the author's own computer, in a file readable only by the author's operating system account.
- An OAuth 2.0 refresh token, which allows the client to obtain access tokens without repeating the browser sign-in. It is retained until the author deletes it or revokes access.
- The video identifiers returned by uploads, which are written into the course website's own files so that pages can link to the correct video. These identifiers are public information about the author's own videos.
Nothing is stored on any server, in any database, or with any hosting provider. No personal data belonging to any other person is stored at any point.
How authorised data is used
Access is used solely to publish the author's own instructional videos to the author's own channel. The videos are lecture recordings for university courses the author teaches. Authorised access is never used to gather information about YouTube users, to analyse other channels, or for any purpose unrelated to uploading these videos.
Data deletion
There is a single stored item that could be called authorised data, the OAuth refresh token, and it is deleted in any of three ways.
- By the author, by deleting the file. It lives at one path on one computer and nothing else holds a copy.
- By revoking access at https://myaccount.google.com/permissions, which invalidates the token immediately and permanently.
- By request. Write to the contact address below and the token is destroyed.
No other authorised data is retained, so there is nothing further to delete. Video identifiers written into the course website refer to the author's own public videos and contain no personal data belonging to anybody.
Revoking access
The authorising account may revoke this client's access at any time, immediately and without contacting the author, at https://myaccount.google.com/permissions. Revocation renders the stored refresh token useless.
Google and YouTube terms
By using this client, the authorising account is bound by the YouTube Terms of Service. The client uses the YouTube API Services; the Google Privacy Policy describes how Google handles data on its side.
Changes to this policy
If the client's behaviour changes, this page is updated and the date at the top revised. Because the client has one user, no notification mechanism exists or is needed.
Contact
Questions about this policy or the client: john.santerre.ai@gmail.com.