By Micky Irons, founder of Mickai.
Two pieces of European law now sit on the same desk and seem to contradict each other. The General Data Protection Regulation gives a person the right to have their personal data erased. The EU AI Act requires that high-risk automated systems keep durable logs of how they reached their decisions, so that a regulator, an auditor, or a wronged citizen can reconstruct what the machine did. One law says delete. The other says keep. Compliance teams have spent two years treating this as a paradox to be argued around. It is not a paradox. It is a design problem with a clean answer.
The confusion comes from collapsing two different things into one word: the record. People hear 'keep the record' and picture a folder full of names, faces, and case files that can never be touched. They hear 'delete the data' and picture shredding the evidence that a decision was ever made. Both pictures are wrong. A record of an action and the personal data referenced by that action are separable. Once you separate them, erasure and auditability stop fighting.
Themis weighs erasure against evidence. The balance holds only when the two are measured on different scales.
What each law actually asks for
GDPR's right to erasure, Article 17, is a right over personal data: the information that identifies a living person. It is not a right to rewrite history. When a bank deletes a customer, regulators still expect the bank to show, years later, that a lending decision was taken lawfully, that it was not discriminatory, and that it followed policy. The customer's identity goes. The fact and the lawfulness of the decision remain demonstrable.
The AI Act, for its part, does not ask anyone to retain a person's data forever. It asks for traceability: an account of inputs, model version, and outcome sufficient to investigate a decision after the fact. That account can be true and complete while containing no recoverable personal data at all. The Act wants proof that the system behaved as claimed. It does not want a surveillance archive, and reading it as one is what manufactures the conflict.
Separate the proof from the payload
The resolution is to record a sealed, signed account of every consequential action while keeping the personal data it touched in a separate, erasable store. The account holds what happened, when, under which model and policy, and with what result. The personal data sits behind a reference. Delete the data, satisfy Article 17. The signed account survives, satisfies the AI Act, and still cannot be quietly altered, because tampering would break its signature.
This is precisely what the Open Audit Record does inside Mickai, the Sovereign Intelligence Operating System that runs fifty specialised brains on the operator's own hardware. Every consequential action the system takes is sealed and signed with FIPS 204 ML-DSA-65, the published NIST post-quantum signature standard. The signature attests that an action occurred and has not been changed since. Crucially, what gets sealed is the attestation of the action, not a permanent copy of the citizen behind it. Erase the personal payload and the proof of conduct stands untouched.
Mnemosyne seals the act, not the person. The mark proves what was done; the name it referenced can be let go.
Why a signature beats a backup
A traditional answer to 'keep the record' is to take backups and lock them away. Backups are the wrong tool here for two reasons. They tend to copy personal data wholesale, which is the opposite of what erasure wants, and they prove nothing about integrity, since a backup can be edited as easily as the original. A signed attestation inverts both faults. It carries no personal payload by design, and it makes alteration detectable rather than merely discouraged. You are no longer trusting a custodian to have left the file alone. You are checking a cryptographic seal that either verifies or does not.
There is a second question a regulator eventually asks: how do I know this log was not written after the fact to fit the story? Local signatures answer integrity but not timing. For that, the record needs an independent anchor in time that the operator cannot backdate.
Anchoring time without surrendering data
Mickai anchors a hash commitment of its records to Bitcoin through Pantheon, its own sovereign Layer 1 with a fixed supply of five billion PAN. The word hash matters. What touches the public chain is a one-way fingerprint of the sealed record, never the record itself and never any personal data. The fingerprint proves the record existed at a given point in time and has not changed since. The contents stay private and erasable on the operator's hardware. Pantheon does not move Bitcoin and is not a Bitcoin Layer 2. Anchoring is not spending. It is a timestamp that no one, including the operator, can rewrite.
Now the two laws are both satisfied from the same architecture. A citizen exercises erasure and their data is genuinely gone. A regulator opens an investigation months later and the signed, time-anchored attestation still demonstrates that the decision was lawful, which model produced it, and that the log predates the complaint. Neither right was traded away to honour the other.
Poseidon fixes the record in time. Only a fingerprint reaches the depths; the citizen stays on the shore.
Sovereignty is the quiet precondition
All of this depends on where the processing happens. If decisions, logs, and personal data live in someone else's cloud, erasure becomes a request to a third party and an act of faith that it was honoured across every replica. Mickai runs offline-capable on the operator's own hardware, so the data that must be deleted is in the operator's custody, and the proof that must survive is generated and held by the same party answerable for both laws. Compliance stops being a chain of trust across vendors and becomes a property of the system in the room.
The approach is documented in the open and backed by 101 filed UK patent applications, comprising around 2,234 claims, owned by Mickai LTD, with Micky Irons named as inventor. The patents are evidence that the architecture is specific and defensible, not the argument itself. The argument is simpler: stop treating the record as a hoard of people and start treating it as a seal on conduct.
The Oracle reads both laws as one instruction. Prove the act, release the person, and the contradiction was never there.
The instruction underneath both laws
GDPR and the AI Act are not at war. They are two halves of a single, reasonable demand: be accountable for what your systems decide, and be respectful of the people those systems touch. The only thing that makes them feel opposed is a habit of storing proof and personhood in the same box. Take them apart, seal the conduct, anchor the time, erase the person on request, and both laws are answered by one design. The record, built correctly, does not have to choose.
Written by Micky Irons. Originally published at https://mickai.co.uk/articles/gdpr-says-delete-ai-act-says-keep-the-record-resolves-both. More from Micky Irons and Mickai at mickai.co.uk.
