Security
We hold the permissions. We don’t hold your work. Here’s exactly what that means.
Locked inside your browser before anything is uploaded. We store something we cannot open. The readable version never leaves your computer.
Never comes to us at all. It moves from your systems to your partner’s. We handle permission and nothing else.
Unlocked only inside your own running software, on your own infrastructure. We’re never in the path.
A breach of NakodaX does not expose your work, because we don’t have it.
Who opened what, and when. That history belongs to you, and it’s the thing most companies discover they’ve never had.
Withdraw access at any time, effective on the next attempt to open.
Access that ends on a date you set.
Cap how many times something can be opened.
Share only part of a document.
A record of every open, exportable.
Every recipient controlled independently.
We think you should know exactly where any AI touches your work, so here it is.
Your documents and data: never. No AI reads, processes, or trains on them. They’re encrypted before we could, even if we wanted to.
Source protection: optional, and off unless you turn it on. When you protect source code, your developers still need to work against the parts that are now locked. We can optionally generate example inputs and outputs to make that easier.
Send it over. We’d rather answer it than schedule a call about scheduling a call.