Self-host for full control, or use the hosted service with published sub-processors and the same BYO-provider model.
Hosted routes use HTTPS, and provider credentials are encrypted before they are stored. API keys are stored as hashes, not raw bearer secrets.
Self-hosted deployments keep the app, database, rank history, sessions, provider credentials and audit logs in infrastructure you operate. Self-host runs with no sub-processors.
Bring your own SERP and analytics providers. Credentials stay scoped to your project, are encrypted at rest, and provider costs remain between you and the provider.
Owner, Admin, Editor and Viewer roles gate project access, and an Auditor role can read audit records. Sensitive account, team, provider, key, schedule and data changes write redacted append-only audit records.
Security reviews can map clear data boundaries: hosted service sub-processors are listed below, self-host has none, and teams can export data through CSV, JSON packages and the REST API.
A monitored email channel accepts private vulnerability reports under the published security policy.
Account security includes two-factor authentication with backup codes, trusted-device management, and session revocation. Instance administrators can perform an audited emergency two-factor reset.
The beta has no restore guarantee yet. Keep a full-history export as the mitigation.
| Sub-processor | Region | Purpose | Scope |
|---|---|---|---|
| EU | Application hosting, managed databases and transactional email (SES) | All application data (hosting and managed database). Email addresses and message content for transactional delivery. | |
| EU | Workflow engine, background workers and cache infrastructure | Workflow state and cache contents. | |
| EU | Marketing and broadcast email delivery | Email addresses and message content. | |
| EU | Error and performance monitoring | Error reports; may include account identifiers, never provider credentials. | |
| US | Product analytics | PlannedProduct usage events. | |
| EU | Subscription billing and payments | PlannedBilling contact and subscription data. |
All hosted data is stored in the EU today. A US region is planned; you will choose a region when it ships. DATA_REGION surfaces the selected region in authentication and onboarding.
Last updated: August 9, 2026. Changes are announced in the changelog.