DPS

Data Processing Schedule

This schedule outlines the categories of data, purposes, and connected systems used to provide ForgedBase.

This page is provided for product transparency. If you need a signed agreement or legal review copy, contact us before relying on this summary.

Subject matter and duration

This schedule covers processing performed to provide ForgedBase workspace, infrastructure, deployment, backup, provider, mail, domain, SSL, API, and support features.

Processing continues for as long as the workspace, account, connected resource, backup, support request, legal obligation, billing record, security record, or operational need remains active.

Data categories

ForgedBase may process account details, workspace membership, provider metadata, encrypted credentials, deployment records, activity logs, command output, backup metadata, billing metadata, and notification settings.

Depending on how you use the platform, customer content may include website files, application configuration, database contents, repository metadata, domain records, mail settings, logs, uploaded assets, and backup archives.

Processing purposes

Data is processed to authenticate users, operate workspaces, provision infrastructure, deploy sites, manage domains and SSL, run backups, send notifications, maintain security, and provide support.

Data may also be processed to enforce plan limits, record audit activity, troubleshoot failed jobs, display operational history, sync provider metadata, prevent abuse, and comply with legal or billing obligations.

Data subjects

Data subjects may include workspace owners, invited members, customer administrators, support contacts, billing contacts, end users represented in hosted applications, and people whose information appears in customer-controlled content.

Systems and recipients

Relevant systems may include ForgedBase application infrastructure, databases, queues, logs, email delivery, billing, storage, provider APIs, repositories, DNS providers, mail providers, and backup destinations.

Recipients may include authorized workspace users, ForgedBase support and operations personnel, selected third-party providers, payment processors, and legal or security recipients where required.

Retention and deletion

Operational records are retained for the period needed to provide the service, preserve security and audit history, support billing, troubleshoot incidents, and meet legal obligations.

Customer-controlled resources, provider-side infrastructure, external backups, repositories, DNS records, and mail domains may continue to exist with connected providers after they are detached from ForgedBase unless separately removed.