GDPR Compliance

Documentation in progress. This page describes technical controls relevant to GDPR; it is not a GDPR compliance certification or legal assessment. Hoziron itself is a data processor/sub-processor in most deployments — your organization remains the data controller and is responsible for its own GDPR compliance program.

Current capabilities

The platform provides technical controls that support GDPR requirements:

  • Right to erasure (Art. 17) — Agents and their data can be fully removed: suspend the agent, then uninstall it (hoziron-cli agent suspend <id> → hoziron-cli catalog uninstall <name>). Uninstall tears down semantic memory, KV-scoped data, knowledge-graph entities, and session history for that agent.
  • Data minimization (Art. 5(1)(c)) — PII is tokenized at the point of detection; only tokens (not raw values) flow between workflow steps and to cloud LLMs by default. Hydration to real values requires an explicit rule in the operator-owned PII policy — there is no default-permissive path.
  • Audit trail (supports Art. 5(2) accountability) — Every authenticated API operation is logged with actor identity, action, target, outcome, and a SHA-256 hash chaining to the previous entry. Chain integrity is independently re-verifiable via GET /security/verify.
  • Data residency (supports Art. 44 restrictions on transfers) — Air-gapped deployment with local-only models (Ollama/vLLM) keeps all inference and data processing on infrastructure the operator controls; cloud providers can be disabled entirely.
  • Access control — RBAC (five roles) restricts who can read or modify agent data via the API, with per-key expiration and audit logging of access.

Coming soon

  • Data processing inventory / Article 30 record template
  • DPIA (Data Protection Impact Assessment) template
  • Configurable data retention policy (beyond the audit trail's max_entries pruning)
  • Consent management integration patterns

Related: