Data & Privacy

Your data is yours

The agency that signs up for SeePM (the customer) owns the data it puts into SeePM and the data SeePM reads from its ad accounts. SeePM processes that data on the customer's behalf and on its instructions, to provide the service — in data-protection terms, the customer is the controller and SeePM is the processor. We do not sell it, use it for advertising, or use one customer's data to serve another.

What SeePM stores

• Your account and team — names, email addresses, organization and roles.
• Clients — the advertisers you manage in SeePM, and who on your team works on each.
• Ad account links — which Google, Meta, TikTok, LinkedIn or Apple ad account belongs to which client (account IDs and names).
• Brain documents — the knowledge you and the assistant write about each client and your agency, with their revision history.
• Platform sign-in tokens — the OAuth tokens (or API keys) you grant when you connect an ad platform or an AI provider. They are stored encrypted in Supabase Vault and used only to make the requests you or your team ask for.
• Tool call logs — a record of each request made to an ad platform or to SeePM's own tools: which tool, for which client and conversation, the parameters sent, and whether it succeeded. The log records the size of each answer, not its content.
• Conversations — your chats with the in-app assistant, and the reports, findings and approvals that come out of them.

Campaign data (spend, clicks, conversions and the like) is fetched from the ad platforms when it is needed. It is stored only where it becomes part of something above — for example a report you save, a finding, or a conversation in which the assistant quoted it.

Where it is kept

The database, sign-in and encrypted token storage run on Supabase in the United States (AWS us-east-2) region. The web application runs on Vercel, and the services that talk to the ad platforms run on Railway. Data is encrypted in transit (HTTPS) between all of them.

Who else processes it (subprocessors)

• Supabase — database, authentication, encrypted token storage.
• Vercel — hosting of the SeePM web application.
• Railway — hosting of the services that call the ad platform APIs.
• Ad platform APIs — Google Ads, Meta, TikTok, LinkedIn and Apple Ads receive the requests made to the accounts you connect. Each one already holds your ad data under your agreement with it.
• AI model providers — only for SeePM's in-app assistant. By default the assistant runs on Google's Gemini models through SeePM's own account. If your organization adds its own key for Anthropic, OpenAI, Google AI or Mistral, the assistant uses that provider under your key instead. The provider receives the conversation and the data the assistant looks up to answer it.
• Supporting services — Inngest (background jobs), Resend (transactional email), Lemon Squeezy (billing) and, when enabled, Langfuse (diagnostic traces of assistant runs).

Using SeePM from your own AI assistant

You can connect your own AI assistant — for example ChatGPT, Claude or Codex — to SeePM through the SeePM MCP server. In that case the assistant is not a SeePM subprocessor: it is governed by your own agreement with its provider (OpenAI, Anthropic or another). SeePM authenticates the person connecting, applies the same permissions they have in SeePM, logs each call, and returns only the data the assistant requests. What the assistant then does with that data is between you and its provider.

Retention and deletion

• We keep your data for as long as your organization uses SeePM.
• We do not currently delete data automatically on a fixed schedule. If you need a specific retention period, ask us and we will apply it to your organization.
• Disconnecting a platform in Settings deletes your stored token (and, for Google, revokes the authorization with Google). You can also revoke SeePM's access in the platform's own security settings, which invalidates the token immediately.
• On request we will export your organization's data, or delete it — clients, account links, brain documents, tokens, tool call logs and conversations. Write to us from an address on your account.