+ We practice what we preach—transparent data handling with architectural constraints: +
++ Audit logs may contain: usernames, timestamps, session IDs, action descriptions. No tracking cookies, no behavioral profiling, no cross-site data collection. +
++ Framework operation requires audit trails for governance decisions. BoundaryEnforcer logs blocked actions, CrossReferenceValidator logs instruction conflicts. +
++ Configurable retention (default 90 days). Organizations can set retention based on their compliance requirements. +
++ Access (Article 15), Deletion (Article 17), Portability (Article 20). + Contact: john.stroh.nz@pm.me +
++ Architectural principle: Data minimization is a system constraint, not a policy hope. BoundaryEnforcer prevents PII exposure structurally—audit trails provide compliance evidence. +
+