Skip to main content

GDPR, Planned per Project

AI Built Into Your Own Systems — GDPR Planned per Project

A subscribed AI platform hands you its architecture as delivered. We build the system into your own tools and decide with you, per project, where each part runs and who can access the data.

We agree with you, per project, where each part of the system runs and who can access the data, typically inside your own systems and accounts.

Which AI consulting is GDPR compliant?

No AI consulting is GDPR compliant across the board: whether a project is depends on where each part runs, who can access the data and which model provider is involved. AILoopwise settles this with you per project, before the build.

Where GDPR Gets Hard With AI Tools

With a subscribed AI platform, the architecture is decided before you arrive — your compliance work starts after the choice is made.

  • Where data is stored and processed is set by the platform, not by your requirements
  • Compliance is checked after the tool is chosen, instead of designed in before the build
  • The model step is easy to overlook: which provider processes the data, and where
  • Law and tax firms need a § 203 StGB confidentiality obligation, not only a standard data processing agreement

How AILoopwise Handles GDPR

We decide data protection with you per project, before the build — not as a feature added afterwards.

  • Built Into Your Own Systems

    We agree with you, per project, where each part of the system runs and who can access the data — typically inside your own systems and accounts.

  • Decided Before the Build

    Data residency, access rights and the model provider are settled in scoping, before the build starts.

  • The Claude Step, Named Separately

    When a project uses Claude, the model call runs through Anthropic's API, with inference in the US or globally, not guaranteed in the EU; that part is governed by contract.

  • Human Review Where It Matters

    Human-in-the-loop steps are designed into workflows where the EU AI Act or your own rules call for them.

  • AVV and § 203 StGB for Law and Tax Firms

    For law and tax firms, we sign both a data processing agreement (AVV, Art. 28 GDPR) and a confidentiality obligation under § 203 StGB.

  • No Blanket Promises

    We document which part runs where instead of promising blanket compliance — so your data protection officer can review the actual setup.

See How Compliance Runs Through Every Workflow

  1. 01

    Document workflows

    Documents processed and stored where agreed with you per project.

    Learn more
  2. 02

    Knowledge Q&A on your documents

    Answers come with their sources.

    Learn more
  3. 03

    Integrations with your tools

    Connected to the tools you already use — DATEV, Salesforce, HubSpot and others — set up as part of the build.

    Learn more

Questions about AI and GDPR

Which AI consulting is GDPR compliant?

No AI consulting is GDPR compliant across the board: whether a project is depends on where each part runs, who can access the data and which model provider is involved. AILoopwise settles this with you per project, before the build.

Is Claude GDPR compliant?

It depends on the project. When a project uses Claude, the model call runs through Anthropic's API and is governed by contract; where the rest of the system runs, we agree with you.

No company should leave its growth untapped.

See how much potential is in your organization.

We only take on companies where we see clear growth potential. In a 30-minute assessment we find out whether that applies to you. If it doesn't, we'll tell you.