Trust and security

What a procurement or security team asks for, on one page: where data lives, who processes it, which controls are built in, and what is still in progress.

Your data, where you decide

We set the location before we build, and write it into the contract. Client data never trains public models.

Swiss-hosted

Servers in Swiss data centres, for data that must stay in Switzerland.

Your cloud

Your own account, in the region you choose, including EU regions in Poland and Germany.

Your servers

Models and agents run inside your own network when data cannot leave it.

Hosted model APIs

Only where you approve it, under the provider’s business terms, with no training on your data.

Built in, not bolted on

Every system we build ships with these controls switched on. You decide what to relax, and the audit trail records it.

Security

Least privilegeEach agent gets only the tools and data its job needs. People sign in with OAuth and act under their own permissions.
Secrets stay secretKeys live in a secrets manager, never in prompts or code. Separate encryption keys per client where data must never mix.
Isolated infrastructureKubernetes namespaces and network policies, with models served inside your perimeter when data cannot leave it.
No training on your dataClient data is never used to train public models, and hosted APIs are used only under terms that say so.

Guardrails

Read-only by defaultAnything that creates, changes or sends waits for a named person to approve it.
Checks on what goes in and outHidden instructions in documents and web pages are stripped, personal data is masked where it is not needed, and drafts are checked against your policy.
Limits and a stop buttonSpend caps, rate limits and scope limits for every agent, and a switch that stops any agent at once.
Evaluation gatesA test set runs before every release. A change that lowers the score does not ship.

Audit

Every call loggedWho asked, which agent acted, what it read, what it changed and when.
Approvals with a nameEach approval records the person and the exact version they approved.
Retention you setLogs kept as long as you decide, at least six months where the EU AI Act asks it of high-risk systems, and exportable on request.
Documentation from the logsRecords of processing, impact assessments and technical files built from the same trail.
Audit trailAllowedWaiting for a personBlocked
TimeWhoActionDataResult
09:14:02Invoice agentRead the latest contract for a clientCRM · contractsAllowed
09:14:05Invoice agentDrafted a payment reminder e-mailE-mail · draftWaiting for a person
09:16:40Anna M.Approved and sent the reminderE-mail · sentAllowed
09:17:12Invoice agentTried to change an invoice amountERP · invoicesBlocked: write not enabled
09:20:31Research agentOpened a web page with hidden instructionsWeb · supplier siteBlocked: instructions removed
Sample entries showing what the audit trail records for every system we build.

Subprocessors

The services that run this website. Each client project lists its own subprocessors in the data processing agreement.

ProviderPurposeLocation
Hetzner Online GmbHHosting of this websiteGermany
CloudflareContent delivery and proxy in front of this websiteGlobal network
Google Workspace (Google Cloud EMEA Ltd)E-mail, including messages sent to [email protected]Global network
Google FontsWeb fonts for this websiteGlobal network

Status, honestly

Data processing agreement
Available on request
GDPR and revFADP
Built into every project
EU AI Act documentation
Prepared per system

Found a vulnerability? Write to [email protected] and we will answer before anything else.

The same logs and controls produce the compliance paperwork for the revFADP and the EU AI Act.