Last updated: April 2026
For data you submit on the platform (articles, prompts, settings), you — the client organization — are the data controller and we act as your data processor under the Data Processing Agreement available at /legal/dpa. For account data (email, login history, billing contact), we act as the data controller.
Account & identity. Email, display name, role on each client workspace, login timestamps, password hash (never the plaintext password), 2FA secrets.
Usage telemetry. Pages visited, actions taken, feature flags, error reports (via Sentry, with secrets scrubbed before transmission), anonymized product analytics (via Posthog where enabled).
Content. Articles, keywords, persona settings, pSEO templates, connected CMS configuration, generated HTML, quality reports.
Credentials you entrust us with. API keys for third-party AI providers (Anthropic, OpenAI, Gemini, Pinecone, DataForSEO, Placid), CMS access tokens (Webflow, WordPress, webhooks). These are encrypted at rest with AES-256-GCM using a key derived via scrypt, and only decrypted in-memory at the moment they are needed to serve a job. They are never returned to the browser, never logged, and scrubbed from error reports via lib/sentry-scrub.ts.
We do not collect. Payment information (billed out of band), real names beyond what you voluntarily provide, biometric data, government IDs.
We host infrastructure on a small number of trusted sub-processors. The current list is published in our Data Processing Agreement at /legal/dpa and includes at a minimum: Supabase (database + auth), Vercel (hosting), Trigger.dev (background jobs), Upstash (rate limiting), Resend (transactional email), and Sentry (error reporting). We notify client administrators at least 30 days in advance of any new sub-processor being added.
Primary database storage is located in the region chosen at onboarding (EU or US). Some sub-processors, notably AI providers, may process request payloads in a different region for the duration of a single request. Where your AI provider supports regional endpoints, configure the endpoint URL on your client workspace to keep inference in your preferred region.
articles, client_config, client_secrets, client_personas, client_prompts, client_integrations, client_invitations, and associated audit trail.If you are in the European Economic Area, the United Kingdom, or another jurisdiction with similar protections, you have the right to:
To exercise any of these rights, email privacy@p-seo.com. We respond within 30 days.
We protect your data with transport encryption (TLS 1.2+), at-rest encryption (AES-256-GCM for secrets, managed disk encryption for databases), row-level security policies on every multi-tenant table, service-role access scoped to backend processes only, rate limiting on authentication endpoints, optional 2FA for administrator accounts, an audited secret rotation procedure, and point-in-time recovery backups. Incidents affecting personal data are notified to client administrators within 72 hours of confirmation, consistent with Art. 33 GDPR.
See our Cookie Policy for the exhaustive list of cookies we set and how to control them.
Data Protection inquiries: privacy@p-seo.com.
General support: hello@p-seo.com.