Legal

Sub-processors.

The third-party services Elennai (operated by ElennAI ApS, VAT: DK46697146) uses to deliver the platform. Our Data Processing Agreement references this list. Pro and Scale customers get 30 days notice by email before a new sub-processor is added.

Active sub-processors

ProviderPurposeLocationData accessedTransfer mechanism
RailwayApplication + database hosting, first-party error tracking, and product-analytics event storage (Postgres). Object-storage migration target.europe-west4 (Eemshaven, NL)All operational data, first-party product-analytics + error eventsEU/EEA - none required
Cloudflare R2Object storage for uploaded documents + file metadata (migration to Railway Buckets in progress)EU jurisdictionUploaded documents + file metadataCloudflare DPA (EU jurisdiction)
Google (Gemini)LLM provider for chat answers + embeddingsMulti-region (EU-eligible)Chat message + retrieved doc chunks (no long-term identity)Google SCCs
StripeBilling (payments, invoices, webhooks)US (with EU operations)Customer email, plan code, payment-method metadataStripe SCCs + DPA
ResendTransactional email (welcome, password reset, newsletter)EU (eu-west-1)Recipient email, message bodyEU/EEA - none required
Managed RedisoptionalCache + cross-replica rate-limit state (when enabled)EU regionCache keys + counters (no document content)EU/EEA - none required

What stays in-house

  • Postgres + pgvector runs on Railway in the same EU region as the application - not a separate sub-processor.
  • Embedding generation is delegated to Google Gemini (listed above); we run no separate embedding vendor.
  • Product analytics, when enabled, is a first-party endpoint on our own API that writes into the same Railway EU Postgres as the rest of the application. No third-party analytics vendor is engaged and no separate analytics infrastructure exists - it is an expanded purpose of existing infrastructure, not a new sub-processor.
  • Visitor country and organisation are derived on our own servers: the country from an offline database that ships with the application, and the organisation from the public registry that publishes which organisation a network range is registered to. The registry is asked about a network block (a /24 or /48), never about a visitor's address, never about who they are, and never about which site they were on - and the answer is the registration record that registry publishes to anyone who asks. Querying a public register is not a sub-processing relationship: nobody processes personal data on our instructions, and no visitor data is disclosed to anyone. We deliberately do not use a commercial IP-to-company service, which is what would put a new row in the table above.
  • Slack channel traffic flows through the customer's own Slack workspace, where the customer is the data controller; Slack is not Elennai's sub-processor for that.

Changes and the DPA

When a sub-processor is added, Pro and Scale customers receive 30 days notice by email and can object before the new processor goes live. Free, Starter, and Growth customers see the change reflected on this page.

Today all data is hosted in the EU region. As additional data regions launch, this page will show the sub-processor list for each region. To request the Data Processing Agreement, write to support@elenn.ai.