Privacy Policy

Escapement Studio · Effective date: July 28, 2026 · Last updated: July 28, 2026

Escapement Studio ("the Application") is a personal application, written and used by one individual developer, that produces original short-form videos and uploads them to that developer's own YouTube channel using YouTube API Services. This policy explains exactly what data the Application touches, why, where it is kept, and how it can be removed.

1. Scope and who this policy covers

The Application has a single user: its developer. It is not distributed, published, sold, licensed or offered to anyone else. There is no sign-up, no account system and no hosted version that a third party could use. As a result, the only Google account the Application ever accesses is the developer's own account, and the only YouTube channel it ever accesses is the developer's own channel.

This policy is published so that Google, YouTube, and anyone who encounters the Application's OAuth consent screen can verify how it handles data.

2. Data collected from other people

None. The Application does not collect, request, receive, buy, store, process or transmit personal data belonging to any person other than its developer. It has no visitors, no customers, no analytics tracking, no advertising, no cookies, no contact forms and no telemetry.

This website itself is a set of static pages. It does not set cookies, does not run analytics or advertising scripts, and does not ask visitors for any information. Standard access logs may be produced by the hosting provider as an ordinary part of serving web pages; they are not used to identify or profile anyone.

3. Google user data the Application accesses

Through Google OAuth, the Application accesses the following data from the developer's own Google/YouTube account, and nothing else:

The Application writes the following to the developer's own channel: video files with their title, description, tags, category, language, privacy status and scheduled publish time; and one comment per video, written as part of that video's script, posted on that same video. It performs no other automatic write operations. Separately, a manual maintenance command, run by the developer by hand, can delete a video that the Application itself uploaded to the developer's own channel.

4. OAuth scopes and why each is requested

• https://www.googleapis.com/auth/youtube.force-ssl — required. Used to upload videos to the developer's own channel, set and read their status, read back the developer's own videos, and post the developer's own comment on the developer's own video.
• https://www.googleapis.com/auth/yt-analytics.readonly — optional. Used only to read aggregate metrics for the developer's own channel.

The Application requests no other scopes, and requests no access to Gmail, Drive, Contacts, Calendar, Photos, location or any other Google service.

5. How data is stored

• OAuth tokens are written to a single JSON file in the Application's own credentials folder, on the developer's own computer and on a private server rented and administered by the developer. They are not copied to any cloud credential store, database, or third-party service.
• Video IDs and titles of the Application's own uploads are recorded in the local project files that describe each production run, so the same video is never uploaded twice.
• A small local counter file records how many uploads were made on each of the last fourteen days, to enforce the daily upload cap. Older entries are discarded automatically.
• Analytics figures are not retained. They are requested from the API when a report is run, printed for the developer, and discarded when the process exits. The Application keeps no historical store of YouTube Analytics data.
• Machines running the Application are under the developer's sole physical or administrative control. The optional local control panel binds to 127.0.0.1 by default; if it is ever exposed beyond the local machine, HTTP authentication with a password is required.

6. How data is shared

Google user data obtained through YouTube API Services is never shared, sold, rented, published, transferred or otherwise disclosed to any third party. It is not sent to the language model, text-to-speech, stock media or image generation services the Application uses.

Those third-party services receive only content the Application itself creates — topic briefs, script text, and scene search terms. They never receive OAuth tokens, channel data, video statistics or any other Google user data.

The Application transfers no data to advertising platforms, data brokers or analytics providers, and does not use Google user data to build profiles, to serve or target advertising, or to train, retrain or fine-tune any machine learning or artificial intelligence model.

7. Limited Use disclosure

Specifically, and consistent with those requirements, the Application: limits its use of Google user data to providing and improving the single user-facing feature it exists for (producing and publishing the developer's own videos and reporting on their performance to the developer); does not transfer that data except as necessary to provide that feature, for security purposes, or to comply with applicable law; does not use that data for serving advertisements; does not allow humans to read that data unless the developer has given affirmative agreement for specific messages, it is necessary for security purposes or to comply with applicable law, or the data has been aggregated and anonymised; and does not sell that data.

8. YouTube API Services

Escapement Studio uses YouTube API Services. By using the Application, its developer agrees to be bound by the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy.

9. Revoking access

Access granted to the Application can be revoked at any time from the Google security settings page:

• https://security.google.com/settings/security/permissions
• https://myaccount.google.com/permissions

Revoking access immediately invalidates the stored tokens. The Application then has no access of any kind until it is authorised again.

10. Retention and deletion

• OAuth tokens are kept only while the Application is in use. Deleting the token file, or revoking access at the links above, removes them completely.
• Stored video IDs and production files can be deleted at any time by deleting the Application's output folder. Nothing is recoverable from anywhere else, because nothing is stored anywhere else.
• The Application maintains no long-lived cache of YouTube API data. Channel figures and video statistics are fetched fresh when they are needed and are not persisted. Where any identifier is retained (video IDs of the developer's own uploads), it is retained only to prevent duplicate uploads and is deleted together with the production folder.
• No data belonging to any other person is held, so there is nothing for a third party to request the deletion of. Requests or questions can still be sent to the address below and will be answered.

11. Security

Credentials are kept on machines controlled solely by the developer, and are excluded from version control. All communication with Google APIs and with every third-party service the Application uses is over HTTPS/TLS. API keys and OAuth client secrets are held in local environment configuration, not in shared or published files.

12. Children

The Application is not directed to children, is not used by children, and collects no data from children. Every video it uploads is explicitly marked as not made for kids.

13. Changes to this policy

If the Application's behaviour changes in a way that affects this policy, this page will be updated and the "Last updated" date at the top will be changed. The current version is always the one published here.

14. Contact

Questions about this policy, or about how the Application handles data: sivrii1940@gmail.com.