Your information

Privacy policy

Effective October 24, 2026

Moze Studio is a personal publishing application operated by MozeTech. The application runs locally on the operator’s Mac; this public website explains how it works.

What the application handles

Google and YouTube data

The app requests access to upload videos and read the authorized YouTube account. It uses that access to identify the selected channel, upload videos with their publishing metadata, and check upload, processing, scheduling, and publication status. It does not use Google API access to read Gmail, Google Drive, contacts, or unrelated Google services.

Moze Studio uses Google API data only to provide the publishing workflow requested by the operator. It does not sell this data, use it for advertising, or use it to train generalized AI models. Its use and transfer of Google API data follows the Google API Services User Data Policy, including the Limited Use requirements.

Google handles data sent to its services under the Google Privacy Policy. Published videos and metadata are also subject to the visibility settings and policies of YouTube.

Content sent to AI services

When generation is enabled, creative prompts and story context are sent to Claude through the operator’s configured Claude Code or Anthropic API connection. For automatic captions, the app samples eight frames from the local input video and supplies those images, the operator’s optional script or summary, and relevant creative context. It does not transcribe or send the full soundtrack as part of this caption workflow.

These are creator-supplied content inputs, not content retrieved from YouTube through the Google API. OAuth tokens and Meta credentials are not included in the AI prompts. Anthropic’s handling of submitted content depends on the operator’s account, settings, and applicable Anthropic privacy policy and service terms.

Optional Grok Bot connection

If the operator connects their own Grok Bot to the local app, that bot can receive selected account names, handles and identifiers; creative briefs; schedules; local source-file paths; queue states; publishing errors and post links; and worker and disk status. This lets the operator check and manage the workflow through their bot.

The integration does not return authorization credentials, OAuth setup data, browser security tokens, video bytes, or sampled frames. The bot’s provider processes information shared with it under its own terms and privacy practices. This optional connection is separate from visiting this website.

Local storage and retention

Credentials are saved in files restricted to the local operating-system user. Moze Studio does not separately encrypt these files at the application level. Device security, operating-system permissions, and any disk encryption configured by the operator protect the local installation.

Original videos, prepared copies, generated media, captions, queue records, and logs remain on the Mac until removed by the operator or an applicable deletion control. There is no general automatic retention deadline. The public website does not store the local app’s credentials or video library.

Disconnecting and deleting information

The local Connections controls provide Disconnect YouTube and Disconnect Instagram. Disconnection pauses new publishing, requests revocation of the selected provider’s authorization, and removes that provider’s locally saved authorization token, account identity, upload journal, and saved API-result fields. If an upload is already in flight, new publishing is paused and the app asks the operator to retry disconnection after that request finishes. Local cleanup failures are reported. If remote revocation fails, the app reports this and links to the provider’s account settings.

Application client configuration, original and generated videos, prepared media, and minimal records used to prevent accidental reposting remain. Historical logs and manually created backups may retain account-related information and need separate removal. To delete retained media or local working files, remove them from the local workspace. Removing local files does not delete videos already uploaded or published; manage those through YouTube Studio or Instagram.

You can independently revoke Google access in Google Account connections and remove Meta access in Facebook Business Integrations. A video already scheduled on YouTube may still publish unless its schedule is changed on YouTube.

This public website

This is a static information site. It has no registration form, upload form, advertising, analytics scripts, or tracking cookies added by MozeTech. When hosted on Cloudflare, Cloudflare processes requests to deliver and protect the site and may handle technical request data such as IP addresses, browser information, and request times under its privacy policy. Links to other services are governed by those services’ policies.

Contact and changes

For questions or a data request, contact MozeTech on X. Do not send passwords or authorization tokens. Because the publishing app stores its working data locally, deleting data from the operator’s device generally requires action on that device. This policy will be updated when the app’s data practices change; the effective date appears above.