Compliance
Evidence of your AI use
from day one.
Every AI call through CareProxy logged, classified and signed, so you can show what happened when the regulator asks. CareProxy supports your work on GDPR, the EU AI Act, NIS2 and ISO 27001; compliance is achieved in your overall setup.
Operational reality check
What do you actually have when the regulator calls?
GDPR gives you 72 hours. The AI Act requires evidence on demand. Here's what you must document, and what CareProxy delivers automatically.
Manual assessment for every AI tool employees use. Rarely updated. Documentation scattered across Word files.
The actual AI traffic is logged per triage decision, so the assessment rests on what happens, not on an estimate.
Must list every AI-related processing activity, legal basis, and recipients. Problem: you don't know precisely what employees send where.
Every AI call through CareProxy is classified, routed and logged, so the record can be built on the actual traffic.
Required for any data transfer outside EU/EEA. Public cloud AI = US transfer. No log = documentation gap.
High-risk data stays on EU soil. For low-risk: hash-chained evidence of exactly what was sent.
High-risk AI systems require formal conformity assessment before use. Employees use tools you have never assessed.
Only the AI destinations you have approved receive traffic through CareProxy. The audit trail shows what is actually in use.
Requires a contract with every AI provider. Employees bypass procurement = shadow IT. Legal exposure.
Only approved AI destinations receive traffic through CareProxy. Everything else is refused.
Data subject requests insight into AI processing of their data. Without a central log, response time breaks the 72-hour rule.
Query session-ID → get a SHA-256-verified list of routing decisions, trigger rules, destinations. Minutes, not days.
Basis: GDPR Regulation (EU) 2016/679 · AI Act Regulation (EU) 2024/1689 · Danish DPA guidance 2024–2025.
Evidence in an incident
What you can actually document when authorities call
The audit chain, the one-click export, and the external timestamp anchor together support three regulatory frames. Technical depth lives on the architecture page. Here is the essence.
What you can prove
For every clinical request: which client, which department, which model, hashes of what went in and what came back, which rules triggered a block. Hashed, signed, tamper-evident. The chain survives restart, verifiable from the database alone.
How you prove it
One-click export from the CISO dashboard produces a self-contained JSON file with the chain, public key, and verification instructions. The receiver runs openssl ts -verify plus sha256sum. If anything has been touched, verification fails: proof in itself.
What it covers
ISO 27001:2022 A.8.15 (logging), GDPR Art. 32 (security of processing), NIS2 Art. 21(2)(c) (incident handling). The concrete requirements are listed below.
The concrete frames
Requires event logs to be retained and protected against change. Our hash chain, Ed25519 signature and Postgres persistence support the control in a single mechanism.
The duty to ensure "ongoing confidentiality, integrity, availability, and resilience" of processing systems. The external RFC 3161 timestamp anchor documents integrity independently of your own signing key.
The one-click export gives compliance leads something concrete to hand over to authorities, not a CSV dump without integrity proof.
Ready to take control of your AI infrastructure?
CareProxy is under active development. Join the waitlist to be notified as soon as pilot installations open.
Or reach out directly kontakt@careproxy.dk