Privacy Policy

This release-candidate draft describes current information handling across the AI Media Studio website, licensing services, desktop application, and live Community and Arena features. External counsel and the operator must approve the final policy, business identity, contact details, retention schedule, and applicable rights before paid launch.

Data Stored on Your Mac

The desktop app stores project metadata, prompt history, settings, notes, usage records, and indexes in a local SQLite database. Generated media, reference files, exports, and recovery backups are stored as files on your Mac. Provider credentials and the local license record are encrypted using the operating system's protected storage where supported and written with owner-only file permissions. Arena saved setups, private comparisons, and personal preferences are also stored in local app storage. This local content is not uploaded to AI Media Studio merely because it exists on your device; publishing and signed-in Arena activity have the separate data flows described below.

Information Used by Hosted Services

• Supabase stores account, license, activation, machine-identifier, usage, and webhook records, plus Community profiles, publication drafts, comparison prompts and settings, uploaded assets, ballots, votes, challenge submissions and feedback, reports, moderation records, ratings, and Arena activity events.
• Stripe processes checkout, payment, customer, refund, dispute, and related transaction metadata.
• Vercel hosts the website and licensing API and processes ordinary request metadata and runtime logs.
• Resend processes recipient addresses and transactional license/recovery email content.
• Upstash processes rate-limit keys and request metadata needed to enforce shared abuse controls.
• Support systems process the messages and attachments you choose to send.

Third-Party Provider Transmission

AI Media Studio uses a bring-your-own-key model. When you submit a generation or editing request, the app sends the selected prompt, reference images, generation settings, and required technical metadata to the third-party provider you chose. Generated AI output is returned by that provider and saved locally. Each provider controls its own retention, training, safety review, geographic processing, and deletion practices; review that provider's policy before sending sensitive content.

Adobe Firefly API and browser-session integrations are disabled in version 1.0.0. If a later reviewed release enables either path, the policy must be updated to describe the content and session data sent to or stored for Adobe.

How We Use Information

• Deliver, validate, and recover software licenses.
• Link an authenticated account to a confirmed purchase.
• Diagnose product and account support issues.
• Process payment events, deliver transactional email, monitor health, and prevent abuse.
• Host selected comparisons, reveal and reuse their setups, run Community voting and creator challenges, calculate aggregate model rankings, and record publication review and reports.
• Understand Arena discovery and use through the limited signed-in activity events described below.

Community and Public Data

Community and Arena are live on the website and in the desktop app. Browsing public comparisons, creator profiles, challenges, and aggregate model rankings is available without signing in. Publishing sends the selected images and generated share assets, the full comparison prompt, title, provider/model details, settings, and supplied cost/timing metadata to the hosted service. A saved publication draft can remain there even if upload or submission is interrupted. Local comparison and Export ZIP actions do not by themselves publish your work.

• Approved, publicly listed comparisons can appear in Arena, creator profiles, and discovery. An approved unlisted comparison can be opened by anyone with its share link; unlisted does not mean confidential. Drafts and pending or rejected submissions are excluded from public comparison delivery.
• Shared images, titles, prompt excerpts, and creator attribution can be public. Voting reveals the full prompt, model identities, settings, and supplied cost/timing details. Publicly listed revealed or dual comparisons can also expose those recipes through model discovery; completed challenge finalists can expose their recipes and aggregate feedback. Blind mode does not keep a published prompt secret.
• Profile handles, display names, avatars, biographies, website links, and X usernames are public profile information when provided. A display name or avatar may come from your sign-in provider. Email, license keys, and provider credentials are not part of the public profile display.
• Comparison images are delivered through expiring application links backed by private Storage buckets. Approved public and unlisted images remain shareable through those links. Download and reveal choices restrict the assets the service delivers; they cannot prevent a viewer from copying an image already displayed.

Arena Votes, Activity, and Reports

Community and challenge voting require sign-in. Hosted ballots and vote receipts are associated with your account. Community vote processing also records server-generated hashes of IP address and user-agent metadata for integrity checks. Eligible Community votes contribute to aggregate model rankings; creator challenge judgments and their structured feedback contribute to separate creator results.

While signed in, the desktop app sends limited Arena events such as opening Arena, viewing or inspecting images, voting, revealing, saving or using a setup, completing a round, and completing a generation started from an Arena setup. These events include your account identifier, event type, sample/private/Community source, timestamps, and, where relevant, model identifier, Community comparison identifier, and duration. This event payload excludes prompts, image contents or locations, private comparison names, local file paths, and provider credentials. Guest sample activity stays local.

Signed-in users can report a comparison for misleading content, abuse, copyright, or another concern. The service stores the reporter's account identifier, comparison identifier, reason, details, and status. Publication review records include the moderator, decision, and reason. Review and reporting controls exist, but final moderation, appeal, copyright, retention, and deletion policies still require operator and legal approval; this draft does not promise a review or response time.

Sharing and Sale

We do not intend to sell personal data. Data is disclosed to the third-party providers and infrastructure processors described above for generation, publishing, voting, account, purchase, security, email, support, and legal purposes. Material shared through Community is also disclosed to its viewers as described above. The final policy must identify the legal operator and any additional processors before launch.

Security

Controls include encrypted local credential storage, owner-only sensitive files, HTTPS endpoints, restricted server credentials, exact-origin CORS, rate limiting, webhook signature verification, and private licensing data. No system can guarantee absolute security. Send suspected incidents to support@aimediastudio.app without including API keys or other secrets.

Data Retention

Local SQLite and generated media remain on your Mac until you delete them or the storage is otherwise removed. Provider-held content follows the selected provider's policy. Hosted license, activation, payment-event, email, rate-limit, and support records are currently retained for operational, fraud-prevention, recovery, dispute, and legal needs. Hosted Community data includes unfinished drafts and uploads, public and unlisted publications, profiles, ballots and votes, challenge submissions and feedback, ratings, reports, moderation records, and signed-in activity events. These Community records have no approved automatic deletion schedule. An image-link or ballot expiry is an access limit, not deletion of its underlying record or image. Exact retention periods and deletion exceptions remain release blockers documented in the operator retention matrix.

Deletion and Privacy Requests

You can delete local projects and generated media using the app and Finder, subject to any backups you control. For account, license, Community, support, correction, access, or deletion requests, email support@aimediastudio.app. Deleting a local image, uninstalling the app, or signing out does not delete an uploaded comparison, profile, or hosted vote. There is no complete self-service hosted account-deletion flow at present. Hosted requests require identity verification and review of affected database records, Storage objects, derived ratings, and applicable legal exceptions. Removing material from this service cannot remove copies held by other people. Final jurisdiction-specific rights, response deadlines, and the complete operator deletion procedure still require legal review and verification.

Contact

For privacy questions or requests, contact support@aimediastudio.app.