Privacy Policy

SEO Autopilot is an SEO operations tool. You connect sites you control, it gathers evidence about them, and it proposes changes you review before anything is applied. This policy describes the deployment at seo.oryxenlabs.com, operated by Oryxen Labs. Questions go to [email protected].

Four kinds of thing, and nothing else:

• Your identity. When you sign in with Google we store the account identifier Google gives us, your email address and your display name. We use them to know who you are across visits and to show your name to other members of your own workspace.
• Credentials you enter. Your own Google OAuth client and GitHub App details, and the tokens that authorising Search Console, Analytics or a repository produces. These are encrypted before they are written down (see below).
• Evidence about your sites. Pages fetched from sites you have added and proved you control, and the metrics Google returns for them — Search Console impressions, clicks and positions, Analytics figures, and mobile performance samples.
• Work produced from that. Findings, ranked opportunities, proposed changes, the decisions you take on them and the outcomes measured afterwards.

We do not use advertising trackers, we do not run third-party analytics on this service, and we do not sell or share anything described here with anybody.

Signing in requests only the openid, email and profile scopes — enough to establish who you are and nothing more.

Connecting Search Console or Analytics is a separate, later, optional step, and it runs through your own Google Cloud OAuth client, which you create and control. The data those grants return is used for one purpose: producing and measuring SEO findings inside your own workspace. It is never used to train models, never used for advertising, and never transferred to anyone.

SEO Autopilot’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke our access at any time from your Google account permissions page, or by removing the connector inside the app.

Every workspace is isolated in the database itself, by row-level security policies that the application cannot bypass — it connects as a role that has no permission to. A query that forgets to name a workspace returns nothing rather than someone else’s rows.

Credentials and tokens are encrypted with AES-GCM before storage, bound to the workspace they belong to, so a row lifted from one workspace cannot be decrypted in another. Traffic is served over HTTPS only.

Being straightforward about the limit of that: the server holds the encryption key, because the server is what exchanges your credentials with Google and GitHub. This protects your data from anyone who reads the database — a dump, a backup, a replica — but not from whoever operates this deployment. If that matters for the account you are connecting, connect one scoped to only the sites and repositories you intend to use here.

Data is stored on servers in Germany, operated by Hetzner, and reached through Cloudflare. It is kept while your workspace exists. Removing a credential revokes it immediately; deleting your workspace deletes the evidence, proposals and credentials belonging to it.

Ask us at [email protected] for a copy of what is held about you, a correction, or deletion, and we will act on it. Backups are retained for a short period and roll off on their own.

If this policy changes in a way that affects what we do with your data, the date above changes and the change is described here. This service is in testing; it is not intended for, and is not knowingly used by, anyone under 16.