Privacy Policy

This policy explains how Lumo Studio, including its Universe with Lumo and Health Advice workspaces (the “Studio”, “we”, “our”, or “service”), handles information when an authorized user creates AI-assisted media and connects publishing providers such as Facebook, Instagram, YouTube and TikTok.

1. Information we process

Depending on the features you use, the Studio may process:

Studio account data: username, encrypted/hashed authentication information, secure session information and account role.
Creative data: prompts, episode text, generated images, video clips, narration, subtitles, thumbnails, captions, titles, descriptions and hashtags.
Connected-provider data: provider account identifiers and account metadata needed to show which account is connected.
OAuth and API credentials: access tokens, refresh tokens, client secrets or API keys that you deliberately provide to enable generation or publishing.
Operational data: saved calendar plans and sources, generation/publishing status, approvals and consent choices, provider job identifiers, timestamps, errors and limited security/technical logs.

The Studio does not ask for or store your Facebook, Instagram, Google/YouTube or TikTok password.

2. How we use information

We process information to authenticate authorized users, research and save requested calendars, create and archive media, recover interrupted jobs, connect third-party accounts, refresh OAuth authorization, publish content under the user's saved workspace settings and platform-specific approvals, display publishing status, prevent duplicate work, secure the service and diagnose errors.

3. Connected services

When you use a connected feature, the Studio may send the minimum content and authorization data needed to the relevant service. These may include OpenAI, OpenArt, ElevenLabs, Meta (Facebook and Instagram), Google/YouTube and TikTok. Those providers process information under their own terms and privacy policies.

For TikTok, the Studio may receive and securely store an OAuth access token, a rotating refresh token, the authorized creator’s Open ID, username/nickname and granted scopes. The Studio uses them only to maintain the authorized connection, query publishing capabilities and publish content requested through the Studio.

4. Credential security

Provider secrets saved through the owner-only Provider API Connections panel are encrypted at rest in a private server-side vault. Saved secrets are not returned to the browser after storage. OpenAI, OpenArt and ElevenLabs can be shared across the two workspaces; social credentials and OAuth accounts are separated by workspace. OAuth state values are short-lived and used to protect the authorization callback against cross-site request forgery. Access tokens are refreshed server-side when supported.

5. Content publishing

The Studio can publish a finished video, feed image, thumbnail/cover where the provider supports it, title where required, description/caption and hashtags. One-off publishing is manual by default. Calendar publishing remains off until the owner enables Autopilot and individual platforms in that workspace. Facebook and Instagram targets may then process automatically. Every YouTube calendar target requires its own approval; every TikTok calendar target requires a fresh privacy choice, interaction choices, commercial-content disclosure and music-rights confirmation. Provider rules, privacy choices, app-review/audit status and API limits may affect whether a post is accepted or public.

6. YouTube API Services

Lumo Studio uses YouTube API Services. By connecting a YouTube channel in either workspace, you also agree to the YouTube Terms of Service. Google processes information under the Google Privacy Policy.

The Studio requests only the OAuth scopes used by its publishing workflow: youtube.upload to upload an owner-approved video and supported thumbnail, youtube.readonly to identify the authorized channel, and youtube.force-ssl to perform the final videos.update(part=status) transition from the temporary private upload to the privacy setting chosen by the owner. We receive the authorized channel ID/title and an OAuth refresh authorization. We do not request or store your Google password.

YouTube API data is used only to show the connected channel, verify authorization, upload a video with user-approved metadata, set its thumbnail and complete the requested publishing workflow. We do not sell YouTube API data, use it for advertising profiles, or share it with unrelated third parties.

The YouTube OAuth refresh token is encrypted at rest on the Studio server. Disconnecting YouTube uses Google’s revocation endpoint when possible and deletes the stored refresh token and connected-channel identifiers from the Studio vault. You can also revoke access at any time from your Google Account’s third-party connections/security controls.

If a user requests deletion of YouTube-related authorization or the Studio can no longer verify authorization, the operator will remove the stored YouTube authorization data promptly and in all cases within 30 days. Disconnecting from the Provider API Connections panel performs this removal immediately from the Studio vault.

7. Retention and deletion

Creative archives and production assets are retained on the private Studio server so interrupted jobs can resume without regenerating paid assets. Provider credentials remain until replaced, revoked or disconnected. YouTube authorization can be revoked and deleted with Disconnect / delete YouTube data; TikTok authorization can be revoked with Disconnect. TikTok’s Disconnect control revokes the token when possible and removes the stored TikTok access and refresh tokens from the Studio vault.

An authorized operator may also delete Studio data directly from the private server and can revoke provider access from the relevant provider’s account/security settings.

8. Sharing and sale

The Studio does not sell personal information. It does not provide connected-account credentials to advertisers. Information is shared with service providers only as necessary to perform the generation, hosting, authentication or publishing operation requested by the authorized user, or when required by law.

9. Security and international processing

We use access controls, encrypted credential storage, secure cookies when deployed over HTTPS, CSRF protection and restricted server-side storage. Internet services cannot be guaranteed perfectly secure. Third-party providers may process information in countries different from yours under their own legal frameworks.

10. Children

The Studio is a private content-production tool and is not directed to children. Do not use it to submit personal information about children without an appropriate lawful basis and authorization.

11. Your choices

You can choose which providers to connect, disconnect TikTok from the Studio, revoke access through each provider, change publishing privacy options, and remove locally stored material through the service operator. Where applicable, you may exercise privacy rights available under your local law.

12. Changes and contact

We may update this policy when the Studio or connected-provider requirements change. The current version is published at this URL. Privacy or data-removal questions should be directed to the operator through the official Eventuza website/contact channel associated with this service.