Privacy Policy

Who we are

Creator Brain is operated by DB Marketing LLC. It provides private brand workspaces where brand teams organize ads and creators receive video coaching. This policy describes the app's current data handling.

Information we collect and why

• Account and access details: email addresses, profile details, sign-in records, brand memberships, roles and invitations. These let us sign you in and give you access to the right workspace.
• Brand materials: brand settings, concepts, approved facts, concerns, uploaded ads, video copies, notes and breakdowns. These support the brand's ad library and coaching.
• Private practice: creators' uploaded videos, chosen concepts, ideas and coaching results. These provide feedback to the creator who uploaded them.
• Connected Meta data: authorized ad account identifiers, names and currency; ad identifiers, names, creative details, spend and reporting dates; and available video files and Page information needed to retrieve authorized media. These identify qualifying ads and bring them into the brand's private library.
• Connection and service records: encrypted Meta credentials, temporary connection verification records, download progress, request pauses and error details. These keep connections secure and help prevent repeated or failed requests.

Connecting Meta

Only a brand owner can connect Meta and select an accessible ad account for that brand. Creator Brain requests ads_read, pages_show_list and pages_read_engagement for read-only ad and authorized Page-media access. Available information depends on Meta's permissions and the assets you authorize.

The app does not request ads_management and does not launch, edit, pause or delete Meta ads or change budgets. Meta credentials are encrypted and kept on the server, not shown to creators or stored as Meta tokens in your browser.

Disconnect Meta removes that brand's saved credentials, selected account and pending connection records. It stops future sync through that connection. It does not delete previously imported ads, spend, videos or breakdowns, or revoke Facebook-wide authorization. You can also manage Creator Brain's authorization in your Facebook account settings.

Who can access your information

Access is restricted by brand membership and role. Owners and strategists can see their brand's spend figures and review ad breakdowns. Creators see the material shared with them, not raw spend figures or unapproved AI breakdowns. A creator's practice videos and reviews are accessible only to that creator, not other creators or the brand team.

Lovable Cloud provides account sign-in, the database and private file storage. Lovable AI Gateway processes videos and coaching requests using Google's Gemini video model. Video bytes, relevant brand facts, concept information and, for creator coaching, approved reference notes are sent for analysis. Generated results are stored in the app. Processing a private video requires these service providers to receive it; private access inside the app does not mean that no provider processes it.

If you choose Google or Lovable sign-in, that provider handles the sign-in and returns account information to the app. Meta handles the separate Meta authorization and data requests. These providers apply their own privacy terms.

The current video-analysis code uses Gemini 3.8 Flash through Lovable's chat-completions service. The authenticated model catalogue labels that specific service as zero provider retention; the same model's separate Interactions service is labelled provider-retained and is not used by this code. This does not mean that the app's saved videos, results or Lovable activity logs have zero retention.

Lovable's privacy policy says app end-user data, including app usage data, is not used to train Lovable's models. It distinguishes this from prompts, files and other content supplied to the Lovable builder chat, which follow separate training settings and terms. App records are not automatically builder-chat content; if an operator copies them into the builder, that is separate processing.

Lovable documents that enabling “AI app context” keeps full AI requests and responses for 90 days; when off, request summaries are still recorded. This project's AI app context setting and summary retention have not been verified. Extended-retention models are enabled for the workspace, but that does not change the current endpoint's catalogue label or prove that every model has zero retention. No EU-only processing setting was verified. See Lovable's AI documentation and privacy settings documentation.

Browser storage and other services

The app saves sign-in session information in browser storage to keep you signed in. It uses temporary browser storage to remember the page to return to after sign-in and to avoid repeating import attempts. These are separate from visitor analytics. Sign-in services may use their own cookies or storage.

We load fonts from Google Fonts. Your browser requests font files from Google, which receives request information such as your IP address and browser details. See Google's privacy policy.

Visitor analytics

Visitor analytics and click tracking are enabled on the published site. Lovable records pages visited, where visitors came from, their country, browser, operating system and device type, time on page, loading speed, errors, and clicks on buttons and links. The app sends error reports to Lovable; no additional custom app events were found.

There is no connected consent banner. Clicks are recorded for every visitor, as are page visits, time on page, page speed and errors, without cookies and without identifying a person. Analytics stores nothing in visitors' browsers. Lovable's public documentation describes a random identifier for each visit, discarded when that visit ends, and no profiles across separate visits. This is not a claim that all identifiers are absent.

Lovable's platform-provided analytics specification says it does not keep visitors' IP addresses, identifies clicks by position rather than text, keeps detailed data for 90 days and daily summaries for a year. These specifics are not stated in the current public analytics documentation and were not independently verified against the hosted script. They are attributed platform statements, not promises about all hosting, security or sign-in logs. See the public analytics documentation. The editor preview is not counted.

Lovable collects this data for us. Lovable's privacy policy explains how it handles it.

Retention and deletion

Imported ads, spend, private videos and breakdowns currently remain stored after Meta is disconnected or the winning-ad threshold changes. The app does not currently have automatic expiry for this content or a complete account or brand deletion workflow.

No automatic expiry for account details, brand materials or practice videos was found in the app code. Lovable documents daily database backups kept for up to roughly 14 days, excluding storage files; this project's backup inventory has not been inspected. Provider logs and AI activity records have separate rules and are not erased merely by deleting live app records.

For privacy questions or deletion requests, contact parker@kiauraeyewear.com. Include your app email, brand and requested scope, never passwords or tokens. Read our data-deletion instructions for information about verification, scope, file cleanup and completion. The contact is owner-confirmed; mailbox delivery has not been tested here.

Your choices and rights

You can sign out and, if you are the brand owner, disconnect Meta. Depending on where you live, you may have rights to access, correct or delete personal information, restrict its use, or complain to a privacy authority. Contact parker@kiauraeyewear.com to discuss a request. Rules differ by country; the operator should have the final policy checked for the places its users live.

Changes to this policy

We will update this page when our data handling changes. The date at the top identifies the latest revision.