Privacy Policy

About this policy

This policy covers the Atlas Cloud website, dashboard, deployment service, and Atlas MCP integration. “Atlas”, “we”, and “us” refer to the operator of Atlas Cloud. Contact our privacy team at hello@atlasos.one.

For account, billing, and service operations, Atlas determines how your information is used. When you host an application containing other people’s data, you determine its purpose and Atlas processes that application data to provide the services you request. You are responsible for your application’s own notices and permissions.

Information we process

• Account and workspace information: name, email address, account identifiers, authentication and verification records, workspace memberships, invitations, and connection permissions.
• Project content: uploaded application source and saved source snapshots, configuration, encrypted server credentials, database content, files and their names, paths, sizes, and other metadata.
• Operations and security: deployment and build records, application logs, errors, activity and administrative audit records, resource measurements, request timestamps, IP addresses, and connection information used to operate and protect the service.
• Billing and support: billing contact and address details you provide, usage and invoice records, payment status and transaction references, and messages you send us. Payment checkout is handled by a payment processor; Atlas does not request your full card details in its dashboard or AI tools.

How we use information

We use this information to create and verify accounts; authorize workspace access; deploy and run applications; operate databases and file storage; diagnose failures; measure usage and prepare invoices; process payments; answer support requests; prevent abuse; and meet applicable legal obligations.

Where a legal basis is required, processing depends on delivering the service you request, our legitimate interests in reliable and secure operations, legal obligations, or your consent where applicable. Atlas does not sell personal information or share it for cross-context behavioral advertising.

AI assistants and connected apps

Connecting an AI client lets it send tool requests to Atlas and receive results within the workspace and permissions you approve. Depending on the tools used, results can include project information, database query results, files, deployment status, logs, configuration metadata, and usage. Read access can therefore expose project content to that client. Deployment access also permits supported changes and can generate usage charges.

The Atlas integration does not require your entire AI conversation. Atlas receives the inputs your client sends to its tools and produces their results; operational records may retain parts of those requests. Your AI provider handles conversations and tool results under its own terms and privacy policy. Disconnecting Atlas stops future authorized calls but does not erase information already received by that provider. Do not send passwords, payment card data, government identifiers, or sensitive regulated data through the integration.

Who can receive information

Information is available to workspace members and connected apps according to their access, and to authorized Atlas operators for support, security, billing, and service operations. Administrative access is recorded.

We use service providers for application hosting, database and authentication infrastructure, object storage, email delivery, payment processing, and operational support. They process the information needed to perform those functions. Applications you deploy may be publicly reachable; your application’s authentication and sharing choices determine what its visitors can see.

We may disclose information when required by law, to protect people and the service, or as part of a business transfer subject to appropriate protections. We do not grant unrelated Atlas workspaces access to your project content.

Service-provider privacy notices

The following notices explain our current service providers’ own privacy practices. They do not replace Atlas’s responsibilities under this policy. Processing on our instructions is also governed by the applicable service agreements.

• Application hosting and delivery privacy notice ↗
• Database and authentication infrastructure privacy notice ↗
• Object storage privacy notice ↗
• Email delivery privacy notice ↗
• Payment processing privacy notice ↗

Your selected AI client has its own policy, available from that client before you connect it.

Processing locations and security

Atlas requests Singapore placement for application functions and new Postgres projects. Global delivery, object storage, backups, email, payments, and support can involve other locations. This is not an exclusive Singapore or India data-residency commitment. Applicable cross-border safeguards are required where law demands them.

Atlas uses authenticated access, workspace and project authorization, encrypted transport, server-side secret handling, and operational monitoring. No service can guarantee absolute security. Protect your account, review AI permissions, keep application credentials on the server, and avoid logging secrets. Report security concerns to hello@atlasos.one.

Retention and deletion

• Active project content: databases, files, and the current saved source snapshot remain while the project uses them. Deleting a file or project requests removal of the corresponding active resources. Project deletion can fail or require reconciliation; check the completed status.
• Source uploads: upload links expire at the time returned by Atlas, with signed upload URLs valid for at most 10 minutes. Expiry is not a deletion guarantee. Superseded or expired uploads are eligible for cleanup; the current saved source remains available for redeployment until replaced or the project is deleted.
• Logs: the runtime-log tool queries a recent 30-minute window; this describes tool availability, not a promise that every underlying log is erased after 30 minutes. Build, deployment, activity, and security records can remain after a project is deleted.
• Accounts and records: Atlas currently has no fixed automatic purge schedule for account, workspace, billing, audit, and deployment metadata. These records remain until a verified deletion request is handled or a retention requirement is resolved. Financial and security records may need to be retained after account closure for applicable accounting, dispute, fraud-prevention, or legal obligations. Backup copies can remain under the infrastructure provider’s retention cycle.

For account closure, a data export, or a retention question, email hello@atlasos.one. These requests are handled manually after identity and authority checks. We explain any information that must be retained; account closure is not an instant self-service purge.

Your choices and rights

You can manage workspace access, revoke AI connections, revoke Atlas API keys, and delete authorized project resources from the dashboard. Export or back up application data before deleting it. Signing out or revoking a connection does not delete a project or stop its usage.

Depending on applicable law, you may request access, correction, deletion, portability, restriction, objection, or withdrawal of consent, and complain to your local data-protection authority. Contact hello@atlasos.one from your account email. We may verify your identity and workspace authority, and respond within applicable legal time limits. Withdrawing consent does not affect earlier lawful processing.

Cookies, children, and changes

Authentication uses cookies and similar session mechanisms. Browser storage remembers preferences such as theme and your selected workspace. Clearing it can sign you out or reset preferences. The Atlas application does not include advertising trackers; external AI clients and payment pages have their own browser-storage practices.

Atlas accounts are intended for adults who can enter a service agreement, not children. Contact us if you believe a child supplied account information.

We update this page when our practices change. The date above identifies this version. Material changes will be communicated through the service or your account contact where required.