Privacy Policy

1. Operator & Scope

This Privacy Policy applies to the deterministic web intelligence compiler platform, developer APIs, documentation, and user dashboard provided through atlas-compiler.com, api.atlas-compiler.com, and dashboard.atlas-compiler.com (collectively, "Atlas", "the Service", "we", "us", or "our").

We believe in minimal data collection. Atlas is a developer infrastructure tool designed to compile publicly available web documents into structured Markdown and typed Intermediate Representations (IR). We collect only the information strictly required to authenticate authorized developers, enforce workspace tenant boundaries, meter universal compute credits, prevent network abuse, and fulfill statutory compliance obligations.

2. Information We Collect

To maintain system correctness and auditability, we categorize the data we process into distinct, transparent classifications:

A. Account & Authentication Data

When you create an account, log into the Atlas Dashboard, or join an organization workspace via our authentication provider (Clerk), we receive and store:

• User Identifier: An internal immutable ULID assigned to your user record and your corresponding external identity provider identifier (Clerk subject ID).
• Email Address: Your primary email address and email verification status.
• Display Name & Avatar: Your name and profile picture URL provided by your identity provider (e.g., Google or GitHub).
• Workspace Membership: The workspaces you belong to and your assigned role (owner, admin, developer, or viewer).

Note on Passwords: Atlas never sees, collects, or stores your raw plaintext password. Password hashing, credential validation, and multi-factor authentication (MFA) are managed directly by Clerk.

B. Workspace & Operational Metadata

• Workspace Configuration: Workspace name, URL slug, subscription plan tier, and assigned project IDs.
• API Key Metadata: Key name, key ID, public key prefix (e.g., at_live_...), creation timestamp, and assigned execution scopes. The plaintext API key secret is displayed exactly once upon generation and is never stored on our servers; only a cryptographically salted HMAC/SHA-256 hash is retained for authentication.
• Webhook Configuration: Destination URLs, subscribed event types (e.g., job.ready, job.failed), and signing secret ciphertexts.

C. API Requests, Target URLs, & Compiled Content

• Target URLs: Publicly accessible web URLs submitted by your application to our execution endpoints (/v1/compile, /v1/scrape, /v1/map, /v1/crawls, and /v1/batches).
• Compiled Artifacts & Cached Sources: The raw HTML fetched from target URLs, generated Markdown text, extracted link graphs, and typed AST nodes.
• Cache Lifecycle: Fetched web sources and compiled artifacts are stored temporarily in object storage (Cloudflare R2) and key-value cache (Cloudflare KV) with an automated time-to-live of seven (7) days (604,800 seconds). Following this expiration period, cached artifacts are purged automatically by scheduled garbage collection.

D. Billing & Financial Data

Payment processing and subscription lifecycle management are handled exclusively by Stripe, Inc. Atlas stores your Stripe Customer ID, Stripe Subscription ID, current plan code (free, starter, pro, team, scale, business, or enterprise), billing cycle (monthly or annual), and credit balances in our ledger.

Atlas never receives, processes, or stores raw payment card numbers, card expiration dates, or CVV security codes. All payment card entry takes place securely within Stripe's hosted Checkout and Customer Portal interfaces.

E. Infrastructure Telemetry & Network Logs

When clients communicate with our public edge network (Cloudflare), standard operational server logs are generated, including: client IP address, HTTP request method, request path, response status code, latency in milliseconds, user-agent string, and a unique request identifier (x-request-id). These logs are retained strictly for network edge rate-limiting, security monitoring, and distributed denial-of-service (DDoS) mitigation.

3. Purposes of Processing

We process personal and operational data exclusively for the following lawful purposes:

• Service Provisioning: Authenticating developers, executing compiler jobs, dispatching webhooks, and routing API calls.
• Universal Credit Accounting: Metering job execution costs, tracking active credit grants, and maintaining immutable financial records.
• Security & Abuse Prevention: Detecting unauthorized API key usage, preventing Server-Side Request Forgery (SSRF) against internal networks, and enforcing edge rate limits.
• Transactional Communications: Sending essential administrative emails, such as workspace invitation links and critical billing alerts, via our transactional delivery provider (Resend). We do not send marketing spam or sell your email address to advertisers.
• Statutory & Legal Compliance: Complying with applicable commercial, tax, accounting, and anti-fraud regulations.

4. Google API & OAuth User Data (Mandatory Disclosure)

When you authenticate with Atlas using Google Single Sign-On (OAuth), our authentication broker (Clerk) interacts with Google's identity infrastructure on our behalf.

A. Exact Google Scopes Requested

Atlas requests exclusively the following three (3) standard, non-sensitive identity scopes:

• openid — To verify your identity using OpenID Connect standards.
• https://www.googleapis.com/auth/userinfo.email — To view your primary Google account email address and its verification status.
• https://www.googleapis.com/auth/userinfo.profile — To view your basic profile information, including your full name and public avatar photo.

No Other Data Accessed: Atlas does not request, access, read, or store your Google contacts, Google Drive files, Gmail messages, calendar events, search history, device identifiers, or any other Google service data.

B. Purpose and Usage of Google Data

We receive your Google user ID (sub), verified email address, full name, and avatar URL. This information is used strictly to establish your session, provision your user account in our Cloudflare D1 database, display your identity in the Atlas Dashboard, and associate you with your developer workspaces.

C. Token Handling

Atlas never receives, stores, or handles Google OAuth access tokens or refresh tokens. Token exchange and session signing are performed directly by Clerk as our identity broker.

D. Explicit Prohibitions on Google User Data

In accordance with Google Limited Use specifications and our core architectural principles:

• Atlas does not sell Google user data to any third party under any circumstances.
• Atlas does not use Google user data for serving advertisements, retargeting, interest-based tracking, or promotional campaigns.
• Atlas does not provide Google user data to data brokers, information resellers, or list aggregators.
• Atlas does not use Google user data to train, fine-tune, or develop generalized artificial intelligence (AI) or machine learning (ML) models. Atlas is a deterministic, rule-based abstract syntax tree (AST) compiler.

E. Deletion of Google User Data

You may disconnect your Google account or delete your Atlas account at any time. When deleted, your email and name are erased from our database as detailed in Section 8.

5. Cookies & Telemetry

A. Marketing Website (atlas-compiler.com)

Our public marketing website uses zero third-party tracking cookies, zero marketing analytics scripts (such as Google Analytics, PostHog, or Meta Pixel), and zero behavioral profiling mechanisms. It is rendered as pure, static semantic HTML.

B. Developer Dashboard (dashboard.atlas-compiler.com)

The authenticated developer dashboard utilizes only strictly necessary functional cookies:

• Clerk Session Cookies (__session, __client_uat): Essential for cryptographic session authentication and keeping you securely logged in across navigation.
• Onboarding Secret Cookie (atlas_onboarding_secret): A transient, encrypted, SameSite=Lax, HttpOnly cookie with an automatic thirty-second (30s) time-to-live. It is used strictly to transport your generated default API key secret across the signup redirect to the welcome page and is purged immediately thereafter.
• CSRF Protection Tokens: Used to validate that state-changing API mutations originate from authorized dashboard sessions.

6. Third-Party Subprocessors & Data Sharing

We do not sell, rent, or trade your personal data. We share data only with verified infrastructure subprocessors strictly necessary to operate the Service:

We may also disclose personal data if required to do so by applicable law, lawful subpoena, or court order, or to protect the vital security and safety of our infrastructure and users.

7. We Do Not Sell Personal Information

Atlas has never sold, rented, leased, or disclosed customer personal information to third parties for monetary or other valuable consideration, and will not do so. Under the California Consumer Privacy Act (CCPA / CPRA), European General Data Protection Regulation (GDPR), and related frameworks, we affirm that we engage in no sale of personal data and no sharing of personal data for cross-context behavioral advertising.

8. Data Retention & Account Deletion Procedure

A. Retention Periods

• Account & Workspace Records: Retained for the active lifetime of your developer account.
• Compiled Web Artifacts (R2/KV): Automatically purged seven (7) days (604,800 seconds) after compilation.
• Financial & Credit Ledger: Transactional credit ledger entries and invoices are retained for up to seven (7) years to comply with statutory tax, corporate reporting, and anti-fraud legal mandates.

B. Account Deletion Execution

You may initiate account deletion directly through the Dashboard or by emailing privacy@atlas-compiler.com. Upon receipt of a verified deletion event (via Clerk user.deleted webhook or verified support ticket), our automated identity lifecycle service executes the following technical sequence in Cloudflare D1:

1. Your email address is permanently overwritten and set to NULL.
2. Your display_name is permanently overwritten and set to NULL.
3. Your external identity subject ID is replaced with an irreversible, one-way SHA-256 cryptographic hash tombstone (deleted:<hash>).
4. All API keys belonging to your owned workspaces are stamped with a revoked_at timestamp, preventing any further authentication.
5. All associated webhook endpoints are updated to disabled status.
6. All non-owner workspace memberships are permanently deleted.
7. An immutable audit log entry is recorded to verify that user deletion was carried out in compliance with applicable law.

9. Technical Security Safeguards

We implement architectural safeguards appropriate to the risk of processing developer data. Our verified technical security controls include:

• Encryption in Transit: All public traffic to atlas-compiler.com, the API, and Dashboard requires HTTPS encryption enforced by Cloudflare edge SSL certificates.
• Credential Protection: API key secrets are never stored in plaintext. We store only cryptographic hashes, ensuring compromised database snapshots cannot expose raw client keys.
• Outbound Network SSRF Filtering: The Atlas compiler egress worker (atlas-egress) actively inspects and blocks all outbound HTTP/HTTPS requests directed toward internal RFC 1918 private networks, RFC 4193 IPv6 unique local addresses, loopback addresses (127.0.0.1), link-local metadata endpoints (169.254.169.254), and internal worker bindings.
• Tenant Boundary Isolation: Workspace resources, API keys, and project scopes are strictly isolated by composite database keys and SQL triggers preventing unauthorized cross-workspace data access.

Security Disclaimer: While we implement robust safeguards to protect your data, no internet transmission or electronic database is completely impenetrable. We cannot warrant or guarantee absolute, error-free security.

10. Your Privacy Rights

Depending on your geographic location, you may have specific statutory rights under data protection laws such as the EU/UK General Data Protection Regulation (GDPR), the California Consumer Privacy Act as amended (CCPA / CPRA), and the Indian Digital Personal Data Protection Act (DPDP Act):

• Right of Access: You may request a copy of the personal information we maintain about you.
• Right to Rectification: You may correct inaccurate or incomplete account information via your profile settings or by contacting us.
• Right to Erasure (Deletion): You may request the permanent erasure of your personal data as described in Section 8.
• Right to Restriction & Objection: You may object to or request restrictions on certain processing activities where lawful grounds exist.
• Right to Data Portability: You may request export of your workspace project data in structured, machine-readable formats.
• Right to Non-Discrimination: We will never discriminate against you, deny you access, or alter your pricing for exercising your privacy rights.

To exercise any of these rights, please contact our privacy team at privacy@atlas-compiler.com. We verify requests by requiring confirmation from the authorized email associated with your Atlas account.

11. Children's Privacy

Atlas is a specialized developer infrastructure tool intended exclusively for professional software developers and organizations. The Service is not directed to individuals under eighteen (18) years of age, and we do not knowingly collect or solicit personal information from children under sixteen (16) (or under 13 where permitted by local law). If we learn that a minor has registered an account, we will immediately tombstone and delete that information.

12. International Transfers

Atlas infrastructure operates across globally distributed edge compute nodes managed by Cloudflare, with core database and authorization storage located in the United States. If you access the Service from the European Economic Area (EEA), United Kingdom, Switzerland, or other jurisdictions, your information will be transferred to and processed in the United States and other global locations under appropriate transfer mechanisms, including standard contractual clauses (SCCs) executed with our subprocessors.

13. Changes to this Privacy Policy

We may update this Privacy Policy periodically to reflect changes in our technical architecture, legal obligations, or service offerings. When material changes are made, we will update the "Last Updated" date at the top of this document and notify account owners via email or a prominent banner in the Atlas Dashboard prior to the changes taking effect.

14. Contact Information

If you have any questions, concerns, or privacy requests regarding this Privacy Policy or our data processing practices, please contact us:

• Privacy & Data Protection: privacy@atlas-compiler.com
• Security & Vulnerabilities: security@atlas-compiler.com
• General Support: support@atlas-compiler.com