What is referential integrity in data?
The short answer
Referential integrity is the rule that every link between records points at a real record. In AI data deals, Spirit Airlines kept links while de-identifying, and the union said links raise re-identification risk. The UK ICO says pseudonymised data stays personal data for anyone with the key.
Two groups use the term for opposite reasons. Database engineers want the links kept. Privacy lawyers want to know who can follow them.
What does referential integrity mean in a database?
A foreign key constraint says the values in one column must match values in a row of another table. PostgreSQL's documentation calls this maintaining referential integrity between two related tables.
Its example has an orders table that points at a products table. Once the constraint exists, no order can name a missing product.
Why do AI companies want the links kept?
A trajectory only shows up when records connect. Fortune described the value in Spirit's archive this way: an IT ticket linked to a Teams discussion, a code change and an operational result. That works only if the links can be rebuilt. Our trajectory entry explains the term.
micro1's David Revland, who works on human data, said in an undated recorded forum talk that micro1 swaps each name for a consistent stand-in across every platform.
The same person gets the same stand-in in Slack and in Google Workspace. micro1 staff said in the same talk that companies cannot pre-scrub. Redacting first destroys the cross-platform trail it needs.
Why does it worry privacy lawyers?
A stand-in that stays the same across tools is a persistent identifier. The ICO says pseudonymised data is personal data in the hands of anyone who holds the additional information. That extra information must be kept apart and secure.
The FTC wrote that hashes are not anonymous and can still be used to identify users. Both points ask one question: can a link be followed back to a person?
What did the Spirit union say?
The union's objection (Doc 1489) quoted section 3(c), the de-identification clause in the sale agreement. It said the clause keeps the joins among timekeeping, pairing, training, payroll and communications data by design. It made no technical claim that a particular record can be re-identified.
Time reported that the union warned even anonymized information about members could be reconstructed. Google told Time the data would be rigorously scrubbed by a third party. Our page on the union objection lists what it asked the court to do.
What should a company ask about stand-ins?
Ask who holds any key that maps stand-ins to real people. Ask whether stand-ins repeat across systems. Ask what the AI company promises about re-association. Pseudonymization versus anonymization and re-identification risk cover the legal test.
Run the rights check before you list anything. We give no legal advice, so talk to a privacy or commercial lawyer in your state before you sign.
micro1 may pay us a referral fee if a company we introduce goes ahead with it. How we are paid
Apply to micro1's data partnership (paid link)micro1's own data-partnerships pagePaid link. How we are paid
Vaultfish helps you run the process. We are not lawyers and this is not legal advice. If you need counsel who knows this area, we can point you to one. Ask for a referral
