Privacy Policy

This Privacy Policy applies to Video Migration System (the “App”) and its public information website. The App is currently designed as a local tool that helps content operations teams manage authorized YouTube channels and video upload tasks.

The public information website does not provide account sign-in or process video uploads.

Google Account and YouTube data

• The authorized account’s email address, used to identify the connected account in the App.
• YouTube channel names and channel IDs that the user can manage, used to display and select a destination channel.
• OAuth access tokens, refresh tokens, and related authorization information, used to call the YouTube Data API while authorization remains valid.
• Content submitted by the user for upload, including titles, descriptions, tags, thumbnails, playlists, and visibility settings.
• Processing status, visibility status, and execution results for uploaded videos, used to show progress and failures.

App operation data

• Upload tasks, file paths, operation settings, error messages, and necessary diagnostic logs.
• User-configured Douyin sources, title translation settings, thumbnail-processing settings, and optional third-party service configuration.

The App does not request or collect a user’s Google Account password.

Google user data is used only for visible product features that the user actively uses, including:

• Identifying authorized accounts and the YouTube channels they can manage.
• Uploading videos and setting titles, descriptions, tags, thumbnails, playlists, and visibility.
• Checking upload, processing, and publishing status and supporting retry, pause, and resume operations.
• Updating or deleting YouTube content when the user explicitly initiates the relevant action.
• Maintaining account and channel bindings and restoring task processing after reauthorization.

The App’s use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including the Limited Use requirements.

We do not sell Google user data or use it for targeted advertising. Necessary data transfers may occur only in the following circumstances:

• Sending video-management operations requested by the user to Google and YouTube.
• When the user enables AI title or thumbnail features, sending a source title, channel background information, or source image to the AI service configured by the user. Google passwords and OAuth tokens are not sent to AI services.
• When disclosure is required to comply with applicable law, a court order, or to protect users or public safety.

The current version primarily stores data on the device running the App. Accounts, OAuth clients, channels, and system settings are stored in a local database. OAuth client secrets and account credentials are encrypted. Upload tasks, file references, and diagnostic logs are also stored on the running device.

Authorization-state validation, PKCE, credential encryption, and minimized logging are used to reduce unauthorized-access risk. No storage or transmission method can guarantee absolute security, and the device owner must protect the device, database backups, and encryption key.

When a user removes a Google Account binding in the App, the App attempts to revoke the corresponding Google authorization and disables the related account and channel bindings. The current version retains soft-deleted records in the local database to preserve task relationships and support troubleshooting.

To permanently remove those records, the device or deployment administrator must delete the corresponding local database records and backups. Public descriptions of deletion behavior must remain consistent with the product’s actual implementation.

Users can also revoke authorization through the third-party connections page in their Google Account. Revoking authorization does not automatically delete content already uploaded to YouTube; users continue to manage that content through YouTube or the App.

Subject to applicable law, users may request access to, correction, export, or deletion of their related data and may decline or revoke Google authorization.

To submit a request, contact contact@lingzhentech.net. We may need to verify the requester’s relationship to the relevant account before processing the request.

We may update this Policy when product features, Google API permissions, data-handling practices, or applicable law change. Material changes will be identified on this page. If a change affects the use of previously authorized data, we will obtain renewed consent or complete additional verification when required.

Contact email

contact@lingzhentech.net

Root domain

lingzhentech.net