Skip to main content

Data handling: storage, retention and deletion

Your data is stored under your account and read only with your own keys. On the shared service, telemetry stays in the live store for 30 days. Deleting your account revokes every key at once, so nothing you stored can be read again, and what is left ages out on the schedule below.

What is stored, and for how long​

DataWhat it isHow long it is kept
Telemetry and topology stateRecords you write to POST /telemetry, directly or through the fleet agent, and the state GET /topology reads backOn the shared service, 30 days in the live store and 35 days in daily backups. A monthly export goes to a long-term archive, kept until you ask support to purge it.
Network configEvery version you upload. Each records created_by, the key that wrote it. See Topology config.Every version, with no expiry
Workflow runsEach run's results, and the workflow results your connectors pullRun results 30 days, workflow results for connectors 7 days. After that the run answers 410 run_data_expired.
FilesPass logs and raw files you upload over HTTPS or SFTP. Each upload is stored as a new file, and you cannot delete or rename one yourself. See Telemetry files.Kept in your account's folder
API keysA hash of each secret, never the secret itself, which is why a secret is shown only onceUntil you revoke the key or it expires
Usage and billing recordsCounts of predictions and telemetry points, and billing entriesKept for billing records

How your data is used, and what changes only if you opt in, is in How your data is used.

How it is separated from other accounts​

Every read and write takes its account, and its workspace, from the API key or sign-in that made it, never from the request body. A key reaches only its own account's data, and a key made in one workspace reaches only that workspace.

PlanWhere your data lives
Explore, Operator, Operator + Act, NetworkThe shared service. Data is kept apart by account in shared storage.
EnterpriseA dedicated deployment of its own, with its own API host, Platform site and sign-in

Sign-in and scopes decide what a caller may do; they do not make a separate storage boundary. Only Enterprise has one. See Tenant isolation.

Calls to the API use HTTPS, and gRPC ingest uses TLS on port 443.

Delete your account​

Settings, Delete account, then type your email to confirm. It needs a sign-in from the last 10 minutes, and an account on a paid plan must cancel the plan first (409 billing_active).

WhenWhat happens
At onceEvery API key is revoked. Workspaces, destinations and their stored credentials are deleted. Linked sign-ins are removed and become separate, empty sign-ins. Your plan ends and your sign-in is deleted.
Within 30 daysTelemetry, topology and forecasts, already unreadable, leave the live store.
Within 35 daysThey leave the daily backups.
On requestSupport purges the long-term archive. Write to contact@constellation.space.

What else you stored, such as network config versions, saved workflows and uploaded files, cannot be read once your keys and sign-in are gone. To have it removed too, write to support. Usage and billing records are kept for billing.

Deleting a linked sign-in deletes only that sign-in; the account it opened keeps its keys and data. An Enterprise deployment is one shared account, so its Platform offers no deletion: ask your Constellation contact.

What Constellation staff can see​

To support your account, Constellation staff can look up its plan, usage, the list of its keys (never their secrets), its destinations, and how many files you uploaded and their size. Every change staff make to an account is recorded with the reason for it. See The audit log.