Werkborg Trust Center
The Trust Center brings human oversight, technical measures, data flows and document status together in one place.
Intended delivery
Authority boundary
Certifications or documents that do not exist are never implied.
Final controls and roles remain dependent on the specific implementation.
Control register
Each state distinguishes a visible design, a local test and operation at a customer. None of these records proves production readiness without separate acceptance.
A0 and A1 have been tested locally with sample data. A2 and A3 are design only and have not been executed locally; customer use requires separate permissions and acceptance tests.
Least privilege, environment separation, fail-closed behaviour, logging and stop procedures are design requirements; production operation is not proven.
Purpose, roles, legal basis, retention, access and deletion depend on the customer flow and selected providers.
The intended source-to-draft-to-decision path and its stop points are explained; no customer flow is connected or tested.
Model, hosting, region, logging, training use, exit and fallback are recorded per use case.
A category register exists; final parties follow only after provider and customer selection.
Before production, periods and deletion evidence are linked to data types, contract and customer policy.
A publicly tested reporting channel and an operational incident process must exist before go-live.
Data export, credential revocation, configuration handover and deletion belong in every production acceptance.
Data flow
The path below is an architecture pattern. Systems, fields, countries and retention periods are determined only in a real implementation.
Only an agreed mailbox, form, document set or API scope.
Normalise, reference the source and expose uncertainty.
A structured proposal; no hidden external action.
A named role sees context, scope and consequences before approval.
Only when separately connected, tested and authorised.
Record actor, version, decision and outcome; access can be revoked.
Evidence boundary
A deterministic Service Intake flow with sample data, human decision, stop control and local audit export.
Local registers and templates exist, but they do not prove operational control at a customer.
No testimonial, production saving, SLA, incident history or connector operation is inferred from the demo.
Werkborg claims no ISO certification, assurance report or legally approved compliance position here.
Pilot gate
Who is controller and who is processor for each data flow?
Which fields are necessary, prohibited and where are they stored?
Which actions may the operator prepare and which role may approve them?
What happens with missing information, source conflict, a safety signal or provider outage?
How are export, revocation, rollback, incident reporting and final deletion tested?
FAQ
Not on the evidence of this website or local documentation. No certification is claimed.
No. Roles, purposes, data, risks and suppliers differ per implementation and require appropriate legal and organisational assessment.
That cannot be stated generally without the selected provider, contract and configuration. The decision must be recorded visibly for each implementation.
A tested exit path is a production condition: export, credential revocation, configuration handover and deletion evidence must be confirmed contractually and technically.
Next step
No generic AI presentation. Bring volume, systems, exceptions and the human decision-maker.
