Skip to content

Security

Your clients’ data, kept where it belongs

Agencies trust us with their clients’ search data. Here is how we protect it.

How we protect your data

Separated by the database

Every table that holds customer data is protected by Postgres row-level security: an organisation can only read and write its own rows, and client logins only their own client’s. Automated tests check every table, including randomised probes across roles.

Read-only Google access

Search Console and Google Analytics are connected with read-only scopes. Refresh tokens are encrypted and can never be read back by the app’s users. Google data is never sent to AI providers.

Encryption

All traffic uses HTTPS with HSTS. Stored credentials (OAuth tokens, webhook URLs) are encrypted with libsodium; the key is kept outside the database and can be rotated.

Untrusted content stays data

Web pages and AI answers are treated as untrusted data: fetched with private-network blocking and size limits, and never followed as instructions.

Hardened web app

Content-Security-Policy, no framing, strict referrer and permissions policies, per-user rate limits, and validation on every server action.

Audit trail

Changes are written to an append-only audit log in the name of the person who made them.

Infrastructure

  • Managed Postgres (Supabase); the web app on Vercel; background jobs on Railway.
  • Secrets live only in the hosting providers’ encrypted settings, never in code.
  • Payments are handled by Stripe; we never see or store card numbers.
  • Errors are monitored; platform health problems alert our team automatically.

AI providers

To measure AI visibility we send the questions you track to AI assistants’ APIs, and we use AI models to draft profiles, briefs and report summaries from your intake and public website content. Google Search Console and Analytics data is never included. See the Privacy Policy for the full list of processors.

Report a vulnerability

If you believe you’ve found a security issue, email support@zoroseo.com with “Security” in the subject and the steps to reproduce. Please don’t access other customers’ data or disrupt the service while testing. We’ll acknowledge your report and keep you updated.

Frequently asked questions

Can other agencies see our data?

No. Every table that holds customer data has row-level security in Postgres, so an organisation can only read and write its own rows. Automated tests check every table, and direct access to the database API is refused.

Can a client see another client’s data?

No. Client logins are limited by the database to their own client’s dashboard, approvals and reports.

What Google permissions do you ask for?

Read-only scopes for Search Console and Google Analytics. We can’t change anything in your Google account, and you can remove access at any time.

Is Google data sent to AI providers?

No. Search Console and Analytics data is used only for your dashboards, goals, alerts and reports.

What is sent to AI providers?

To measure AI visibility, the questions you track are sent to the AI engines’ APIs. To draft profiles, briefs and report summaries, the intake and public website content are sent to AI models. The list of providers is in the Privacy Policy.

Does ZORO SEO publish to our clients’ websites?

No. Nothing is published automatically; a person makes and approves every change.

How do I report a vulnerability?

Email support@zoroseo.com with “Security” in the subject and the steps to reproduce. Please don’t access other customers’ data or disrupt the service while testing.