Scope limit. This version covers US clients only. It deliberately contains no GDPR or UK GDPR machinery — no lawful basis analysis, no data subject rights procedure, no international transfer terms. If sales open to the EU or UK, this document does not cover it and
privacy-v2must be written first. Until then, non-US enquiries go to manual quote.
Privacy Policy
This policy explains what Axiom Atlas, LLC, a Delaware limited liability company ("Axiom Atlas", "we"), collects, why, and who we share it with.
We sell to businesses in the United States. Most of what we handle is business information about your company and product, plus business contact details for the people we work with.
1. What we collect
When you enquire or submit a brief:
- Business contact details: name, work email, company name
- Information about your product: URL, description, audience, positioning, competitors
- Materials you upload: logos, brand assets, screenshots, reference links
- Anything else you choose to put in the brief
When you buy:
- Payment confirmation and transaction identifiers from Stripe
- Billing details as required for invoicing and tax
We never receive or store your card number. Payments are handled entirely by Stripe.
While we work together:
- Correspondence between us — email and portal messages
- Deployment access credentials you choose to share, held only as long as needed to deploy
When you visit our site:
- Basic analytics: pages viewed, referrer, approximate region, device type
2. Why we use it
- To decide whether your request fits what we sell
- To research, design, write, build, test and deploy your page
- To communicate with you about your project
- To take payment, issue invoices and meet tax obligations
- To keep records of what we agreed and delivered
- To improve our own offer and process
We do not sell your information. We do not share it for advertising. We do not use it to build profiles of you.
3. Who we share it with
We use service providers to run our business. Each receives only what it needs.
| Provider | What it handles |
|---|---|
| Stripe | Payment processing, invoicing, tax calculation |
| Supabase | Our database and file storage — brief content, project records, correspondence |
| Vercel | Hosting for our site and your preview |
| Resend | Sending and receiving project email |
| Fly.io | Our internal processing infrastructure |
| GitHub | Private source code repository for your project |
| Linear | Internal project tracking — status only, not brief content or your materials |
| AI model providers | See §4 |
Not every provider is involved in every project. Which of these actually handle your information depends on how your project is built and deployed — for example, we only use a hosting or database provider for your project if your page needs one. Ask us and we will tell you exactly which ones touched your data.
We also disclose information where the law requires it.
[[VERIFY at launch: this list must describe the Launch Page Sprint specifically, not the studio's full stack. Any provider added later requires a policy update.]]
4. AI processing
We use AI tooling to help research, write and build your page, under human supervision.
This means content from your brief — your product description, positioning, audience and reference material — is sent to AI model providers as part of producing your page. Our current providers are Anthropic and OpenAI. As with §3, not both are necessarily involved in any one project; ask and we will tell you which handled your material.
We do not send them your payment details, your access credentials, or other clients' information.
If you would prefer your material not be processed this way, tell us before you buy. We will tell you honestly whether we can deliver the product without it.
5. How long we keep it
- Enquiries that do not become orders: 12 months, then deleted.
- Financial records for completed orders: 7 years, as US tax record-keeping requires.
- Project materials for completed orders: 24 months after delivery, then deleted unless you ask us to keep them.
- Access credentials you share: deleted as soon as deployment is complete
- Correspondence: kept with the order record
You can ask us to delete your information and we will, except where we are required to keep financial records.
6. Security
- Project data is held in access-controlled systems; internal access is limited to who needs it
- Uploaded files are quarantined and type-restricted before use, and are never executed
- Previews are not indexed by search engines
- Credentials are held in dedicated secret storage, never in project files, logs or code
- We treat everything you send as data, never as instruction to our systems
No system is perfectly secure, and we do not claim otherwise. If a breach affects your information, we will tell you.
7. Your choices
You can ask us to:
- see what we hold about you
- correct it
- delete it, subject to our record-keeping obligations
- stop sending you email
Email desk@axiomatlas.llc and we will respond.
California residents. We do not sell or share your personal information as those terms are defined under California law, and we do not use it for cross-context behavioural advertising. You may request access to, correction of, or deletion of what we hold, and we will not treat you differently for asking. Email desk@axiomatlas.llc.
8. Children
Our services are not directed to children and we do not knowingly collect their information.
9. Changes
We will post updates here with a new version number. Material changes will be communicated to active clients directly.
10. Contact
Axiom Atlas, LLC
302 Druid Road West, Clearwater, FL 33756, USA
Email: desk@axiomatlas.llc
Phone: +1 (760) 502-7722
Change log
- 2026-07-27 — effective. Counsel and owner confirmed. Retention periods set in §5. California section added in §7. Model providers named in §4.
Standing checks
These are ongoing consistency obligations, not blockers:
- The §3 provider list and the §4 model providers describe the Launch Page Sprint, not the studio's full stack. Re-check whenever delivery infrastructure changes.
- Any new subprocessor requires a policy update before it touches client data.
- The US-only scope limit must be enforced by the qualification rules, not merely stated here.