AutomiateVideo

Data and account access

Privacy policy

Last updated: September 7, 2026.

This policy covers AutomiateVideo, a private, operator-controlled video pipeline. It does not cover the separate SwapOnSpot marketplace. The project operator can be contacted at hariosaag@gmail.com.

Information the application handles

The Google connection does not request access to Gmail, Google Drive files or Google Contacts.

Why Google access is requested

The configured permissions are youtube.upload, youtube.readonly, youtube.force-ssl and yt-analytics.readonly. They support uploading videos, reading channel/video information, setting thumbnails and video visibility, and reading analytics. Some permissions allow broader actions than the application uses; this pipeline does not use them to manage subscriptions or post comments.

Information is used to perform the operator's publishing tasks, troubleshoot delivery and evaluate content performance. It is not sold or used for advertising profiles.

Processing and service providers

The pipeline runs on the operator's computer. Uploads and API requests transmit necessary information to Google/YouTube or another explicitly configured platform. Telegram processes commands and notifications, which may contain topics, status details and video links, including review links.

Configured AI, voice and media providers receive the text or assets needed for their tasks. This may include script content, topic history and content-performance summaries used for planning. Provider choices depend on the local configuration; their own terms and privacy policies apply. OAuth credentials are not intended as prompt content. The operator must not put credentials or unrelated personal information into topics or media prompts.

AutomiateVideo does not train a generalized AI model on Google user data. Its use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and retention

Tokens are stored in local configuration. Job records, media, checkpoints, analytics and metadata are stored in the project workspace and may also exist in device backups or file-sync storage. Lightweight metadata may be archived rather than automatically erased. There is no single automatic deletion deadline for all records; they remain until the operator removes them. Access is governed by the operator's device, filesystem and backup permissions.

Uploaded videos and messages remain with their respective platforms until separately deleted. Revoking authorization prevents future authorized access but does not delete already uploaded videos or local copies.

Revocation and deletion

To revoke Google access, open Google Account connections, select the connection for this project and remove access. The application will need fresh authorization to reconnect.

To request deletion of application-held account data, email hariosaag@gmail.com. Identify the connected channel, but never send passwords or tokens. The operator will verify the request and remove the relevant credentials, local account records and retained copies under their control, subject to any applicable retention obligations. Public videos must be removed through the relevant platform or by an explicit deletion request.

This informational website

These pages contain no login form, advertising scripts, tracking pixels or application cookies. The hosting provider may process standard request information such as IP addresses, timestamps and browser details to serve and secure the site. Contacting the operator by email discloses the information included in your message.

Changes and questions

Material changes to account access or processing should be reflected in this policy before use. For privacy questions, contact hariosaag@gmail.com.