Privacy Policy

This Privacy Policy explains what personal information SEOArchitect collects, why we collect it, and how we handle it. We aim to collect the minimum needed to run the Service.

1. What we collect

Account & profile

• Email address and full name (you provide).
• Workspace name + slug.
• Password hash (Argon2; we never see your plaintext password).
• If you sign in with Google: your Google email + a stable Google subject ID, plus your profile picture URL.

Connected Google account (optional)

• If you connect Google for live data, we store an encrypted refresh token (Fernet, AES-128 GCM) bound to your workspace and the scopes you granted (Search Console read-only, Analytics read-only).
• We use it only to read GSC + GA4 data for sites you have explicitly bound.
• You can disconnect at any time from the Integrations page; we revoke the token at Google and delete it from our database.

Usage & technical data

• API request metadata (path, status, latency) for security and debugging, retained ~30 days.
• Errors captured by Sentry, scoped to release tags and stripped of request bodies.
• Product analytics via PostHog (page views, feature usage), pseudonymized.

Billing

• We do not store credit card numbers. Payments are processed by Stripe, who returns a customer ID + last-4 of the card we display in the billing page.

2. Why we use it

• To operate and secure the Service (authentication, multi-tenant isolation).
• To provide the features you ask for (analyzing sites, generating briefs, fetching live data).
• To send transactional email (welcome, password reset, billing receipts) via Resend.
• To bill you for the plan you chose, via Stripe.
• To improve the product (aggregate, de-identified usage analytics).

We do not sell your data, do not use your Customer Content to train foundation models, and do not share your live GSC/GA4 data with third parties beyond the sub-processors listed below.

3. Sub-processors

We use the following third parties to operate the Service:

• Vercel — application hosting (USA).
• Supabase — managed PostgreSQL (USA, us-east-1).
• Upstash — Redis cache (USA, us-east-1).
• Stripe — payment processing.
• Anthropic — large language models for the agent layer.
• Resend — transactional email delivery.
• Sentry — error monitoring.
• PostHog — product analytics.
• Google — only when you connect Search Console / Analytics; we read scoped data on your behalf.

4. Storage & retention

Your data is stored in encrypted-at-rest databases in the United States. We retain your account and Customer Content for as long as your account is active and for up to 30 days after deletion (to recover from accidental deletes). Billing records are retained for 7 years to comply with tax law.

5. Your rights

You can access, export, or delete your data at any time. To request export or deletion, email support@seoarchitect.app from the email address tied to your account. We respond within 30 days. If you are in the EU/UK or California, you have additional rights under GDPR / CCPA; the same email is the entry point.

6. Cookies

We use a small number of strictly-functional cookies + localStorage entries to keep you signed in (JWT access + refresh tokens). PostHog sets its own cookie for product analytics; you can opt out via your browser’s Do Not Track signal or by deleting the cookie. We do not use advertising cookies.

7. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from them.

8. Changes

We may update this Privacy Policy from time to time; the effective date above will reflect the latest version. Material changes will be communicated by email at least 7 days before they take effect.

9. Contact

Privacy questions can be sent to privacy@seoarchitect.app (or support@seoarchitect.app if you prefer).

Note: this is a template starting point, not legal advice. Have a lawyer in your jurisdiction review it before relying on it, especially the GDPR and Canadian PIPEDA-specific language.