Privacy Policy

JARVIS Studio · last updated 9 September 2026

JARVIS Studio is a private tool operated by one person to produce and analyse short-form video for their own YouTube channel. It has no other users, no sign-up, and does not offer a service to the public.

Whose data this covers

Only the operator's own Google account and the YouTube channels that account controls. No third party can authorise this application, and no third party's data is collected, processed or stored.

What Google data is accessed

The application requests these OAuth scopes:

• youtube — manage the operator's own videos, including uploading and editing an existing video's metadata or visibility.
• youtube.readonly — read the operator's own channel and video metadata.
• yt-analytics.readonly — read audience-retention and performance reports for the operator's own content.

How that data is used

Retention curves, view counts and video metadata are used to decide what to make next and to measure what was made. Analytics are read; they are never sold, shared, published, or sent to any advertising or analytics provider.

Where it is stored

• Data lives in a private database on a single server reachable only over a private network.
• OAuth tokens are encrypted at rest with AES-256-GCM and are never written to logs, traces, error reports or source control.
• Nothing is stored in a third-party analytics or marketing platform.

What is published here

Only this page, the homepage, and the OAuth callback endpoint are reachable on the public internet. The dashboard and every administrative function are not publicly accessible.

Sharing

No data obtained through Google APIs is shared with anyone. There are no third-party processors, no advertising, and no data brokers. Text may be sent to a language-model provider to draft scripts and ideas; that content is video concepts and the operator's own performance figures, never viewer personal data — YouTube does not expose identifiable viewer data through the APIs used here.

Retention and deletion

Data is kept while the tool is in use. The operator can revoke this application's access at any time at Google Account permissions, which invalidates its tokens immediately. Stored copies can be deleted by disconnecting the integration in the application, which removes the stored credentials.

Google API Services User Data Policy

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

Contact

This application is operated privately. Enquiries about it go to the Google account that authorised it; there is no separate support channel because there are no other users.