Skip to main content

How your data is used, and who can see it

Your telemetry, pass logs, network config and results belong to your account. Every API call is scoped to the account its key belongs to, and Constellation uses your data to compute your forecasts, runs and reports. No setting shares it beyond your account today.

Who can see it​

  • Your account. Each API key resolves to one account, or to one Enterprise tenant, and reads and writes only that account's data. A workspace is an account of its own, with its own keys.
  • People signed in to it. A shared view or report link opens only for people signed in to the same account. Team members and roles are not available yet. See Roles and SSO.
  • Your mission control system (MCS) and destinations. Results go where your workflows send them: a connector you install pulls them into your MCS, and a destination you set up receives them.

Where it is kept​

What is stored, for how long, how it is kept apart from other accounts on each plan, and what deleting your account removes are in Data handling. To agree a retention period, write to contact@constellation.space.

How Constellation uses it​

  • To answer you. Models read your network config and your links' recent telemetry to price your passes. Where a model calibrates on your own telemetry, its card says so; see Models and their tiers.
  • Kept apart by kind. Pass logs go into the audit dataset, so an audit never mixes with your live telemetry. See Data modes.
  • Not shared. No data-sharing opt-in exists yet: there is no setting that shares your data with other accounts or adds it to models other accounts use. Constellation's open datasets, such as the demo fleet on Hugging Face, are Constellation's own data, not customers'.

Report a concern​

Send security questions or reports to contact@constellation.space. Include the environment, the time, and the request or incident ID, but no credentials or telemetry.