By NakodaX Marketing team
NakodaX ·
NakodaX blog/Document Protection·4 min read
Revoking a login closes the doors to the building. It does nothing about the files that already left. NakodaX .nkxd files stop opening, on their laptop and in AI, the moment you revoke.
By NakodaX Marketing team
NakodaX ·

Revoke access, and every .nkxd file they downloaded stops opening. For them. And for AI.
People leave. That is normal.
What they take with them is the part nobody plans for. Not out of malice, most of the time. A sales lead keeps the pricing sheet because it was on their laptop. A consultant keeps the client deck because it was in their downloads folder.
Two years ago, that was a paper problem. A file sitting on a hard drive is only dangerous if someone reads it. Now everyone has an AI assistant that reads for them.
Here is what a departed employee can do in the first week of a new job, with files they already have.
Upload your customer list and ask AI to rank accounts by likely deal size. Upload your proposal template and ask AI to rewrite it for their new company. Upload three quarters of board decks and ask AI what your weaknesses are.
None of this requires skill. None of it takes more than a minute. None of it leaves a trace on your side.
Most companies handle departures the same way. Disable the email. Remove from Slack. Turn off the drive.
That closes the doors to the building. It does nothing about what already walked out. Every file that was ever downloaded, attached, or synced to a personal device is still there. Still a PDF. Still an Excel sheet. Still perfectly readable by any AI tool that person now has.
When a document is shared as a .nkxd file, the file on their laptop is not the document. It is a locked container. The content only appears when NakodaX confirms they still have access.
On their last day, you revoke. Every .nkxd file they ever received stops opening: the copy on their laptop, the copy they emailed to themselves, the copy on a USB drive.
And because the file was never readable outside NakodaX, it was never readable by AI either. There is nothing to upload, nothing to summarize, nothing to extract. The downloaded copy is not a risk anymore. It is just a file that does nothing.
The ex-employee is the obvious case. The same problem exists with every external party you ever shared a protected document with: the agency whose contract ended, the vendor you replaced, the freelancer who did one project.
Tie their access to the relationship. When the relationship ends, every protected document you ever sent them ends with it, the same day, with a record of what they saw and when.
Not "do we have a policy for departures."
The question is: if the last person who left ran every document they downloaded through AI this afternoon, what would it find?
If that answer makes you uncomfortable, the fix is not a better policy. It is a document format that stops working when you say so.
A disabled login only closes the front door. Document Protection closes every copy that already left, including the ones sitting in someone's downloads folder.