How we keep your data safe
A plain-English summary for you and your IT team: where data lives, who can see it, and what you can do with it.
Where your data lives
Established infrastructure
The app runs on Cloudflare’s global network. Data is stored in a Supabase (PostgreSQL) database. Payments go through Stripe, and Google data comes from Google’s own APIs. Each of these providers publishes independent security reports, such as SOC 2, and Stripe is PCI DSS Level 1 certified.
Encrypted in transit and at rest
Every connection uses HTTPS. The database is encrypted at rest by our provider, and we encrypt Google access tokens and WordPress connection keys again with our own key before storing them.
No card numbers stored
Plan payments and client deposits happen on Stripe’s checkout. Card details never reach our servers.
Who can see what
Row-level access per workspace
Every table in the database checks who is asking. Team data is limited to the workspace’s admins and managers, and a client login sees only that client’s portal. Tables holding tokens, payments and private links can’t be read from a browser at all.
Roles you control
Admins invite their team as admins or managers and decide which clients get portal access. Only admins change roles, plans and billing.
Google data stays per person
Search Console and Google Analytics are read-only connections made by each person, to the properties they choose. Disconnecting deletes the stored tokens. Google data is never used to train AI models. See the privacy policy for details.
How the app protects itself
Verified connections
Background jobs, email triggers and payment webhooks prove who they are with secrets or signatures before anything runs. Onboarding links are long random tokens that we store only as hashes, and they expire.
Browser protections
Security headers on every page block framing by other sites, content sniffing and plain-HTTP connections. Server actions are protected against cross-site requests.
Safety nets and monitoring
Public forms have spam protection and rate limits. A fair-use safety net pauses runaway AI or crawling use. Automatic health checks alert us to failed or stuck work and unusual spend.
AI handled with care
Website content and client answers are passed to AI as data, not instructions. AI output is shown as plain text, and the team reviews AI-written content before a client sees it.
Your data, your call
Export any time
Settings → Profile → Export my data downloads your account, plus the workspaces you own or administer, as a file. Secrets such as tokens are never included.
Delete when you leave
Cancelling keeps your data for 30 days so you can come back. The person who created the workspace can delete it and its files right away, and anyone can delete their own account in Settings. Ask us and we’ll delete it for you.
Requests answered
Privacy and data requests get a reply within 30 days through our data request form.
Compliance
We’re an early-stage company and don’t hold our own SOC 2 report yet. Our infrastructure providers do, and we’re glad to fill in your security questionnaire. If your organization needs a specific certification or agreement, tell us, so we can plan for it.
Report a security issue
Found something that looks like a vulnerability? Email privacy@searchobservatory.com with “Security report” in the subject, or use the data request form. Please give us a chance to fix it before sharing it publicly. We’ll reply quickly and keep you updated.
See also the privacy policy and terms of service.