SecretSafe

← Back to the directory

Profile

Lexis+ AI / Protégé

HQ: UK/US (RELX)7/7 criteria disclosedChecked 2026-10-17

Compare with others →

Data storage 2/3

What the vendor states (our summary):

AWS hosting in several regions incl. France, Germany, Ireland, UK; "local data hosting" stated for Europe incl. UK; region assigned to Swiss customers not stated

What this means: EU/EEA, or selectable region including Switzerland. Where data rests decides which law and which authorities can reach it. Swiss firms often require Swiss residency for client matters.

Source: www.lexisnexis.com/global/privacy/en/subprocessor.page · Checked 2026-10-17

Where the AI runs / sub-processors 1/3

What the vendor states (our summary):

Product page: models process data in the local region (Europe incl. UK); global sub-processor list shows Anthropic (USA), OpenAI (USA) and Google (Global) for Lexis+ AI file uploads

What this means: Can leave the region, or relies on US LLM APIs. Storage and AI processing are often in different places. A tool can store data in Zurich and still send prompts to models in another country.

Source: www.lexisnexis.com/global/privacy/en/subprocessor.page · Checked 2026-10-17

US Cloud Act exposure 1/3 ⚖︎

What the vendor states (our summary):

RELX group (UK parent) on AWS and US AI providers; US affiliates (RELX Inc.) listed for data-centre operations

⚖︎ Judgment call: UK-parented vendor, but hosting and AI providers are US-parent companies and US affiliates provide data-centre operations; confirm the contracting entity.

What this means: Non-US vendor on US-parent clouds/models. The US CLOUD Act lets US authorities require US providers to disclose data in their possession, custody or control, wherever it is stored. This score is always an editorial judgment call.

Source: www.lexisnexis.com/global/privacy/en/subprocessor.page · Checked 2026-10-17

Art. 321 SCC auxiliary terms 2/3

What the vendor states (our summary):

General confidentiality claim for client and firm work; DPA requires confidentiality of authorised staff; no auxiliary-person term

What this means: General confidentiality claim, no auxiliary-person term. Under Art. 321 SCC, auxiliaries of a lawyer are bound by professional secrecy, and Art. 13 para. 2 BGFA/LLCA makes the lawyer responsible for ensuring they respect it. Written auxiliary terms help document that.

Source: www.lexisnexis.co.uk/solutions/protege-general-ai.html · Checked 2026-10-17

revFADP / GDPR processing agreement 3/3

What the vendor states (our summary):

Public LexisNexis DPA with Swiss transfer terms: GDPR references read as the FADP, FDPIC as authority

What this means: Public DPA that names the revFADP. Art. 9 revFADP and Art. 28 GDPR require a contract (or legal basis) when a processor handles personal data on your behalf.

Source: www.lexisnexis.com/global/privacy/en/processor-terms.page · Checked 2026-10-17

No training on customer data 3/3

What the vendor states (our summary):

Does not train or fine-tune AI models on customer data

What this means: Contractual no-training, including model providers. If customer data trains a model, confidential content could surface elsewhere. Look for a contractual ban that also binds model providers.

Source: trust.lexisnexis.com · Checked 2026-10-17

ISO 27001 / SOC 2 3/3

What the vendor states (our summary):

SOC 2 Type 2 and ISO/IEC 27001 listed

What this means: Own ISO 27001 or SOC 2 Type II. Independent audits (ISO 27001, SOC 2 Type II) give evidence that security controls exist and are tested.

Source: trust.lexisnexis.com · Checked 2026-10-17

What to ask this vendor

  1. Data storage In which country and data centre are our documents, prompts, outputs and backups stored?
  2. Data storage Can we contractually fix storage in Switzerland?
  3. Where the AI runs / sub-processors In which countries do the AI models process our prompts, including fallback or peak-load routing?
  4. Where the AI runs / sub-processors Please provide the full sub-processor list with locations, and how we are notified of changes.
  5. US Cloud Act exposure Is your company or any sub-processor in the processing chain a US company or a subsidiary of one?
  6. US Cloud Act exposure How would you respond to a foreign government request for our data, and will you notify us?
  7. Art. 321 SCC auxiliary terms Will you contractually accept auxiliary-person (Hilfsperson) status under Art. 321 SCC and pass it to sub-processors?
  8. Art. 321 SCC auxiliary terms Who at your company or at sub-processors can access our content in clear text?

Is this listing wrong?

Vendors and readers can request a correction. Send the source; we update the record and log the change publicly.

Request a correction

Informational only, not legal advice. Results reflect vendors’ public statements on the date checked and our scoring rules. Verify contracts yourself before using any tool with client data.