Safe by Design, Honest by Default.
Encryption, least-privilege access, and connected-account scopes — plus what we deliberately never do.
Encrypted Everywhere
TLS in transit and at rest. Connected Google tokens are encrypted with a dedicated key, never stored in plain text.
Least Privilege
We request only read scopes on Search Console and Analytics, and only when you connect them. No write access, ever.
Isolated by Tenant
Every project’s data is scoped to its owner server-side. Team roles narrow access further — a client can only see report output.
Access Control
Sessions use single-use, expiring tokens — never passed in a URL. Passwords are hashed, minimum eight characters, and sign-ups are approval-gated rather than self-serve. Team members get exactly the role you assign (from report-only clients to full SEO managers), enforced on the server, not just hidden in the UI.
Your Connected Google Data
When you connect Search Console or Analytics, we store an encrypted, revocable token for the read scopes you grant. We use it only to compute the signals you see in the app. Disconnect at any time from Integrations, or revoke access directly in your Google account — either fully cuts our access.
What We Never Do
- We never sell your data.
- We never use your audited content or connected data to train models.
- We never ask for, store, or transmit your Google password — connection is OAuth only.
Reliability & Honesty
The same honesty that runs through the product runs through our operations: when a crawl can’t reach something, we mark it not yet measured rather than guessing. When something breaks, we’d rather tell you than paper over it.
Responsible Disclosure
Found a vulnerability? We want to hear from you before anyone else does. Email [email protected] with the details and steps to reproduce. We’ll acknowledge, investigate, and keep you posted — and we won’t pursue good-faith researchers who follow this path.