Privacy Policy

Last updated: January 2026

This Privacy Policy describes how the Archive to YouTube application (“App”) handles information when you use the App to upload content to YouTube.

1. Use of YouTube API Services

This App uses YouTube API Services to let you sign in with your Google account, upload videos to your YouTube channel, and create or update playlists. By using the App, you are also subject to the Google Privacy Policy (http://www.google.com/policies/privacy).

2. Information We Access, Collect, and Use

When you use the App:

Account and auth: To sign you in, we use Google OAuth. We do not store your Google password. We store a session (e.g. in a cookie) so you stay signed in; that session holds access and refresh tokens provided by Google to upload and manage content on your behalf.
API Data: We use YouTube API Services to create and update videos and playlists (titles, descriptions, privacy status) on your channel. We do not sell or share this data with third parties. Data sent to YouTube (e.g. video titles and descriptions) is processed by Google according to the Google Privacy Policy.
Archive.org URL and metadata: When you enter an archive.org URL, we fetch public metadata and audio from archive.org to generate a preview and to create videos. We do not store that URL or metadata longer than needed to complete your upload job.

3. How We Use and Share Your Information

We use the information above only to operate the App: to authenticate you, to run preview and upload jobs you start, and to set titles, descriptions, and privacy for your videos and playlists. We do not use your data for advertising or share it with external parties for marketing. Session and token data is used only to call YouTube API on your behalf and is not shared with third parties except as needed to use Google’s services (e.g. OAuth and YouTube API).

4. Storage and Technology on Your Device

The App stores or accesses information on your device or browser in the following ways:

Cookies / session storage: We use session cookies (or similar technology) to keep you signed in and to maintain your session. These are required for the sign-in and upload flow. You can clear cookies in your browser to end your session.

5. Refreshing, Storing, and Deleting API Data

We do not cache or store YouTube API Data (e.g. video or playlist metadata from YouTube) for longer than needed to complete a single user action:

Refresh: We do not periodically refresh API Data. We call the YouTube API only when you use the App (e.g. when you run a preview, start an upload, or change privacy). We do not store copies of your YouTube content (titles, descriptions, video IDs) after the request completes.
Storage: We store only OAuth access and refresh tokens in your server-side session so you can stay signed in. Session data is temporary and is cleared when you sign out or when the session expires (e.g. after a period of inactivity). Upload job status (e.g. progress and result) is held in memory only for the duration of the job and for the short time you use the “review” and “make public” features; we do not retain it long term.
Deletion: When you sign out, we clear your session. You can revoke the App’s access to your Google account at any time (see section 6). We do not retain API Data after that; we have no separate retention schedule because we do not store API Data beyond the life of the session and the in-memory job.

6. Deleting Data and Revoking Access

You can revoke the App’s access to your YouTube/Google account and request that we stop using your data as follows:

Revoke access: Go to the Google security settings page for third-party apps: https://myaccount.google.com/connections?filters=3,4&hl=en. Find “Archive to YouTube” (or the name of this app) and remove access. After that, we can no longer access your YouTube channel via the API.
Session data: Sign out using the “Sign out” button in the App to clear your session. Server-side session data is typically removed when the session expires (e.g. after a period of inactivity). We do not retain upload job data longer than needed for the job to complete and for you to use the “review” and “make public” features.

7. Contact

For questions about this Privacy Policy or your data, please use the project repository (e.g. open an issue or contact the maintainers listed there).