Privacy Policy

Account information

When you create an account, we process information such as your name, email address, and login data needed to authenticate you and keep your workspace secure.

Workspace and project inputs

Content you enter into MarketingMindOS — including project details, strategy notes, planners, reports, learnings, and related workspace inputs — is stored so the product can run your marketing workflows.

AI Assist

When you use AI Assist, relevant user inputs may be sent to OpenAI to generate drafts and suggestions. Those requests are used to provide the Assist feature in context of your workspace.

Intelligence providers

MarketingMindOS may use third-party intelligence providers such as Exa, Firecrawl, and DataForSEO to gather external market or search evidence that supports recommendations and research features. SEO Intelligence may use DataForSEO for external keyword volume, competition, and SERP snapshots. These providers receive the search queries or public URLs you choose to analyze; MarketingMindOS does not add new OAuth permissions for DataForSEO.

Paid performance integrations

If you connect LinkedIn Ads, Meta Ads, Google Ads, or future TikTok Ads, MarketingMindOS may read campaign performance data from those accounts. Access is for performance visibility and recommendations. MarketingMindOS does not use these connections to change budgets, creatives, or campaign settings in your ad platforms.

Disconnecting a provider clears encrypted OAuth tokens stored by MarketingMindOS and attempts provider-side token revocation where supported. Historical performance snapshots, recommendations, and learnings are retained after disconnect unless you request deletion.

Website & Search Performance

If you connect Google Analytics 4 or Google Search Console, MarketingMindOS may read website and organic search performance for your selected property or site. Access is read-only (analytics.readonly / webmasters.readonly). MarketingMindOS does not edit properties, streams, users, key events, conversions, audiences, sitemaps, or site settings.

OAuth tokens are stored server-side and encrypted. Disconnecting clears encrypted tokens and attempts Google token revocation. Historical owned performance snapshots and related learnings are retained after disconnect unless you request deletion.

OAuth tokens

OAuth tokens for connected integrations are stored server-side and encrypted. They are not exposed to the browser. Access tokens, refresh tokens, client secrets, and encryption keys are not logged in application responses or debug copy returned to the client.

Payment data

Payments are handled by Stripe. MarketingMindOS does not store card numbers.

Analytics and logs

We keep basic technical logs for security, reliability, and debugging. These may include request metadata and error information needed to operate the service.

How we use data

We use the information above to provide MarketingMindOS: generate recommendations, reports, and learnings; power Assist and intelligence features; support connected performance views; and improve the service.

Data deletion

You can disconnect paid media integrations and Website & Search connections at any time (see the Data Deletion page). You can also request deletion of your account and associated workspace data, including performance snapshots, recommendations, and learnings. Contact us using the email below and we will process the request.

Contact

Privacy questions or deletion requests: vaggelis.mintzioris@gmail.com.