Security
How Spuro handles your data.
Spuro connects to the accounts your business runs on. We treat that responsibility as part of the product. Here is how your data is handled, in plain words. The technical details come after.
In plain words
Who can see your data
Everything you store in Spuro belongs to your workspace, and it is kept inside that workspace. Every request that touches your data checks that it belongs to your organization before acting.
How sign-in works
You sign in with Google, or with an email and password. Signing in sets a cookie that keeps your session going. That cookie isn’t used for advertising or to track you across other sites.
What Spuro can and can’t do in your Meta account
To connect Meta, you sign in on Facebook’s own login screen, so Spuro never sees your Facebook password. Spuro stores the ad accounts and Pages you selected, and reads performance data for those accounts, such as spend, impressions and clicks. It asks for the narrowest permissions that make a feature work.
Launchpad only publishes when you press publish, and it adds your ads to ad sets you already set up. Brain never touches your ad account.
Where your uploaded videos go
Videos you upload are stored in your Spuro account. When you upload a video, its audio goes to an outside service that writes a transcript. When you run an analysis, still frames from the video go to an outside AI service that writes the notes.
What we don’t do with your data
We do not sell your data, and we do not use your private business data to train AI models. Ad copy, creatives and results generated for your workspace are yours.
How your connected accounts are protected
The access tokens for the platforms you connect are encrypted. They are only used on Spuro’s servers and are never sent to your browser.
How to delete your data
You can request deletion of your account and its data at any time. The Data deletion page has the steps. Connected platforms can be disconnected whenever you want, which revokes Spuro’s access.
For your technical team
Technical details
The same commitments, in the terms an engineer will look for.
- One workspace, one boundary
- Everything you store in Spuro belongs to your workspace and is scoped to it at the database layer (row-level security in Postgres). Every request that touches tenant data verifies the resource belongs to your organization before acting.
- Connected-account credentials are encrypted
- Tokens for the platforms you connect are encrypted at rest with a dedicated key, on top of full-database encryption at rest. They are used server-side only and never shipped to the browser.
- Least privilege by default
- We request the narrowest platform scopes that make a feature work, and every publishing action runs through guarded server routes.
- Transport is locked down
- Production traffic uses HTTPS and HSTS, with frame embedding disabled. Content-Security-Policy is currently report-only. When configured, marketing analytics and advertising tags load only after consent. These marketing tags are not mounted on the app host. See the Privacy policy for the tools, Global Privacy Control and your privacy choices.
Questions, or something you think we should harden further? Tell us: hello@spuro.ai. Security reports get read first.