How your data flows.

Using one fictional client, Example Construction Ltd, we show the route the data takes: where it is stored, which AI gets to see it, and where a person decides.

  • In the EU processed within the EU
  • May leave the EU with the safeguards the GDPR requires
  • A person decides someone approves here
The source · fictional example

The Odoo of Example Construction Ltd

Invoices, entries, bank lines and contacts live in the client’s own Odoo. Every flow starts there, and the result ends up there too. The dashboard and our client questions service also store a limited amount of data. Which data and for how long is set out in our privacy statement and retention policy (both in Dutch).

1. The dashboard reads the figures

The AI features of the dashboard are off by default. We switch them on per client, by agreement. When they are off, the flow stops after the second block.

  1. The client’s Odoo

    The source. The dashboard reads the figures from here.

  2. Dashboard

    Railway · Amsterdam

    Each client has its own, separated part of the database.

    In the EU
  3. Pseudonymisation

    Only when AI is switched on

    Names, IBAN, email address, phone and VAT number are replaced with codes. The key stays with FID.

    In the EU
  4. Amazon Bedrock

    AWS · EU regions

    Claude models through AWS. No training on your data, and AWS does not share the requests with Anthropic.

    In the EU
  5. You read and decide

    The answer comes back in the dashboard, with the real names. AI explains and proposes, a person decides.

    A person decides

What the AI gets to see

A question about an open invoice at Example Construction, before and after pseudonymisation. Amounts and context remain visible, and not every name is recognised. So it remains personal data.

In the dashboard Jansen Installations Ltd NL00 BANK 0123 4567 89 accounts@jansen.example €4,235.00 · 30 days open
Sent to the AI ⟦Klant 3⟧ ⟦IBAN 1⟧ ⟦E-mail 1⟧ €4,235.00 · 30 days open
  • PDFs and images only go to AI when a separate setting is switched on for that client. They are sent unchanged.
  • Temporary retention. In limited cases, AWS may temporarily store requests or have them reviewed to prevent abuse.

2. A colleague at FID works in the books

For bookkeeping and reviews, AI prepares the work. Our colleague approves before anything is posted.

  1. The client’s Odoo

    AI works directly in Odoo, without exports.

  2. Our own MCP server

    Railway · Amsterdam · with Hemisphere AI

    The secure connection. It determines what AI may read and do in Odoo.

    In the EU
  3. Claude Team

    Anthropic · business account

    Reads what is needed and prepares a proposal. No training on your data.

    May leave the EU
  4. Colleague at FID

    Reviews the proposal and approves it. Only then is the entry posted in Odoo.

    A person decides
  • Langdock is also our AI workspace for day-to-day work. The models there are hosted in the EU. In the EU
  • Fixed automations. A few tasks, defined in advance, run independently on our own DigitalOcean server in Amsterdam. In the EU

3. Example Construction asks a question

“Has the Jansen invoice been paid yet?” Our client questions service prepares a draft answer. Nothing goes to the client before a colleague has approved it.

  1. The question

    Odoo or email (Microsoft 365)

    Through a message in Odoo or an email to FID.

  2. Client questions service

    DigitalOcean · Amsterdam

    Reads only what it needs in Odoo for that one question.

    In the EU
  3. Claude

    Anthropic · through the API

    Drafts an answer, with the sources.

    May leave the EU
  4. Colleague at FID

    Reviews the draft, adjusts it where needed and approves it.

    A person decides
  5. Answer to the client

    For each question, we record what was read, what the draft was and who approved it.

At a glance

ComponentWhereLocationWho decides
DashboardRailway, AmsterdamIn the EUYou
AI features of the dashboardAmazon Bedrock (AWS), EU regionsIn the EUYou or your adviser at FID
MCP serverRailway, Amsterdam, with Hemisphere AIIn the EUColleague at FID
Claude TeamAnthropicMay leave the EUColleague at FID
LangdockModels hosted in the EUIn the EUColleague at FID
Client questions serviceDigitalOcean, AmsterdamIn the EUColleague at FID
Claude for client questionsAnthropic, through the APIMay leave the EUColleague at FID

Also, briefly

  • Email. Our email runs on Microsoft 365. Our IT partner manages and secures that environment.
  • Payment. The dashboard subscription is paid through a payment service.
  • Notifications. Invitations, notifications and invoices from the dashboard are sent through a separate email service.

The full list of parties and the safeguards are in our privacy statement (Dutch). All policy documents are under Documents.

Questions about your data?

In a call, we are happy to walk through what is stored where in your situation, and which AI features are on or off.

Book a call