For your IT partner or security officer
Security & governance
Your data is stored in the EU and only your team can reach it; the assistant sees only what your admin releases. We take care of backups, updates and security.
What you can expect
Your data is stored in the EU
On servers in the EU, with a European hosting provider. Only what your admin releases to the assistant goes to Anthropic (US).
Only your team gets in
Everyone signs in with their own account, and you decide who can do what. Your data sits in your own installation, apart from other customers’ data.
We never see your password
Passwords for connected systems are stored encrypted too, and they never reach your browser.
Every update is tested first
A change only goes live after automatic checks. If something still goes wrong, we roll it back.
Topic by topic
Where your data is stored
On Hetzner cloud servers in the EU, in your own installation: own database, data warehouse, file storage, sign-in environment, keys and back-ups.
Signing in
Through a separate, secured login system. Studio never sees your password, and your browser stores no access keys, only a secure session.
Roles & permissions
In each workspace you’re a member or an admin. You share apps and documents per person, with view or edit rights. An admin invites new colleagues.
Own installation per customer
Every customer gets their own installation, which we run. Your data is kept apart from other customers’ data. Inside your installation the database separates your workspaces row by row, and who you are comes from your session, never from what a screen sends along.
Passwords for integrations
Credentials for connected systems never reach the browser and never end up in an export. They’re stored encrypted and only retrieved at the moment they’re used.
Uploaded files
Files go into quarantine first and are read in a separate, locked-down process without internet access. Only then does the content move on.
Backups & export
A backup every day and an extra one just before every update; we test restoring automatically. You can export apps as a file and import them elsewhere; you request the export from us.
Updates
Every change first passes through separate test environments and is checked automatically before it moves on. A failed update is rolled back.
Where does my data go?
It is the question we hear most in care. Here is the short, honest answer.
Where is it stored?
On servers in the EU, with a European hosting provider. You get your own installation, with its own database, sign-in environment and keys; your data is kept apart from other organisations’ data.
Who sees what?
Everyone signs in with their own account. In each workspace you are a member or an admin, and you share apps and documents per person, to view or to edit.
This is how Studio is set up: every field gets a label that says how sensitive it is. A field without a label stays closed.
What goes to AI, and what doesn't?
Nothing goes to an AI model by itself. This is how Studio is set up: you decide per field what a model may see, and you shield names. Every step is recorded and a person decides.
Can it run locally?On request
Rather keep everything on your own server? We can set up speech and AI locally for you.
Per record you see who created or changed it, and admins have an audit log. That helps you show how you handle data.
Agreements about your data
Who processes your data, where it’s stored and who to contact with privacy questions.
- Parties in Studio
- Hetzner (servers in the EU), Cloudflare (secure entry point) and Anthropic (the assistant, only if your admin allows it).
- Parties for this website
- Hetzner (Germany): the server of this website and the backup of form submissions
- Cloudflare: protects and delivers this website (and Studio’s entry point), so it sees the IP address of every visitor
- Brevo: sends the email from forms
- Cal.com: schedules your demo
- Google: the video link for your demo (Google Meet for now)
- Google: our inbox for [email protected] (Gmail, via Cloudflare Email Routing)
- Mistral AI (France): voice demo (transcription and report), only when you use the voice trial
- Privacy policy
- Read the privacy statement
- Contact for privacy questions
- [email protected] · or via the contact form
The IT fact sheet
Everything on one page. Forward it, print it or save it as a PDF.
Denkbaar Studio · IT fact sheet
Architecture, access and data
As of September 23, 2026 · version 1.1
| Setup | Own installation per customer in the EU (database, data warehouse, search index, sign-in environment, keys, back-ups), set up and run by us |
|---|---|
| Hosting | Hetzner, data centres in the EU |
| Ingress | Only reachable over HTTPS, through a secure entry point |
| Identity | Separate login system on an open standard (OIDC); no tokens in the browser |
| Authorisation | Member/admin roles per workspace; sharing per document (view/edit) |
| Logging | Per record: who created and changed it, and when, plus an audit log with filters for admins |
| Separation | Own installation per customer; inside the installation the database separates workspaces row by row; who you are comes from your session |
| Encryption | In transit: HTTPS. Connector secrets: stored encrypted |
| Files | Uploads in quarantine, read by a sealed-off process without internet access |
| Secrets | Stored encrypted; never in the browser or in an export |
| Integrations | Exact Online, Florinet, file import, ECB exchange rates and your own web services (fetching data); outbound traffic only to allowed addresses; no connectors switched on by default |
| Workflows | Own workflow engine within Studio |
| Releases | Every update first through separate test environments, with automatic checks; rollback on failure |
| Backup | A backup every day and an extra one just before every update; we test restoring automatically |
| Export | Apps as a file; you request the export |
| GDPR | Sub-processors: Hetzner, Cloudflare and Anthropic (assistant, only if the admin allows it) The website itself uses separate parties (forms, demo calendar, measurement): see Parties for this website. |
| Vulnerabilities | Report to [email protected] (also in /.well-known/security.txt) |
More detail on request
Extended technical documentation, a completed security questionnaire or a technical session with your IT partner: on request, under NDA if you like.
Questions from your IT team?
Does your IT partner have a questionnaire? Send it over and we’ll fill it in.