Privacy policy
This policy explains what devopsellence collects, why, how we use it, and the choices you have.
What we collect
We collect the information needed to run the service you ask us to run.
- Account data such as your email address, account kind, and login state.
- Identity-provider data from GitHub or Google, including provider identifiers, verified email, and basic profile metadata.
- Workspace data such as organizations, projects, environments, releases, deployments, node names, labels, and runtime configuration.
- Infrastructure metadata such as desired-state locations, public IPs, provider server identifiers, region and size selections, and environment secret names.
- Secrets that you submit so we can provision runtime access.
- Authentication and security data such as session state, API token digests, refresh token digests, bootstrap token digests, and audit timestamps.
- Technical data such as IP address, user agent, request logs, and operational telemetry.
How we use information
- To authenticate you and keep your account secure.
- To create organizations, environments, releases, nodes, and optional preview capacity.
- To store, publish, sign, and deliver desired state to nodes.
- To provision and control runtime resources.
- To investigate incidents, prevent abuse, enforce limits, and improve reliability.
- To communicate with you about the service.
How information is shared
We do not sell personal information.
- With infrastructure providers we use to run the service, including Google Cloud and configured managed-node providers.
- With identity providers you choose for login, such as GitHub or Google.
- With DNS and infrastructure providers we use to publish managed ingress records.
- With service providers that help us operate the product, only as needed.
- When required by law or to protect safety and security.
Secrets and runtime data
devopsellence handles operationally sensitive deployment data. We use it to run your workloads, not to inspect application content for unrelated purposes.
- Environment secrets are used to provision runtime access.
- Release and deployment metadata are used to build, publish, and reconcile desired state on nodes.
- You are responsible for the content of the applications, images, data, and secrets you deploy.
Retention
- We keep records for as long as your account or workspace remains active, and longer if needed for security, disputes, or compliance.
- Short-lived authentication artifacts expire automatically.
- We may retain logs, backups, and security records for a limited period after deletion.
Your choices
- You can update configuration, rotate secrets, revoke tokens, and delete environments.
- You can stop using the service at any time.
- For account or workspace deletion, contact us.
Security
We use administrative, technical, and organizational measures to protect information. No system is perfectly secure.
Children
devopsellence is not directed to children under 13.
Changes
We may update this policy as the service evolves. Updated versions will be posted here with a new effective date.
Contact
Questions: contact@devopsellence.com