Security and operation

Security decisions, instance by instance.

The Core has bounded test evidence for governance controls. Deployment security, processing locations and contractual commitments are established for each instance before productive processing.

01

Isolated instance

The target deployment isolates each client instance. Its database, storage, access routes and authorised people are documented and verified before productive processing.

02

Data regions and subprocessors

Data regions, subprocessors and any third-country transfers are confirmed in writing for the instance before productive processing. The current processing chain belongs in its security review.

03

Models and training

The model provider, processing terms and data route are specified for each instance before productive use. No provider or training condition is assumed from the Core architecture alone.

04

Human approval

In bounded Core tests, an eligible human approves the exact stored output before deterministic delivery. An enabled client workflow must pass its own deployment checks.

05

Evidence and audit trail

The tested Core records execution basis, check results and approvals. The scope and method of audit export are confirmed for each deployment.

06

What actually applies under the EU AI Act

Governance features such as versioned evidence, checks and human approval can support internal control processes. This is not a compliance badge. Applicable obligations depend on the concrete use.

07

Export, retention and deletion

Brand Truth sits in the Brand Definition, a documented, machine-readable format. Export, retention, deletion and surviving audit evidence are specified in the client contract and verified for the deployment.

We answer questions from procurement or IT security directly. hello@supakraft.ai