Privacy Policy

Effective date: July 18, 2026 · Last updated: July 18, 2026

This Privacy Policy explains how The Atlas Project ("we," "us," "our") handles personal information in connection with SnapLedger at snapledger.the-atlas-project.net (the "Service"). It applies to the Service and our marketing site. It does not cover Third-Party Services you separately connect, which have their own policies.

The short version. SnapLedger structures receipt data. We use essential cookies only, run no analytics or advertising trackers, do not sell or share personal information for advertising, and handle privacy requests by email. Receipt images may contain personal data; we process them only to produce your structured expense lines, we disclose the AI subprocessors that read them, and we delete them on request and on a storage-lifecycle schedule.


§1 Who we are; scope; roles

This Policy covers personal information we handle for SnapLedger.

Controller / processor roles.

  • For your account and billing data, we act as controller.
  • For the personal data contained in the receipt images, PDFs, and text you submit (e.g., names, partial card digits, locations, timestamps that appear on a receipt), you are the controller and we are your processor, processing that content only to produce your structured lines and history. The mini-DPA (Schedule A of the Terms) governs that relationship.

§2 Categories of personal information we collect

CategoryExamplesSource
Account dataname, email, password/OAuth identity, workspace settingsyou, at signup (via Supabase auth)
Billing dataplan, billing email, partial card metadata, transaction historyyou and Stripe (we do not store full card numbers)
Usage & device datalog events, feature and parse usage, IP address, timestamps, error logsautomatically, to run and secure the Service
Support datamessages you send us (including inbound support email)you
Essential cookiesSupabase auth-session cookie; a signed anonymous-scan cookie for logged-out useyour browser session
Receipt content you submitreceipt images, PDFs, or pasted receipt text, and the structured lines, history, tallies, categorization rules, and CSV exports generated from them — any of which may contain personal datayou (web scan or the Raycast extension)

We do not use analytics or advertising cookies or pixels, and we do not build advertising profiles. If this ever changes, we will update this Policy and, where required, obtain consent first.

§3 How and why we use personal information (purposes)

  • Provide the Service — authenticate you; structure receipts into fields via a vision/extraction model; accumulate your history and running tally; generate CSV exports for entitled accounts.
  • Billing — process subscriptions and manage plans, trials, and cancellations, via Stripe.
  • Communicate — send transactional and service messages (receipts, security notices, lifecycle and product notices, and — for Pro/Team — the optional weekly digest) via Resend. Any marketing email is sent only where permitted and includes an unsubscribe option.
  • Secure and maintain — enforce parse quotas and entitlement gates, detect and limit abuse, debug, and protect the Service and its users.
  • Comply — meet legal obligations and enforce our Terms.
  • Improve — understand feature usage in aggregate. We do not use the receipt content you submit to train generalized AI models, and the vision/extraction subprocessors (OpenAI or Anthropic) do not train their general models on your content per their API/enterprise terms.

§4 Legal bases (GDPR / UK GDPR)

Where GDPR/UK GDPR applies, we rely on: performance of a contract (to provide the Service you signed up for); legitimate interests (to secure, maintain, and improve the Service, and for limited service communications), balanced against your rights; consent (where required, e.g., any future non-essential cookies or optional marketing); and legal obligation (e.g., tax/records). For the receipt content we process on your behalf, your instructions and the mini-DPA govern, and you are responsible for the legal basis as controller.

§5 Subprocessors and third-party recipients

We use the following subprocessors and service providers for SnapLedger:

SubprocessorFunctionPersonal data involved
VercelApplication hosting / edge deliveryall traffic and stored request data in transit
SupabaseDatabase, authentication, and file storage (receipt images, exports)account, receipt content, history, exports
StripePayment processing; subscription billing and customer portalbilling data (Stripe handles card data)
ResendTransactional, lifecycle, and inbound support emailyour email address and message content
OpenAI or AnthropicVision/extraction model that structures receipts — one provider is configured at a timethe receipt image, PDF, or text you submit
Foreign-exchange rate provider (exchangerate.host or Open Exchange Rates)Daily currency rates for multi-currency structuringnone — currency codes only, no personal data sent
Sentry (optional, if enabled)Error trackingerror logs, which may include IP address and technical metadata

When a vision provider key is configured, the receipt content you submit is sent to that provider (OpenAI or Anthropic) to produce the structured line; when no key is configured, the Service returns structured lines from a bundled sample set and no receipt content leaves our infrastructure for extraction. We enter data-processing terms with subprocessors where required and require appropriate safeguards. We will update this list and, where required, give notice before adding a subprocessor that materially changes processing of your data.

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

§6 Cookies and similar technologies

We use essential cookies only — the Supabase authentication-session cookie that keeps you signed in, and a signed cookie that tracks anonymous scans and their tally for logged-out use. We do not use analytics, advertising, or tracking cookies or pixels. Because we use only strictly-necessary cookies, we do not show a non-essential-cookie consent banner. If we ever introduce non-essential cookies, we will update this Policy and obtain consent where required.

§7 Retention

  • Account and billing data — kept while your Account is active and as needed for legitimate business and legal purposes (e.g., tax records) after closure.
  • Receipt content and structured history — retained per your plan and settings so your history and tally persist, and deleted or de-identified on request or on termination, subject to residual backups purged on our ordinary cycle and records we must keep by law.
  • Receipt source images stored in file storage are subject to a storage-lifecycle deletion and are removed after 90 days.
  • Anonymous scans (logged-out use) are deleted after 30 days.
  • CSV exports stored in file storage expire and are removed on our ordinary cycle.

You may request earlier deletion at any time (see §9).

§8 Security

We use reasonable technical and organizational measures appropriate to the risk, including encryption in transit, access controls, least-privilege, per-account parse quotas and entitlement gates enforced server-side, and reliance on reputable infrastructure providers (Vercel, Supabase, Stripe). No system is perfectly secure; we cannot guarantee absolute security. We will notify affected users and regulators of a personal-data breach where required by law.

§9 Your privacy rights

§9.1 GDPR / UK GDPR (EEA/UK residents). Subject to conditions, you may request access, rectification, erasure, restriction, portability, and objection, and may withdraw consent where processing is based on consent. You may lodge a complaint with your supervisory authority. Where we act as processor for receipt content, we will route or assist requests to the relevant controller (our customer).

§9.2 CCPA / CPRA (California residents). You have rights to know/access, delete, correct, and to opt out of "sale" or "sharing." We do not sell or share personal information as those terms are defined, and we do not use sensitive personal information for purposes that would require a right-to-limit. We will not discriminate against you for exercising rights. Authorized agents may submit requests with proof of authorization.

§9.3 Receipt content held on your behalf. Some receipt content is personal data of individuals other than you (e.g., a name printed on a receipt). Where we hold such data as your processor, rights requests are typically directed to you as controller, and we assist as processor.

§9.4 How to exercise rights. Email admin@the-atlas-project.net (or admin@the-atlas-project.net) from your Account address, describing your request. We will verify your identity and respond within the time required by law. For content held on behalf of a customer (processor role), we direct end users to the customer/controller.

§10 International data transfers

We are based in the United States, and our subprocessors may process data in the US and elsewhere. Where we transfer personal data out of the EEA/UK, we rely on appropriate safeguards such as the EU Standard Contractual Clauses and the UK Addendum, or another lawful mechanism. By using the Service, you understand your information may be processed in the US.

§11 Children

The Service is not directed to individuals under 18, and we do not knowingly collect their personal information (see Terms §16).

§12 Changes to this Policy

We may update this Policy. We will post the new version with a revised "Last updated" date and, for material changes, provide additional notice (email or in-product). Continued use after the effective date constitutes acceptance where permitted by law.

§13 Contact

Questions or requests: admin@the-atlas-project.net (privacy) or admin@the-atlas-project.net. Postal address: The Atlas Project, mailing address to be added once the operating entity is formed.

Last updated: July 18, 2026 · The Atlas Project · admin@the-atlas-project.net

This document was prepared with automated assistance and has not been reviewed by an attorney. It is not legal advice.