Privacy Policy
Effective date: June 9, 2026
AI Audience Studio provides creator workflow tools for planning, reviewing, and preparing short-form product video drafts. This policy explains what information may be processed when a creator or reviewer uses the service.
Information We Process
- Account connection data, such as OAuth authorization codes, access tokens, refresh tokens, token expiry data, and connected account identifiers when authorized by the user.
- Creator workflow data, such as product names, product links, audience notes, captions, script instructions, approval commands, and draft status.
- Uploaded or generated media, such as product reference images, scene clips, subtitles, and final video draft files.
- Technical data, such as application logs, setup status, browser automation status, error messages, and API response metadata needed to operate the workflow.
How We Use Information
- To create, manage, and review content draft jobs requested by the creator.
- To connect authorized accounts and prepare uploads or drafts only when the creator initiates or approves that action.
- To send review notifications and receive approval commands through configured messaging tools.
- To diagnose errors, protect the service, maintain audit records, and improve workflow reliability.
Third-Party Services
Depending on the project configuration, AI Audience Studio may interact with third-party services selected by the project owner, including social platform developer APIs, messaging APIs, AI model providers, browser-based generation tools, cloud tunnel providers, and hosting infrastructure. Data sent to those services is limited to what is needed for the configured workflow.
Publishing Control
The service is designed around human review. Drafts are not posted by default. Upload or publish actions require creator authorization, configured account access, and an explicit approval or upload command.
Retention
Product records, job records, media files, and tokens are retained while needed for the creator workflow, debugging, compliance, or account connection. The project owner may delete tokens, generated files, and product data when they are no longer needed.
Security
The reviewer dashboard is protected by access control. Secrets and tokens are not displayed in plain text in the setup screen after they are saved. No system can guarantee perfect security, but reasonable access controls and secret redaction are used to reduce risk.
Deletion Requests
Users may request deletion of connected tokens, product records, generated drafts, and media files through the project owner or the contact information supplied in the relevant developer app review submission.
Changes
This policy may be updated as the service changes. The effective date above will be updated when material changes are made.