SEOGrowPilot
Sign in

Security

You are about to give a piece of software your analytics, your CMS login and permission to change your website. These are the specific things it does about that.

Tenant separation
Every query is scoped to the organisations you belong to, at the database layer rather than in the interface. A request for something in another organisation returns 404 and not 403 — a 403 confirms the thing exists, and whether a competitor is a customer of ours is not ours to disclose.
Credentials
Google tokens, CMS logins, and your own AI provider keys are encrypted with AES-256-GCM before they are stored, under versioned keys so a key can be rotated without a migration. They are never returned by any API and never shown back to anyone, including us. Delete the connection and the stored credential is destroyed.
The audit log cannot be edited
Every change, approval, credential event and administrative action is appended to a hash-chained log. The database rejects updates and deletes to it outright, so a record cannot be altered afterwards — not by an administrator, not by us. Two consequences follow, and both are deliberate: a mistake is corrected by a second entry rather than a rewrite, and no secret may ever be written to it, so the log records credential field names, never values.
Permissions are checked on the server
Fourteen roles, granular permissions, and a check on every action at the point it happens. Nothing is authorised because a button was visible; hiding a control is a courtesy to the user, not a security measure, and the software treats it that way.
Two platform roles, and what they do not reach
Your organisation's roles govern your data. Our platform roles govern the platform — deployments, plans, system health. A platform role does not grant access to a customer's data, and there is no impersonation feature: we cannot sign in as you.
Sign-in
Passwords are hashed with bcrypt, sessions are short-lived JSON web tokens, and time-based two-factor authentication is available to every account and expected on any account with administrative rights.
Client portal links
An agency client portal has no account and no password: the link is the credential. It is shown once when created, it is read-only, it is scoped to one client's websites, and it can be revoked at any moment. Treat it as you would a password, issue one per client, and revoke it when the engagement ends.
Your data leaving
Export is available on every plan and stays available when an account is past due. We do not withhold data over a bill.

Reporting something

If you believe you have found a vulnerability, write to security@seogrowpilot.com with enough detail to reproduce it. We will not pursue anyone who reports a genuine finding in good faith and gives us a reasonable opportunity to fix it first.

How it worksPricing

Questions people ask

›What access does SEOGrowPilot need to my Google account?

Read-only access to Search Console and to Analytics, granted by you through Google's own consent screen and revocable from your Google account at any time. It is never used to post, change or delete anything, the tokens are encrypted before they are stored, and disconnecting destroys them.

›Can SEOGrowPilot staff see my passwords or API keys?

No. Credentials are encrypted with AES-256-GCM before they are stored and are never returned by any API or shown in any interface, to you or to us. The audit log records that a credential changed and which fields it had, never the values, because an append-only log cannot be redacted afterwards.

›Can someone at SEOGrowPilot log in as me?

No. There is no impersonation feature. Our platform roles govern the platform — deployments, plans, system health — and do not grant access to a customer's data. Every action is checked on the server at the point it happens and written to the audit log.

›Where is my data stored?

In managed PostgreSQL and Redis on our hosting provider, with the encryption and access controls described above. If you need a specific region or a data processing agreement for a procurement process, ask before you sign — we would rather tell you what we can and cannot offer than discover it afterwards.

›Is SEOGrowPilot ISO 27001 or SOC 2 certified?

No, and we will not imply otherwise. The controls on this page are real and enforced in the software, but they are not the same thing as an audited certification, and no amount of description substitutes for one. If a certification is a requirement for you, say so and we will tell you honestly where we are.

›How do I report a security problem?

Email security@seogrowpilot.com with enough detail to reproduce it. We will acknowledge it, and we will not threaten anyone who reports a genuine problem in good faith.