DATA & SAFETY

How Marketing Commander handles data

This page provides a concise overview for users. The Privacy Policy remains the controlling description of our privacy practices.

Last updated: 30 July 2026

Data you choose to provide

  • Account details such as your email address and profile information.
  • Campaign briefs, prompts, brand details, URLs and files you submit.
  • Generated content, approvals and workspace activity.
  • Support messages and feedback you send to us.

Data used to operate the service

Limited authentication, security, diagnostic, entitlement and transaction-status information may be processed to provide the service, prevent abuse and resolve failures.

Payment-card information is handled by the applicable payment provider. Marketing Commander does not store complete card details.

AI and service providers

Relevant prompts and campaign context are sent securely to server-side AI providers only when needed to perform a requested generation task. Other providers support authentication, hosting, payments, app delivery and distribution.

Current providers may include Supabase, Vercel, OpenAI, Groq, Stripe, Expo and Google Play. We do not sell personal information and do not use third-party advertising SDKs in the mobile app.

Permissions

  • Microphone access is requested only when you start a voice feature.
  • Media write access is requested only when you choose to save an asset.
  • The app is designed to avoid broad read access to your media library.

Security

We use encrypted network connections, authenticated requests, server-side credentials and workspace-level access controls. No online service can guarantee absolute security.

Your controls

  • Review and approve generated work before publishing.
  • Request access to or correction of your information.
  • Delete stored content where the product provides that control.
  • Request deletion of your account and associated data online.
Open account deletion

Important

The information submitted in an app store’s Data safety form must match the behavior of the released app and every included third-party SDK. This public overview does not replace that store declaration.