Policies & Agreements
Where to find the Atlas Cloud terms, acceptable use policy, data policies, service level agreement, and services agreement.
The authoritative version of every legal document lives on the main site. This page is a map — read the linked documents for the binding text.
Documents
| Document | Covers |
|---|---|
| Privacy & Terms | Terms of service, purchases and subscriptions, prohibited activities, ownership of your content and outputs, governing law |
| Acceptable Use Policy | What you may and may not build, API reseller obligations, prepaid credit terms, export controls |
| Data Retention | How long content is kept, Enterprise Zero Data Retention, and the commitment not to train on your content |
| Data Deletion & Account Closure | Deletion requests, account closure, what must be retained for legal and accounting reasons |
| Service Level Agreement | Availability commitments and service credits under a signed Order |
| Services Agreement | The master commercial agreement: payment terms, term and termination, liability, dispute resolution |
Summaries of the two data policies are also maintained in these docs: Data Retention and Data Deletion.
Points worth knowing
These come up often enough to call out. They are summaries — the linked documents govern.
Your content and outputs are yours
Atlas Cloud does not claim ownership of what you submit or what the models generate for you.
Your content is not used for training
Content submitted through Atlas Cloud is not used to train, fine-tune, evaluate, or benchmark hosted models unless you authorize it in writing.
Prepaid credits expire, and purchases are final
Prepaid credits are valid for a defined period from purchase. Purchases are final and credits are not refundable, transferable, or redeemable for cash. Remaining credits may be forfeited on account closure. See the Acceptable Use Policy.
You must add value on top of the API
Exposing the Atlas Cloud API directly to your own end users, or reselling it as a thin wrapper without substantive added functionality, is not permitted.
Benchmark results need written consent
Publishing benchmark results, performance metrics, latency or throughput figures, or comparative evaluations requires prior written consent. Internal testing is fine; publishing the numbers is not automatic.
No specific certifications are claimed
Atlas Cloud does not represent that it holds SOC 1, SOC 2, ISO 27001, or any other specific certification, and the platform is not tailored to meet HIPAA or FISMA requirements. If your workload is subject to those regimes, talk to us before building on it.
The Service Level Agreement applies to instance-based services purchased under a signed Order, and its availability and service-credit terms are written in those terms. It is not an uptime commitment for pay-as-you-go API usage. If you need a contractual availability guarantee for API workloads, contact sales.
Enterprise documents
Enterprise customers can request a Data Processing Agreement, a Zero Data Retention addendum, a subprocessor list, and a security overview. Contact [email protected].
Contacts
| Topic | Address |
|---|---|
| Privacy and data requests | [email protected] |
| Enterprise and contracts | [email protected] |
| General support | [email protected] |
Last updated on