Customer and provider data
Authorized website, repository, CMS, analytics, search, ranking and backlink observations required for configured workflows.
Explore SEOForge
Data processing · updated 20 July 2026
Customer data should have a defined purpose, scope and end state.
This public overview supplements the Privacy Policy. Contractual controller/processor terms, transfer mechanisms and retention commitments are governed by the executed agreement and any data processing addendum.
Nothing publishes without approvalPaid product accessNo ranking guarantees
Processing path
Authorize → ingest → normalize → operate → audit → retain or delete
Data classes
The workflow determines what is processed.
Operational artifacts
Runs, activity summaries, evidence, findings, drafts, media, proposals, validation, approvals and usage records.
Credentials and configuration
Provider tokens and connection metadata are restricted to the integration path; raw credentials should not enter agent prompts.
Security and audit records
Identity, access, decisions, failures and delivery events may be retained to operate, protect and support the service.
Lifecycle principles
Retention is record-specific, not one universal timer.
- Collect and process for documented service purposes
- Scope access by tenant, site, environment and role
- Encrypt in transit and at rest where applicable
- Redact secrets from model and public contexts
- Allow connection revocation and supported data requests
- Retain billing, security or legal records only where justified
Deletion and portability
Workspace administrators can revoke connections. Access, export, correction or deletion requests may require identity and authority verification. Deletion can be limited by backups, fraud prevention, billing, dispute or legal obligations and the executed agreement.
Production boundary
Processing permission is not publishing permission.
Authorizing a provider allows the configured collection or preparation workflow. A separate authenticated human decision is required for each consequential production proposal. API, CLI and MCP access cannot approve, merge, deploy, retrieve credentials or bypass protection.
Paid deployment · human authority
Review processing terms against your actual provider and site architecture.
Contact sales for available contractual documents and scope-specific answers.