Privacy Policy

Atlas by Equipoise · Last updated 12 October 2026 · Contact: luke@equipoise.earth

Who we are

The Platform is operated by Equipoise Earth Ltd, registered in England and Wales (company number 14300979), registered office: 1 Station Court, Station Approach, Wickford SS11 7AT. Equipoise Earth Ltd is the data controller for personal data processed on the Platform, and is registered with the Information Commissioner’s Office under reference ZB374255. We may update this policy from time to time; the date above always reflects the current version.

What we hold

  • Account details — your name, work email, organisation and role, and whether you agreed to receive marketing from Equipoise. If a programme organiser invited you, we received your email address and company name from them.
  • Your organisation’s work on the Platform — emissions reports, targets, progress through modules, courses and live events, expert sessions booked or held, and documents you upload to your Second Brain. Atlas conversations and generated business cases are not stored by us: each request is sent to Anthropic to produce the answer, and we keep only a count of AI use.
  • Community contributions — posts, replies, pictures and likes, shown with your name and organisation. Some channels include posts imported from the earlier Equipoise support forum on Mighty Networks.
  • Billing details — if your organisation subscribes, Stripe handles payment. We hold the subscription status and Stripe customer reference; we never see or store card numbers.
  • Usage and security records — counts of AI use (to apply usage limits), changes made by administrators, and blocked or rate-limited requests. Our hosting and sign-in providers process your IP address and browser details to deliver and secure the service.
  • Usage analytics — pages visited, referring site, country, and browser and device type, collected without cookies by Vercel Web Analytics and Speed Insights to measure traffic and performance. We do not use it to identify you.
  • Website visitors — if you register interest, the email address and company name you give us. The free Atlas demo on our public page uses an anonymous identifier cookie and a scrambled (hashed) form of your IP address to limit how many questions can be asked.

Why we use it

To provide the Platform under our agreement with your organisation (account access, your journey, Atlas, the Community, expert sessions and billing); to send service emails — sign-in codes (sent by Clerk), invitations and data-sharing requests (sent by Resend), and billing receipts (sent by Stripe); and, in our legitimate interests, to keep the service secure, apply programme and usage limits, measure performance, and support you. If you ticked the box when you joined, we send you marketing emails from Equipoise with your consent; you can withdraw it at any time by emailing luke@equipoise.earth or using the unsubscribe link in any marketing email. We do not sell personal data or use it for advertising.

How Atlas, the AI assistant, uses your data

Atlas is powered by Anthropic’s Claude models under Anthropic’s commercial API terms: your data is not used to train Anthropic’s models. Atlas draws on three sources: your organisation’s own Second Brain, which grounds answers for your organisation only and is never mixed into any other organisation’s context (a separation enforced at the database level and covered by automated tests); reference material provided for your programme; and Equipoise’s own guidance library. Document search is powered by Voyage AI, which converts the text of uploaded documents, and your questions, in short sections into numerical representations under equivalent no-training API terms. Atlas gives advice only: it is never used to assess or grade people, and no decision with legal or similar effect is made about you by automated means.

Who can see what

  • Your colleagues. Anyone who signs up with a verified email address at your organisation’s domain joins your organisation and can see its work. Your Org Lead manages members and roles.
  • Your programme organiser. If your organisation joined through a programme run by a customer or partner, the organiser sees, at organisation level, your participation and progress — which modules are complete, attendance at programme live events, whether an expert session was booked or held, and when your organisation was last active — and can download it. The organiser never sees individual names, course results, Community activity or the content of your work. Your emissions report and reduction target are shared with the organiser only if your Org Lead switches on sharing; both settings are off until then, and your Org Lead can accept, decline or later revoke individual requests. Your documents and Atlas conversations are never shared.
  • Other Community members see what you post in a channel they can access, with your name and organisation. Programme channels are visible only to organisations taking part in that programme.
  • Experts. If you book an expert session, you do so on the expert’s own booking page, under that service’s terms, and the expert receives the details you enter there. We record that you clicked to book, and whether the session was held.
  • Equipoise staff can access account and organisation data where needed to run, support and secure the Platform. Administrator access requires multi-factor authentication, and changes made by administrators are logged.

Where your data lives

Hosting and storage run in EU regions: our database (Neon, Frankfurt), file storage (Vercel Blob) and application hosting (Vercel, Frankfurt, with pages delivered over Vercel’s global network). Data is encrypted in transit and at rest. Authentication is provided by Clerk, transactional email by Resend and payments by Stripe. Errors are monitored with Sentry using internal identifiers only — never names, emails or document content. Backup copies of files we publish on the Platform (course files, Community pictures, expert photos, and programme and reference materials, but never your organisation’s uploaded documents) are kept in GitHub for up to 90 days so we can restore them after an incident. The full list of third parties that process data on our behalf, with regions and certifications, is published on our sub-processors page. Where a sub-processor processes personal data outside the UK or European Economic Area, the transfer is safeguarded by Standard Contractual Clauses approved by the European Commission or an equivalent mechanism under Chapter V of the UK and EU GDPR.

How long we keep it

We keep personal data while your account and organisation are active. When an organisation is deleted we erase its data from the Platform, and backup copies expire on a rolling basis within 90 days; Stripe keeps the payment and invoice records it is required to keep by law. Register-interest details are kept until you ask us to delete them.

Your rights

You have the right to access, correct, delete, restrict or object to the use of your personal data, and to receive it in a portable format. Your Org Lead can export everything we hold about your organisation as a machine-readable file (Settings → Data & privacy → Export our data; uploaded documents are listed, and the files themselves can be downloaded from your Second Brain) and can request deletion of the organisation and all its data from the same place — we confirm and then erase it, deleting the customer record at Stripe and the sign-in accounts at Clerk. Community posts by a deleted account remain visible without the author’s name; pictures are removed when the organisation is deleted. For anything else, email luke@equipoise.earth. You may also complain to the Information Commissioner’s Office (ico.org.uk) or your local supervisory authority.

Cookies

We use strictly necessary cookies only: sign-in (Clerk), an invitation cookie that remembers which programme invited you, an anonymous identifier that rate-limits the free Atlas demo on our public page, and a one-minute cookie that carries a sign-up error message. Our analytics work without cookies. No advertising or cross-site tracking. See our cookie policy for details.