Security

1. Account Data Isolation

Every table that stores your account data — profile, audit jobs, audit results, and payment records — has PostgreSQL row-level security (RLS) enabled and enforced by the database itself, not just by application code. Policies scope reads and writes to your own account (auth.uid()), so one signed-in user's queries cannot return another user's profile, private audits, or billing history.

2. Authentication

• Sign-in is handled by Supabase Auth, not custom-built session or password code.
• You can sign in with email and password, or with Google.
• We never store your password in our application database — it is hashed and managed entirely by the authentication service, standard practice for modern auth systems.

3. Payment Data

All checkout happens on Stripe's own hosted payment page. We never receive, see, or store your card number, CVC, or full billing details. Stripe passes back only a customer ID, session ID, and payment status, which we use to activate your plan.

4. Encryption in Transit

Our app, API, and database gateway are served over HTTPS only. Plain HTTP requests are redirected to HTTPS, using TLS 1.2/1.3 certificates.

5. Where Audit Data Lives

GEO & SEO Checker runs on infrastructure we operate ourselves — a self-hosted database stack behind our own reverse proxy — rather than a shared third-party platform's default multi-tenant environment. We haven't published the exact physical data center location, and we'd rather say that plainly than claim a region we can't back up.

6. Shared Audit Report Pages

When an audit finishes, it gets a results page you can share by link. Anyone who isn't the owner (and isn't on a paid plan) sees a masked summary — scores and issue titles, not detailed fix instructions — the same limited view a free visitor sees. Today, these results pages don't require a private access token to view; a fully private-by-default option is on our roadmap (see below).

7. Data Retention

We retain account and audit data as long as your account is active, or as needed for the purposes described in our Privacy Policy. We don't currently run an automated deletion job on a fixed schedule — if you want data removed sooner, contact us and we'll handle it manually.