By Arun Verma
Investor and Advisor, NakodaX ·
NakodaX blog/Data Protection·3 min read
How do you control old copies of customer data?
You cannot find every copy of a dataset. Instead, protect the data before it is exported. With NakodaX Data Protection, each copy is an encrypted file that needs a key, so when you stop releasing the key, old copies stop opening. Copies made without protection are not covered.
You do not need to find every copy. You need to control the one thing that makes any of them readable.
Ask an IT team to list every copy of the customer database and watch the confidence leave the room.
There is production, the replica, a backup from a migration three years ago, a spreadsheet a product manager exported for a deck, a copy at an old analytics vendor, and one on a laptop of an engineer who left.
Nobody was careless. This is what happens when data is useful and copying costs nothing.
Why do retention rules not solve this?
A retention policy works only if you know where the data is and can reach it. For copies inside your systems that is often true. For a vendor's backup or a laptop that never came back, it is not. You can ask for deletion and get an email back, with no way to check.
What does NakodaX change?
Stop chasing copies and make them matter less. If a dataset is protected before it is exported, each file made from it is encrypted. Reading it needs a key, and the key comes from NakodaX under your rules.
Each run of a dataset gets its own keys, so one leaked key opens one run, not the whole archive. You can also set a retention: after it, NakodaX stops releasing the key. Sensitive columns can be left out or sealed, so even an opened file may not show them.
What happens when a vendor leaves or a project ends?
Revoke the license tied to them. The protected files stay where they are and stop opening for any new key request. The old migration backup, if it was made from a protected export, is no longer something you have to worry about.
This is a locked door, not a shredder. Nothing is erased, and anyone who already opened a file keeps what they opened.
What if something goes wrong later?
A former vendor has a breach two years after the contract ended. Instead of a week of tracking down exports, you check which datasets were shared with them and whether their license is still active. NakodaX keeps an activity record of every key request and refusal.
What does this not do?
It does not protect copies that were made unprotected. A plain export that already exists stays plain. The benefit starts with the next export.
The takeaway
Protect data before it leaves, and every protected copy made afterward is covered without you knowing where it is.
Related product
NakodaX Data Protection
Filter rows, protect columns, deliver data to each recipient and enforce access and retention without storing business data on NakodaX. Works alongside a data clean room.
See how it worksCommon questions
Can I make old copies of my data stop being readable?
Only copies that were protected before they were made. For those, stop releasing the key. Plain exports already out cannot be changed.
Does retention delete the data?
No. After retention, NakodaX stops releasing the key. The files are not destroyed.
Does NakodaX store my data?
No. Your data moves from your systems to theirs. NakodaX holds keys and license records only.
