Privacy policy.

AtlasOps stores the account, organization, infrastructure, billing, and audit data needed to operate deployment and monitoring workflows.

Data we process

The application data model is intentionally scoped to DevOps operations.

Account data: name, email, password hash, email verification state, timezone, role, and session metadata.
Organization data: workspaces, members, invitations, teams, roles, permissions, audit logs, and activity history.
Infrastructure data: projects, repositories, environments, servers, regions, operating systems, tags, health status, domains, and deployment logs.
Security data: API key hashes, SSH key fingerprints, webhook secret digests, environment variable records, and secret metadata.
Billing data: subscriptions, invoices, payment references, Razorpay webhook payloads, plan names, amounts, and hosted invoice URLs.
Support data: support tickets, knowledge-base interactions, roadmap requests, feature requests, and operational correspondence.

AtlasOps uses collected data only to provide and protect the product workflows.

Authenticate users, maintain remembered sessions, reset passwords, and verify email ownership.
Authorize access to organization, team, project, server, billing, and settings records.
Render dashboards, deployment history, monitoring charts, alerts, and activity timelines.
Send transactional emails such as verification, reset, billing, alert, and invitation messages.
Investigate abuse, debug incidents, verify webhook signatures, and maintain audit evidence.

Operational systems need durable history, but access should be minimized.

Soft-deleted users, organizations, projects, and servers remain marked with deletion timestamps for auditability.
API keys and reset tokens can be revoked or marked used without exposing the original secret value.
Billing records are retained as needed for accounting, tax, dispute, and refund review.
Customers can request export or deletion review for organization data that is not required for legal or security retention.

Data we process

The application data model is intentionally scoped to DevOps operations.

Account data: name, email, password hash, email verification state, timezone, role, and session metadata.
Organization data: workspaces, members, invitations, teams, roles, permissions, audit logs, and activity history.
Infrastructure data: projects, repositories, environments, servers, regions, operating systems, tags, health status, domains, and deployment logs.
Security data: API key hashes, SSH key fingerprints, webhook secret digests, environment variable records, and secret metadata.
Billing data: subscriptions, invoices, payment references, Razorpay webhook payloads, plan names, amounts, and hosted invoice URLs.
Support data: support tickets, knowledge-base interactions, roadmap requests, feature requests, and operational correspondence.

How data is used

AtlasOps uses collected data only to provide and protect the product workflows.

Authenticate users, maintain remembered sessions, reset passwords, and verify email ownership.
Authorize access to organization, team, project, server, billing, and settings records.
Render dashboards, deployment history, monitoring charts, alerts, and activity timelines.
Send transactional emails such as verification, reset, billing, alert, and invitation messages.
Investigate abuse, debug incidents, verify webhook signatures, and maintain audit evidence.

Retention and deletion

Operational systems need durable history, but access should be minimized.

Soft-deleted users, organizations, projects, and servers remain marked with deletion timestamps for auditability.
API keys and reset tokens can be revoked or marked used without exposing the original secret value.
Billing records are retained as needed for accounting, tax, dispute, and refund review.
Customers can request export or deletion review for organization data that is not required for legal or security retention.