← Back to Archive to Video

Privacy Policy

Last updated: March 2026

This Privacy Policy describes how the Archive to Video 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. User Information and API Data We Access, Collect, Store, and Use

We want you to understand exactly what user information and YouTube API Data the App accesses, collects, stores, and uses:

  • Account and authentication: To sign you in, we use Google OAuth 2.0. We do not access or store your Google password. We access and collect OAuth access and refresh tokens from Google when you authorize the App. We store these tokens in a server-side session (associated with a session cookie on your device) so you stay signed in. We use the tokens only to call the YouTube API on your behalf (e.g. to upload videos, create playlists, and set titles, descriptions, and privacy status).
  • YouTube API Data: “API Data” means data we receive from or send to YouTube via the API. We access and use YouTube API Services to create and update videos and playlists (titles, descriptions, privacy status, video IDs, playlist IDs) on your channel. We do not cache or store YouTube API Data (e.g. video or playlist metadata from YouTube) after the API request completes. Data we send to YouTube (e.g. video titles and descriptions) is processed by Google according to the Google Privacy Policy. We do not sell YouTube API Data or user information.
  • 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 use this only to complete your request. We do not store the URL or archive.org metadata longer than needed for the preview and upload job (and not long-term).

3. How We Use, Process, and Share Your Information

We use and process the information described above only to provide and improve the App’s functionality: to authenticate you, to run preview and upload jobs you start, and to set titles, descriptions, and privacy for your videos and playlists on YouTube. We do not use Google user data or YouTube API Data for advertising, analytics, marketing, or any purpose other than operating this App.

  • Internal use: Session data (including OAuth tokens) and in-memory job state are used only by our server to perform the actions you request.
  • With whom we share, transfer, or disclose Google user data: We share Google user data and YouTube API Data only with Google — we send OAuth tokens and API requests (e.g. video metadata) to Google’s OAuth and YouTube API services so you can sign in and upload content. Google’s use of that data is governed by the Google Privacy Policy. We do not share, transfer, or disclose your user information or API Data to any other third parties (no advertisers, no data brokers, no resale). We do not sell Google user data or YouTube API Data.

4. Data Protection and Security

We protect Google user data and other sensitive data as follows:

  • Security procedures: Security procedures are in place to protect the confidentiality of your data. Access to OAuth tokens and session data is restricted to the systems and processes needed to operate the App.
  • Encryption: We use encryption to protect your information. Data in transit between your browser and our server, and between our server and Google’s APIs, is protected using HTTPS/TLS. Sensitive data (such as OAuth tokens) is stored and handled in a way that minimizes exposure.
  • No long-term storage of API Data: We do not cache or persistently store YouTube API Data (e.g. video or playlist metadata). Such data is used only in memory to complete your request and is not retained after the request completes.

5. 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.

6. Data Retention and Deletion

Retention: We do not retain Google user data or YouTube API Data beyond what is needed to provide the service. 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. OAuth tokens and session data are retained only for the duration of your session and are cleared when you sign out or when the session expires.

Deletion:

  • 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 7). 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.

7. 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 Video” (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.

8. Contact Information

For questions about this Privacy Policy, your data, or the App, you may contact us as follows:

  • Contact: Henry Romp — 151henry151@gmail.com
  • GitHub: Open an issue or discussion at https://github.com/151henry151/archive-to-video.
  • Website: The App is available at https://hromp.com/archive-to-video/app/.

We will respond to privacy and data requests in a reasonable time.