Privacy policy

HistoryShorts Studio · last updated 24 August 2026

HistoryShorts Studio is a personal application that runs on its author's own computer. It has no other users, no accounts, and no server. This policy describes what it does with data obtained through Google APIs.

What it accesses

With the account holder's permission, the application requests two read-only Google scopes:

youtube.readonly — to list the account's own channels and videos.
yt-analytics.readonly — to read view counts, watch time and audience-retention curves for those videos.

Both are read-only. The application cannot upload, modify, delete or publish anything, and does not request permission to do so.

What it stores, and where

Everything stays on the author's own computer. There is no server, no database, and no cloud storage.

The access token returned by Google is written to a local file so the application does not have to ask for permission every time it runs.
Statistics retrieved from YouTube — view counts and retention curves — are saved locally alongside the corresponding video project.

What it does not do

It does not transmit Google user data to any third party.
It does not sell, share, rent or trade any data.
It does not use Google user data for advertising, profiling, or training machine-learning models.
It does not read data belonging to anyone other than the signed-in account holder.
It has no analytics, no tracking, and sets no cookies. This website collects nothing from visitors.

Limited Use

The application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Retention and removal

Stored statistics and tokens can be deleted at any time by deleting the application's local files. Access can be withdrawn independently at myaccount.google.com/permissions, which immediately and permanently revokes the application's ability to read anything.

Contact

Questions about this policy: thesawg69@gmail.com