Privacy policy

Data and purpose

The studio processes your uploaded media, briefs, text, Brand Memory, drafts, approvals and local history to prepare content. Local AI analyzes your own inputs; it does not use YouTube API data to train AI or create advertising profiles.

The application uses YouTube API Services. With your Google authorization it reads the selected channel identity and the information necessary to verify a specific upload: video identifier, metadata, processing status, visibility and resource version. It stores OAuth tokens and resumable upload session references only in the local macOS Keychain. It does not request your Google password or download videos from YouTube.

Sharing

Only content you explicitly approve for transfer is sent to the selected provider. YouTube receives the approved video, title, description, audience declarations and technical upload requests. Upload permission and a later change to public or unlisted visibility are separate decisions. Account linking, editorial approval and a local calendar entry do not publish content.

Content and application data remain on the owner's Mac. The private remote connection uses Tailscale and application authentication. No advertising, third-party tracking or analytics widgets are embedded in the studio. Opening a provider's external link is subject to that provider's policies.

Information website

The separate public information website contains these documents only. It does not provide access to the studio, source media, account records or OAuth credentials. Hosting providers process necessary connection and security information to deliver and protect the website. The site does not include advertising, tracking widgets or a contact form. The operator receives messages only when you choose to contact the published email address.

Retention and deletion

Original user media and editorial history are kept for the owner's work until separately deleted by the owner. Google authorization and YouTube-derived data are handled separately. Requests to revoke access or erase provider data must be completed as soon as possible and within seven calendar days, including controlled backup copies. Stale API metadata must be refreshed or removed within thirty calendar days. A pending cleanup must not be represented as completed.

Use the studio's data-deletion controls or contact the operator below. Revocation and local data deletion do not delete videos from YouTube. YouTube videos must be managed in YouTube Studio. The owner must also remove any separately made external backup copies; the application cannot access files outside its controlled storage.

Sessions

The studio uses a Secure HttpOnly session cookie for private HTTPS login, and browser local storage for interface preferences and resumable file-selection bookkeeping. Each device has its own revocable session. No advertising cookies are used.

Purpose and your rights

Data is processed to provide the private studio functions you request, protect the service and handle your support or deletion request. Optional Google access is based on your authorization; it can be withdrawn without authorizing publication. Where data-protection law applies, you may request access, correction, erasure, restriction or portability of your personal data and object to processing when the applicable conditions are met. You may also complain to your competent data-protection authority. The operator does not use this studio to make decisions about individuals with legal or similarly significant effects.

Your controls

You can revoke Google's authorization directly in Google account permissions. Google's handling of data is described in the Google Privacy Policy. Contact the operator for access, correction, deletion or privacy complaints. Before the reviewed integration is activated, the owner must accept the current privacy policy and terms.