complyee.ai

Sub-processors

Last updated: 5 September 2026

A sub-processor is a third party that can process customer data on our behalf when we run Complyee for you. The list below covers every workspace running on the Complyee-operated environment, and we keep it current rather than reconstructing it when a questionnaire arrives.

The controls these providers sit behind are described on our security page.

Current sub-processors

  • Google Cloud EMEA Limited

    Purpose
    Cloud Storage, Vertex AI Search and Gemini: document storage, search index, answer generation and audit-log storage.
    Data it can process
    Uploaded documents, questions asked, generated answers, audit events.
    Location
    EU by default; the region is fixed per workspace.

  • Supabase, Inc.

    Purpose
    Application database and authentication. Supabase runs its managed infrastructure on Amazon Web Services.
    Data it can process
    Account email address, workspace membership and role, workspace settings, document and workspace request records.
    Location
    EU

  • Cloudflare, Inc.

    Purpose
    TLS termination, edge network protection and enforcement of per-workspace network rules.
    Data it can process
    Request metadata and IP addresses.
    Location
    Global edge network

  • Lovable (Lovable Labs)

    Purpose
    Application hosting, platform services and platform email sending on managed infrastructure.
    Data it can process
    Recipient email address, email content, request metadata.
    Location
    Managed by the provider

  • Paddle.com Market Ltd

    Purpose
    Merchant of Record for paid plans: checkout, payment processing, billing, invoicing, sales tax and VAT, refunds and chargebacks. Paddle.js is loaded only on checkout and billing pages.
    Data it can process
    Billing name and email address, billing country, plan and transaction metadata, payment details collected by Paddle directly. We never receive full card details.
    Location
    UK / EU / US

  • Prodengo AB (Agent Control Room, agent-cr.com)

    Purpose
    Policy engine that supervises agent work: it decides, step by step, whether an agent may read a document, call a model or write a result back, and it holds the decision and approval log for those steps.
    Data it can process
    No document content and no answers. Workspace identifier, agent name, requested action, the document identifier the step concerns, and a one-way fingerprint of the content the step would act on.
    Location
    EU

  • IONOS SE

    Purpose
    Mailbox hosting for Complyee's own company addresses.
    Data it can process
    Email sent to or from Complyee staff addresses.
    Location
    EU

Model use and data residency

Answer generation runs on Gemini inside the same Google region as the workspace it serves. Your documents, questions and answers are not used to train models.

New workspaces are placed in the EU by default and the region is fixed for the lifetime of the workspace.

Agent supervision

Work performed by agents inside Complyee is supervised by a separate policy engine, Agent Control Room, running on agent-cr.com, operated by Prodengo AB. Every step an agent takes is authorised individually before it happens, and the engine sees only what it needs to decide: the workspace, the agent, the action, the document identifier and a one-way fingerprint of the content. Document text, questions and answers never leave Complyee for the engine.

Bring your own cloud

A workspace can run entirely inside your own Google Cloud project: your storage, your search index, your region, your service account. For those workspaces Google is your own provider rather than our sub-processor, and the Google row above does not apply to your documents or answers — Complyee holds only a scoped credential that you issue and can revoke.

Payments

Paid plans are sold through Paddle, which acts as Merchant of Record. Paddle independently processes the payment, billing, sales tax and VAT, invoicing, refunds and chargebacks, and its own privacy notice applies to that processing (paddle.com/legal/privacy).

Card details are entered in Paddle's own checkout and never reach Complyee; we receive only order metadata such as plan, transaction identifier and billing country. Paddle's checkout script runs only on checkout and billing pages, and never on pages where documents, questions or answers are handled.

Supporting vendors (no customer data)

We also use tools that never touch customer documents or member data, and which we therefore do not list as sub-processors: source code hosting, the development and deployment platform, our domain registrar and DNS, and internal productivity tooling. If your review needs these named individually, we will list them for you.

Changes to this list

This page carries the date it was last updated, and it is the authoritative version. We have not yet committed to a fixed advance-notice period for new sub-processors; where a notice window matters to you, it belongs in the data processing agreement and we are happy to agree one.

To be told when this list changes, or to ask about a specific provider, write to security@complyee.ai.

Questions about this list

We answer security questionnaires and discuss data processing terms. Reach us at security@complyee.ai.