Privacy Policy

Last updated: 2026-07-16

Overview

AIRMIDA Studio helps creators prepare, review, approve, and transfer short-form video drafts and related metadata to selected social providers. This policy explains the information used for those workflows.

Information we may process

Account, workspace, and contact information you provide.
Content ideas, captions, scripts, media, revisions, approvals, and publication-job status.
Basic social-provider profile information and non-secret account identifiers after authorization.
Connection status, granted scopes, expiry state, and operational logs needed for security, debugging, idempotency, and audit evidence.

TikTok data use

The initial integration requests user.info.basic to show the connected creator identity and video.upload to transfer an approved draft to TikTok. AIRMIDA does not request Direct Post for the initial review target. The creator must review, edit, and complete posting in TikTok.

How information is used

Provide creator workflows, revision history, approvals, and requested social-provider transfers.
Show connection and job status without exposing credential values.
Protect the service, prevent duplicate operations, investigate failures, and maintain audit evidence.
Respond to support, access, correction, disconnection, or deletion requests.

Human approval and publication boundary

AI output is not final publication authority. The creator approves an exact content version. A material revision invalidates prior approval. For TikTok Upload Draft, the creator must still review and complete posting in TikTok.

Sharing

AIRMIDA does not sell creator content or account data. Information may be sent to a selected social provider when the creator authorizes a workflow, and to infrastructure or service providers only as needed to operate and protect the service.

Retention and deletion

Information should be kept only while needed for the workflow, security, audit, legal, or support purpose for which it was collected. To request access, correction, disconnection, or deletion, email [email protected]. Provider-side data remains subject to the provider's own controls and policy.

Security

OAuth tokens and connection secrets are intended to remain in private runtime storage and must not appear in public pages, committed files, Markdown reports, or chat transcripts. No internet transmission or storage method can be guaranteed completely secure.

Changes to this policy

We may update this policy as the service changes. The date above identifies the latest version.

Contact

Email: [email protected].