Privacy Policy

1. Who operates MediaOS

Hellier.ai operates MediaOS as a private media production workspace. Questions, complaints, access requests, and deletion requests can be sent to agent@hellier.ai. Include enough information to identify your channel or workspace. Do not send passwords, authorization codes, or access tokens.

2. Information we handle

Workspace information. We process the identity and email used to sign in, brand and account setup records, proposed handles and descriptions, production briefs, source research, scripts, uploaded or generated media, review decisions, schedules, and activity records.

YouTube connection information. MediaOS uses YouTube API Services. When you authorize a channel, we receive its channel ID, name, handle or custom URL, profile-image URL, and authorization credentials. We store the connection status and related timestamps. Google handles your Google sign-in; MediaOS does not ask you to provide your Google password.

YouTube reporting and publishing information. We retrieve channel statistics such as views, subscriber count, video count, and whether subscriber counts are hidden. Publishing records include destination channel, title, description, media and thumbnail references, schedule, requested visibility, upload and processing status, YouTube video ID or URL, and relevant errors.

Technical information. Hosting and sign-in services process the network requests needed to serve the application, including IP address, browser information, timestamps, and operational logs. Sign-in providers may use cookies or similar browser storage to maintain your session. Google-hosted profile images and links to Google services may cause your browser to contact Google.

3. How we use information

• Authenticate authorized users and maintain the private workspace.
• Identify the channel you select and associate it with the intended brand.
• Prepare and review media, run authorized schedules, and upload selected content.
• Display channel reporting and confirm upload processing and visibility.
• Resolve errors, protect account access, and prevent duplicate publishing.

YouTube authorization is limited to viewing your YouTube account and managing uploads through the requested read and upload permissions. Ongoing authorization lets scheduled work run without requiring a new sign-in for each upload.

Hellier does not use information received through Google APIs for advertising, sell that information, or use it to train generalized AI models. Its use and transfer of Google API information must follow the Google API Services User Data Policy, including its Limited Use requirements.

4. Service providers and sharing

OpenAI Sites provides the application hosting, sign-in integration, and application data services. Google Cloud provides the publishing worker, job scheduling, and storage for account authorization and publishing records. Cloudflare supports website infrastructure and media storage or delivery.

When you authorize an upload, MediaOS sends the video, its title and description, visibility and audience settings, applicable synthetic-media declaration, and any selected thumbnail to YouTube. Content becomes available according to YouTube’s resulting visibility settings. Google’s handling of this information is described in the Google Privacy Policy.

Authorized Hellier operators can access workspace information to operate the service and respond to requests. We may disclose information when legally required or necessary to address abuse or protect rights. Google API information is subject to its applicable use and transfer restrictions.

5. AI assistance and media

MediaOS can send production briefs, source research, scripts, audio, and sample video frames to OpenAI’s API for research, writing, narration, transcription, and review. Google Veo receives prompts for generated motion. These production features do not require sending your Google authorization tokens to an AI model.

If you ask a connected assistant to inspect the workspace, its tools can return non-token channel information and campaign records, such as channel names, IDs, handles, connection status, and publication results. Information you include in an assistant prompt may also be sent to the selected provider. Use those features only with information you intend to share with that assistant.

Some rendered media is delivered through shareable URLs. Anyone who has such a URL may be able to view the file. A private workspace does not make every delivery URL private. Use YouTube Studio to verify the visibility of uploaded YouTube content.

6. Storage and protection

MediaOS stores its Google access and refresh tokens in encrypted records in private Google Cloud Storage. The application uses AES-256-GCM encryption for those token records. Token values are excluded from normal account-list responses. Access to account operations is controlled by the application’s administrator permissions.

These safeguards apply to the identified systems and records; they are not a guarantee against every security incident. Service providers process data according to their applicable terms and infrastructure arrangements.

7. Disconnecting, revoking, and deleting data

Unlinking a brand removes its publishing destination and pauses its automated series. It does not revoke the underlying Google authorization or delete YouTube videos.

Revoke & remove data, available in MediaOS Accounts, records an explicit deletion request, removes active application authorization, attempts Google consent revocation, pauses affected publishing, and removes associated live API records. Google revocation may also invalidate other channels or scopes granted to the same Google application. An upload already accepted by YouTube may still finish. The control records unfinished steps and supports retries; a live-record completion status is not a certificate that every infrastructure copy has been erased.

You can also revoke the app’s Google access directly in your Google Account permissions, or request deletion of stored YouTube account data by contacting agent@hellier.ai. We may request proportionate information to confirm that you are the account owner or an authorized representative; this must not extend an applicable deletion deadline.

Applicable YouTube requirements call for deletion as soon as possible and within seven calendar days of an in-app revocation or deletion request. Failed or incomplete steps require operator follow-up. Report an unfinished request to the contact above; do not assume that a pending request has completed.

Deleting MediaOS account data does not delete videos or channels held by YouTube. Use YouTube’s own controls for those resources. Independently created Hellier scripts and media are separate from Google API data; identify any original workspace materials you want removed in your request.

8. Retention and policy changes

Daily background maintenance checks saved YouTube authorization and retries eligible cleanup requests. Channel metadata is refreshed during verification. Publishing API records are selected for refresh after 20 days and for expiry after 21 days without successful verification. Current channel statistics are fetched when requested. The website does not retain a second copy of provider-returned YouTube profile names, handles, or IDs in brand mapping rows; operator-selected destination IDs and original production records are separate.

We will update this page when MediaOS’s data practices change. Material changes to Google data use require appropriate disclosure and consent before the affected use begins.