Security & privacy.

How does Bouw Botje access Exact Online Construction?

With an API key that you create yourself in Exact Online Construction (Exact Online Bouw, formerly Bouw7), on the API access page of start.bouw7.nl. You paste that key on the connection screen in your Bouw Botje account. There is no Exact sign-in screen and no OAuth consent on the Exact Online Construction side: the API key is the only credential.

Bouw Botje stores the key encrypted (AES-256-CBC with an HMAC-SHA256 integrity check) and only exchanges it server-side for a short-lived access token of the Exact Online Construction API. That token is never logged.

• The API key is an organisation-wide credential, so Bouw Botje does not follow the permissions of an individual Exact user account.
• If you generate a new key in Exact Online Construction, the old one stops working immediately, for Bouw Botje too.
• The Exact Online Construction access token lives about 15 minutes; Bouw Botje requests a new one automatically.

How does my AI assistant sign in to Bouw Botje?

Via OAuth 2.1 with mandatory PKCE (S256). Your AI assistant sends you to Bouw Botje, you sign in with your own Bouw Botje account and approve (or deny) on a consent screen. Only then does the assistant receive an access token. The AI assistant never sees your password; Bouw Botje stores passwords only as a hash.

• Authorization codes are single-use and valid for 10 minutes.
• Access tokens are valid for 60 minutes and are renewed with a refresh token.
• Redirect addresses must use https (or http on your own computer, for desktop apps).
• All traffic runs over HTTPS/TLS with HSTS.

Where is my data stored and how is it separated?

Bouw Botje synchronises your Exact Online Construction data per administration into its own, isolated database. Search and read questions from your AI assistant are answered from that copy, which is fast and puts no load on Exact Online Construction. Write actions (create, update, delete) go directly to the Exact Online Construction API.

• Hosted at Scaleway in the Netherlands (EEA); Bouw Botje does not transfer data outside the EEA.
• Each administration has its own database; mixing with other customers' data is ruled out by design.
• Databases are encrypted at the hosting provider; backups are encrypted.
• Production databases are only accessible to designated administrators of Industrial IT.
• Bouw Botje does not process Dutch citizen service numbers (BSN) or special categories of personal data.

Can the AI change data in Exact Online Construction on its own?

No. The connection is read-only by default. As long as writing is off, the 80 write tools do not exist for your AI assistant: they are left out of the tool list, and an attempt to call one anyway is refused with a clear error message. Of the 206 tools, 126 are read-only.

You enable write access per user under Settings → AI connection (MCP). This requires the Advanced plan or the free trial; Basic is always read-only.

• A tool counts as writing as soon as its name indicates a mutation (such as create, update, delete, set, vote or restore); when in doubt, it counts as writing.
• Approving or rejecting contracts and purchase invoices also counts as a write action.
• Tip: for actions with financial impact, let the AI summarise first and confirm yourself.

What does my AI provider see of my data?

Only what the tools return in response to your questions. Bouw Botje does not send a complete administration to the AI; the assistant requests specific data, such as a single project or a list of invoices. What you share in the chat, and what the tools put into it, is subject to the terms of your AI provider (OpenAI, Anthropic, Microsoft, Google, Mistral, Perplexity, xAI and others).

AI providers are therefore not sub-processors of Bouw Botje: that relationship runs directly between you and the provider. If you do not want conversations used for training, check the settings and policy of your assistant.

What is logged?

Every tool call via MCP is recorded: which tool, with which parameters, the result, the duration, the AI client and the reason the AI itself gives for the call. Refused calls (for example a write attempt in read-only mode) are logged too. Fields such as API keys, passwords, tokens and secrets are masked before they reach the log.

• You can review your own tool calls under MCP activity in your Bouw Botje account.
• Retention: 180 days for non-critical and 365 days for critical audit and security logs, after which they are purged automatically.

How do I revoke access?

At three levels, without needing us:

• One AI assistant: under Connected AI clients or Settings in your Bouw Botje account you revoke the connection or all tokens. This takes effect immediately, including for the refresh token.
• Write access: switch read-write off in Settings; the write tools then disappear from the tool list.
• The whole connection: remove the connection in Bouw Botje, or generate a new API key in Exact Online Construction. Bouw Botje then retrieves nothing more; synchronised data is deleted within 30 days (encrypted backups within 90 days at most).

Which measures are in place at a glance?

Technical details such as endpoints, token lifetimes and limits are on the technical specifications page.

Who are Bouw Botje's sub-processors?

Not a sub-processor: Exact Online Construction (your source system, used on your instruction), Mollie B.V. (independent controller for payments) and the AI provider you choose. Bouw Botje is a service of Industrial IT (Dutch Chamber of Commerce 67449727), Ugchelen, the Netherlands.

How do I handle the GDPR side?

Generate a GDPR data processing agreement (Article 28) between your organisation and Industrial IT on the data processing agreement page. It lists the types of personal data, the sub-processors, the retention periods and the technical and organisational measures. Submit a GDPR request (access, rectification, erasure) via the contact form with the subject “GDPR request”.

Frequently asked security questions