Application information / 01

Privacy policy

Effective and last updated: August 30, 2026 · Policy version 2026-08-31

Index 9 Studio is a privately operated video-production and publishing workspace. Its owner operates the service and controls access. This policy describes the current application, including its public information pages, hosted queue, render worker, and optional social connections.

Information processed Use and sharing Access and security Retention Disconnect and delete Contact

1. Information processed

Production content: scripts, project names, scene images and ZIPs, optional music, settings, generated audio, captions, rendered videos, and processing files.
Queue and publishing records: job identifiers, timestamps, status and error messages, upload progress, selected platforms, titles, descriptions, captions, hashtags, audience and visibility settings, scheduling details, and platform post identifiers or links.
Connected-account information: OAuth client credentials, access and refresh tokens, granted permissions, expiry information, and account/channel identifiers, names, or profile-image URLs returned by the platform. Index 9 does not ask for your social-account password.
YouTube data: Index 9 uses YouTube API Services to identify the authorized channel and carry out approved uploads. The current connection also requests read-only YouTube and YouTube Analytics permissions; the current publisher does not run a separate analytics-data collection job.
Technical information: the service and hosting providers may process IP addresses, request headers, timestamps, and diagnostic logs for delivery, operation, and security.

Information is used to operate the authorized workspace, render and download videos, show job status, maintain social connections, and execute approved publishing requests. The application does not sell user data, serve advertising, or use Google account data to train general-purpose AI models.

Hosting and rendering: requests pass through Cloudflare to the Oracle-hosted controller when needed. Production files are also downloaded to the configured render worker and can remain in that worker's local storage.
Optional cloud processing: when selected and configured, Azure receives narration text, and Groq receives audio for transcription or script/edit-planning input. Local Kokoro, whisper.cpp, and FFmpeg processing is available instead. Selecting local processing does not remove the hosted queue's stored copy of your files.
Social platforms: connecting an account exchanges authorization data with that provider. An approved upload sends the selected video and metadata to YouTube, TikTok, or Instagram. Its eventual audience depends on your publishing choices and the provider's rules.
Automated assistants: an assistant or collaborator given the workspace access token can access the workspace. Information you share separately with such a service is also subject to that service's own terms and privacy practices.

Google data and credentials are used for the authorized connection and publishing features, not advertising or unrelated AI processing. The service's use of Google API data is subject to the Google API Services User Data Policy. Google's handling of data is explained in the Google Privacy Policy. Other providers apply their own policies; processing may occur outside your country.

3. Private access, cookies, and security

The information pages are public. Workspace APIs require the owner's access token or an authorized browser session. This is a shared workspace, not a multi-user service with separate private project areas: anyone given a valid workspace token can use the protected workspace.

Browser sign-in uses an essential Secure, HttpOnly session cookie with a lifetime of up to 30 days. Logout clears the browser session. These information pages do not set cookies, load analytics scripts, or embed social feeds.

Owner Google sign-in (added August 31, 2026): the owner may use Google to unlock the studio and recover its shared access token. Google provides a verified email address and stable account identifier. The controller stores that identity, hashed owner-session identifiers and security timestamps; it does not retain Google access or refresh tokens from this sign-in. Essential owner-session cookies last up to 30 days, and a temporary sign-in cookie lasts up to 10 minutes. Token recovery requires a Google sign-in within the previous 10 minutes. Signing out revokes that owner session. Expired sign-in records are removed during subsequent sign-ins; the pinned owner identity remains until the operator removes it. This owner login is separate from YouTube publishing authorization.

Public service traffic uses HTTPS. The application encrypts stored social OAuth tokens and client secrets on the controller. This does not mean every project file, database field, diagnostic log, or backup is encrypted by the application. The owner and authorized infrastructure administrators may access stored data. No system can promise absolute security.

During approved publishing, a platform may receive a hard-to-guess, limited-use media URL. Anyone possessing that URL can retrieve that video while the publishing job permits it; it is disabled when the job leaves its active publishing states. Do not share workspace tokens or publishing media links.

4. Storage and retention

Production files and job/publishing history are retained in the controller, render-worker storage, or operator-managed backups until the owner removes them. The current release has no automatic age-based purge for this history. Avoid submitting content you do not want retained, and request removal when it is no longer needed.

Disconnecting a social account clears that connection's account details and access/refresh tokens from the active connection record. It does not automatically remove OAuth application credentials, production files, publishing history, local render copies, logs, or backups. Those require owner-managed cleanup. Provider-side copies and published posts are controlled separately by the provider.

5. Disconnect, revoke access, and request deletion

Inside the unlocked workspace, open Publishing and use the account's Disconnect control to stop using its saved connection.
For Google/YouTube, also revoke Index 9's access through Google Account third-party connections. Other social platforms provide their own connected-app controls. Revocation and workspace logout are different actions.
Contact the workspace owner through the channel used to arrange your access. Identify the affected account or project and ask for deletion of its stored data, including any relevant local copies and backups. Never send passwords, access tokens, or client secrets with a request. The owner may need to verify that you are authorized to request removal.
To delete a post already uploaded to a platform, use that platform's own controls. Disconnecting Index 9 does not delete published videos.

There is no public self-service deletion endpoint in this release. The workspace owner must handle deletion requests and any applicable provider or legal retention/deletion requirements; this page does not claim that operator-managed deletion has already occurred.

6. Questions and policy changes

Authorized users can contact the person who provided their Index 9 workspace access using their existing private contact channel. The owner's personal contact details are not published on this page. Ask that person about access, correction, deletion, or privacy concerns.