How data moves through the HIHB app
The diagram shows where data is kept, where it reaches the AI model and where it is anonymised. The sample record in it is invented. The explanation in words is on the page GDPR and the EU AI Act.
Swipe sideways to read, or pinch to zoom.
[CLIENT] BROWSER
Participants
Management,
department, HR
TLS · encrypted
Participants
Management,
department, HR
TLS · encrypted
01 Access check on every requestPROCESS
Permissions by role. Without an explicit assignment, nobody sees a client.
Permissions by role. Without an explicit assignment, nobody sees a client.
Client 1
Sessions, cards
skills, documents
own DB file
Sessions, cards
skills, documents
own DB file
Client 2
Sessions, cards
skills, documents
own DB file
Sessions, cards
skills, documents
own DB file
Client 3
Sessions, cards
skills, documents
own DB file
no path between clients
Sessions, cards
skills, documents
own DB file
no path between clients
Account patterns AOPTIONAL
learns only in account A, suggests only there
can be switched on and off
learns only in account A, suggests only there
can be switched on and off
Account patterns BOPTIONAL
learns only in account B
can be switched on and off
learns only in account B
can be switched on and off
03 Context boundaryPROCESS
The AI receives only this client's own slice
The AI receives only this client's own slice
05 Anonymisation for patterns
PROCESS
no names, figures, companies, roles
released by a customer
origin link deleted after 30 days
PROCESS
no names, figures, companies, roles
released by a customer
origin link deleted after 30 days
06 Pattern pool, anonymousDATA POOL
voluntary, cross-account, no identifier
of account, client or session
voluntary, cross-account, no identifier
of account, client or session
04 Pseudonymisation before the AIPROCESS
Names become [Person A],
responses are checked
Names become [Person A],
responses are checked
07 AI provenance (Art. 50 AI Act)PROCESS
every AI output labelled visibly
and machine-readably
every AI output labelled visibly
and machine-readably
Claude
language model by Anthropic
language model by Anthropic
Permissions by role
Separate databases
Runner + pull request
Commands: allow list
Emergency stop
Credentials kept apart
TLS, auto certificates
Login protection
Separate backups
Secure deletion
Monitoring + alerting
Security updates auto
① IN THE CLIENT · PLAIN TEXT
Ms Weber, head of sales, is hiring a team lead. Budget 85,000 €
Ms Weber, head of sales, is hiring a team lead. Budget 85,000 €
② TO THE AI · PSEUDONYM (04)
[Person A], head of sales, is hiring a team lead. Budget 85,000 €
[Person A], head of sales, is hiring a team lead. Budget 85,000 €
③ IN THE PATTERN POOL · ANONYMOUS (05)
Role is advertised before the tasks are settled.
no names, figures, roles · released
Role is advertised before the tasks are settled.
no names, figures, roles · released
“Who sees my data?”
Only people explicitly assigned to your client. Checked on every request.
→ 01 ACCESS CHECK
Only people explicitly assigned to your client. Checked on every request.
→ 01 ACCESS CHECK
“Can other customers see us?”
No. One database per client, and the AI sees only that slice.
→ 02 · 03 CONTEXT BOUNDARY
No. One database per client, and the AI sees only that slice.
→ 02 · 03 CONTEXT BOUNDARY
“Does the AI learn from our data?”
No. No training, no storage of inputs, processing in the EU only.
→ AI · GUARANTEES
No. No training, no storage of inputs, processing in the EU only.
→ AI · GUARANTEES
“Do we have to share patterns?”
No. Both pattern levels are voluntary: inside your account and anonymously across accounts.
→ ACCOUNT PATTERNS · 06
No. Both pattern levels are voluntary: inside your account and anonymously across accounts.
→ ACCOUNT PATTERNS · 06
“Does this hold after updates?”
Yes. Every change is checked against the EU AI Act and the GDPR before it goes live.
→ CI · COMPASS
Yes. Every change is checked against the EU AI Act and the GDPR before it goes live.
→ CI · COMPASS
Change to the code
branch → pull request
branch → pull request
Checked by T.R.U.S.S. Compass
EU AI Act and GDPR as a continuous check against every change
powered by Arionkoder: arionkoder.com
EU AI Act and GDPR as a continuous check against every change
powered by Arionkoder: arionkoder.com
Finding?
becomes a task and is fixed
becomes a task and is fixed
Released, then live
with proof of check
with proof of check
1
2
3
4
5
6
HIHB · SYSTEM ARCHITECTURE · DATA FLOW
How data moves through the HIHB app
Production · Application, operations, AI and compliance in the EU
DOC HIHB-ARCH-01 · AS OF 06.11.2026
4 LAYERS · 7 CONTROLS · 12 MEASURES · 3 BOUNDARIES
TRUST BOUNDARY WITH CONTROL
PROCESSDATA POOL
4 LAYERS · 7 CONTROLS · 12 MEASURES · 3 BOUNDARIES
TRUST BOUNDARY WITH CONTROL
PROCESSDATA POOL
EUROPEAN UNION · DATA BOUNDARY
THE PATH OF A REQUEST
1Request from the browser, encrypted
2Access check by role
3Context boundary: own client only
4Pseudonymisation before the AI
5Claude in Bedrock, EU only
6Response checked and labelled
2Access check by role
3Context boundary: own client only
4Pseudonymisation before the AI
5Claude in Bedrock, EU only
6Response checked and labelled
QUESTIONS CUSTOMERS ASK
[APP] APPLICATION LAYER HIHB App
CONTROLS 01–07
02 Separate data spaces: one database file per client
ACCOUNT A
ACCOUNT B
confirmed content only,
and only once released
and only once released
without direct
personal reference
personal reference
Response,
checked
checked
dashed: anonymous suggestions flow back
into every account that takes part (voluntary)
into every account that takes part (voluntary)
[OPS] OPERATIONS LAYER Server in Germany
12 MEASURES · MONITORED
[AI] MODEL OPERATION
Amazon Bedrock
EU regions only (incl. Frankfurt)
GUARANTEES
✓Processing stays in the EU
✓nothing passed to Anthropic
✓no training on your data
✓no storage of inputs
zero data retention
✓data processing agreement with AWS
✓nothing passed to Anthropic
✓no training on your data
✓no storage of inputs
zero data retention
✓data processing agreement with AWS
Bedrock runs the model in its own data centres. Anthropic has no access to inputs and outputs.
EXAMPLE · ONE RECORD, THREE FORMS
to the AI
[CI] CONTINUOUS COMPLIANCE Every change is checked before it goes live
Compass checks the app's code and documentation against the EU AI Act and the GDPR. Compass does not see customer data.
Unlike a certificate issued on one date, Compass keeps compliance current and keeps people in every release (human in the loop).
Unlike a certificate issued on one date, Compass keeps compliance current and keeps people in every release (human in the loop).
Data inside its own client
to the AI, without direct personal reference
anonymous, for patterns and suggestions
Dot:
plain text
pseudonymous
anonymous
HIHB (High-Impact Hiring Blueprint) · HireWorks GmbH