Legal

This page describes the legal position, not the law. It is written for the person who has to complete your data protection review. Your contract with Atlantic governs; where this page and your contract differ, the contract wins.

What Atlantic holds

Your content is not stored by Atlantic. When your people, or Atlantic staff you have authorised, view content in LightHouse, it is read from your account, passes through LightHouse to the person viewing it, and is not kept.

The personal data LightHouse does hold is limited to the names and email addresses of the people who sign in (and any profile picture they add), the keyed hashes your deployment computes for people, and your billing contacts. Atlantic processes it under the data processing agreement below, which sets out each party’s role.

The data processing agreement

• When you sign up yourself, you accept the master services agreement and the data processing agreement in LightHouse. The acceptance is recorded with the agreement’s version, the time, the verified email of the person who accepted, and a keyed hash of where the request came from. Acceptance records are append-only: neither party can quietly restate them.
• When you sign through Atlantic’s sales team, the agreements are part of your order, and your commercial terms are recorded on your tenant.
• A new version is shown in LightHouse (Spend → Terms) until your administrator accepts it. Nothing is slipped in.
• Content export needs a signed data processing agreement before it can be turned on.

The DPA’s text, published on the company site per version: Coming. Until then, ask us for it, or read it in the sign-up flow.

The company site’s privacy notice covers the data Atlantic handles as a controller (enquiries, site forms).

Sub-processors

The companies that process personal data on Atlantic’s behalf, what for, and where, are listed on Sub-processors.

Two points shape that list:

• Direct or Managed. If your models, cloud and identity provider are your own (Direct), those providers act under your contracts with them and are not Atlantic’s sub-processors. They become Atlantic’s sub-processors only where Atlantic provides the service: managed model access, Octy where Atlantic serves it, and Atlantic-hosted.
• Open-weight models (Llama, Granite, Qwen, DeepSeek and others) run on one of the clouds listed or in your own account. Their makers receive nothing, and are listed only so you know a model’s origin.

Changes. Atlantic gives notice before a new sub-processor starts processing your data: 30 days by default, by email to your billing contact. The notice period is a commercial term you can see under Spend → Terms. You may object within that period; if the objection cannot be resolved, you can stop using that provider or end the affected service.

A notice of sub-processor changes inside LightHouse: Coming

Transfer mechanisms

LightHouse’s data is stored in the EU (Ireland). Where a sub-processor processes outside the EU, the transfer relies on the European Commission’s standard contractual clauses or the EU–US Data Privacy Framework, as listed per sub-processor. Each sub-processor’s own data processing terms cover Atlantic’s onward obligations under Article 28(4) GDPR.

Your content is stored in your account, in the region you chose. A prompt goes where the model path you configured sends it: under your own contract in Direct mode, or to the provider listed as Atlantic’s sub-processor under managed model access. Each path’s inference geography is disclosed on Regions.

How to describe the position

LightHouse is audit-ready: every control on these pages is enforced in code or in the platform, and each says how you can verify it. Your audit log, your access review and your content reader’s log are the evidence. Atlantic holds no certification today, and these pages do not claim one.