Skip to main content

Data

What ComputeSphere stores about your account and services, how long it's retained, where it lives, and how to remove it.

What we store​

CategoryExamplesRetained
Account metadataAccount name, owner, member list, billing detailsLifetime of the account
Project + service configService settings, env vars, custom domains, secretsLifetime of the resource
DeploymentsBuild images, deployment records, build logsRecent deployments kept for rollback
Runtime logsStdout/stderr from your running spherelets90 days
MetricsCPU, memory, request rate, error rate per spherelet90 days
Audit eventsAccount state changes, deployments, member changes90 days (extended for Team+)
Invoices and billingInvoices, payment history, subscription records7 years (financial-records requirement)

Customer data ingested into your service (database rows, file uploads, customer payloads, etc.) is your data. ComputeSphere doesn't read or process it.

Where data lives​

  • Compute, networking, observability — hosted on enterprise cloud infrastructure in the ComputeSphere regions
  • Container images — the ComputeSphere registry, in our available regions
  • Billing data — a PCI-certified payment processor (subject to the processor's own data-handling policies)
  • Email — a transactional email provider

All runtime data (logs, metrics, image, env vars) for your services lives in our available regions — see the Residency section below.

Deletion​

Delete a service​

Deleting a service in the console:

  • Removes the service config, env vars, and custom domain bindings immediately
  • Drains and terminates running spherelets within minutes
  • Pruning of deployment images and logs follows the retention windows above

Delete an account​

Account deletion is a self-serve flow in Settings → Account → Delete account. The flow includes:

  1. A confirmation step that lists every resource that will be removed
  2. A 90-day soft-delete grace period during which the account can be restored by contacting support
  3. After 90 days, permanent deletion: configuration, deployments, images, logs, metrics — all removed

Billing records are retained per the 7-year financial-records requirement regardless of account state.

Data export​

  • Account / service metadata — exportable via the REST API at any time
  • Logs and metrics — exportable via API and via the observability surfaces
  • Bulk export of all account data — available on request to support; useful for end-of-tenant migrations or compliance evidence

Residency​

ComputeSphere services run in the regions below. Customer payloads, logs, metrics, and images are stored in our available regions, listed below.

us-east-1
US East (Virginia)
eu-north-1
EU (Sweden)

For workloads with specific residency requirements — sovereign-cloud arrangements, or industry-specific data-handling rules (HIPAA, FedRAMP, etc.) — see Compliance and contact us about Enterprise tier provisioning.

Sub-processors​

ComputeSphere uses sub-processors for hosting, payment processing, email delivery, and customer support. The current list is published on the security & trust page and updated when sub-processors change.