Trust and security

Last updated: Nov 16, 2026

How SeePM protects the ad accounts and the client knowledge you connect. To report a security issue, write to info@seepm.app.

Your platform logins

You connect each ad platform on the platform's own sign-in screen, so SeePM never sees your password. The access it gets (a sign-in token, or an API key you paste) is stored encrypted in Supabase Vault, apart from everything else.

That access never goes into an AI chat. Your AI asks SeePM, and SeePM makes the request to the platform. Disconnecting a platform in Settings deletes the stored token; for Google, it also revokes the access with Google.

Signing in

Two-step sign-in is required for every person, with an authenticator app or a passkey. Once it is set up, the database itself refuses to return client data to a session that skipped the second step, so the check does not depend on the app alone.

An AI app you connect, like Claude or ChatGPT, signs in through SeePM as you and gets exactly your permissions. You can remove it any time in Settings.

Keeping organizations and clients apart

Every record carries the organization it belongs to, and the database returns only your organization's rows. Inside your organization, roles decide who sees and changes which clients, and each client's ad accounts stay with that client.

Changes to ad accounts

  • Your team's roles decide who can change what, and which changes wait for someone's approval.
  • A change that waits is approved on its own page in SeePM, never with a button inside the chat. High-risk changes take a code or a passkey.
  • Money changes must state the account's currency, count toward a daily money limit, and are read back from the platform after they run.
  • Every request to an ad platform is logged: which tool, for which client, and whether it worked.

Client knowledge

SeePM keeps what you and your team teach it about each client: goals, audience, targets, what worked. It never saves a password, key or access token there. The lines SeePM writes on its own, from your sessions, never keep an email address or a phone number, so the details of your clients' customers and leads stay out.

Where data is kept

The database, sign-in and encrypted token storage run on Supabase in the United States (AWS us-east-2). The web app runs on Vercel and the services that talk to the ad platforms on Railway, with every connection encrypted (HTTPS). The AI providers behind SeePM's own assistant work under terms that do not let them train on your data.

Who processes what, retention and deletion: How your data is handled. The full policy: Privacy Policy.

Report a security issue

Write to info@seepm.app with what you found and how to reproduce it. We read every report and reply. Please test only with accounts you own, do not access or change other people's data, and give us time to fix an issue before you publish it.