Privacy Policy

ShortVideoAutomation · last updated 5 October 2026

ShortVideoAutomation is a private tool that publishes videos to YouTube channels owned by its operator. It is not a public service: there are no user accounts, no sign-ups, and nobody but the operator uses it. This policy explains what Google data the tool touches and what happens to it.

What Google data the tool accesses

When a YouTube channel is connected, Google is asked for these permissions, and each is used for one thing only:

• youtube.upload — uploading the operator's own video files to the operator's own channel.
• youtube.readonly — reading the connected channel's name and ID, so the tool can show which channel a token belongs to and refuse to upload to the wrong one.
• yt-analytics.readonly — reading view counts and retention for the operator's own videos, to decide what to publish next.
• youtube.force-ssl — setting a video's thumbnail, posting the channel's own first comment under its own video, and correcting a title.

Limited use

Concretely: Google user data is never sold, never transferred to anyone else, never used for advertising or profiling, and never read by a human except the operator. It is not used to train any model.

What is stored, and where

• OAuth tokens — one file per connected channel, on a private server controlled by the operator, readable only by the account that runs the tool. Tokens are never sent anywhere except to Google.
• Channel name and ID — stored alongside the token so the interface can name the channel.
• Video files and their metadata — the operator's own videos, titles and descriptions, held in the operator's own object storage.
• View and retention figures — kept in a local database to compare one video against another.

No data about viewers, subscribers or commenters is collected, and none is requested from Google.

Who else sees it

Nobody. There are no analytics services, no advertising networks and no third-party processors beyond the infrastructure the tool itself runs on — a virtual server and object storage rented by the operator. Data is sent to Google's own APIs to perform the actions above, and to no one else.

How long it is kept

A token is kept until the channel is disconnected or Google expires it, and the file is deleted at that point. Videos and their figures are kept while the channel is being run and deleted when they are no longer useful.

How to revoke access

Access can be withdrawn at any time from your Google Account's permissions page. The tool loses access immediately, and the stored token stops working at the same moment.

Changes

If this policy changes, the date at the top changes with it.