NakodaX

Data protection

Offboard the partner, not just the login.

Files and feeds leave your company every day: to agencies, vendors, partners and resellers. They never come back. NakodaX makes everything you’ve ever sent stop working the moment the relationship does.

Years of partner files in storage cubes, some already gone dark.

You’ve been sending it for years. All of it is still there.

Every hour, every night, every month: extracts, exports, feeds and files move out of your systems into someone else’s.

Then the contract ends. You close their accounts. You disable their logins. You send an email asking them to delete what they hold.

None of that touches the files. Four years of your data is sitting in their storage, in their backups, in the working folders of people who left.

And the uncomfortable version: some of those partners now work for your competitors.

Revoking a login stops them getting anything new. It does nothing about the four years you already sent.

Send it locked. Take it back whenever you want.

  1. 01

    It leaves your systems locked

    Files go out sealed, from the pipeline you already run. Nothing about how you send them changes.

  2. 02

    It opens on your permission

    When their system reads the file, it asks yours for permission. Every time.

  3. 03

    You end it when you want

    Withdraw permission and their next run fails. Not just the newest file. Every file you have ever sent them.

The relationship ends. The data ends with it.

Sealed data capsules traveling into a partner archive; some already dark.

Four things that have never had a real answer

Offboarding

Ending a vendor relationship covers accounts, badges and logins. It has never covered the data. Now it does.

Retention promises you can’t verify

“We delete client data 30 days after termination” is in a hundred contracts and enforced by nobody. Make it something that happens rather than something that’s claimed.

Agreements with an end date

Research agreements, data sharing agreements, pilot programmes: all of them expire on paper. Now they expire in reality.

The partner who becomes a competitor

It happens. When it does, the question is what they walk away holding.

It works with the pipeline you already have

Your data engineers don’t rebuild anything. Files carry on moving the way they always have. Same schedules, same storage, same destinations.

The difference is what happens at the other end: their system asks your system for permission before it can read anything.

Where it fits

Your pipeline stays your pipeline

No new platform to move to, no data to migrate to us.

Works across their stack

Whatever the receiving team runs, there’s a way in that fits how they already work.

Fits how partners actually receive things

Scheduled drops, hourly feeds, one-off exports, bulk transfers.

Set up once per partner

A short onboarding with each recipient, then it runs.

What you can do

Cut off a partner

Everything you ever sent them stops working.

Set an expiry

Access that ends when the agreement does.

Per-partner control

Ending one relationship doesn’t touch any other.

See who’s opening what

A record of every read, by which partner, and when.

Prove it to an auditor

Show that termination actually took effect, not that you asked.

Your data never comes to us

It moves from your systems to theirs. We’re never in the middle.

This is for you if…

  • You send files or feeds to companies you don’t control
  • Those relationships have an end: a contract term, a project close, an offboarding
  • The receiving company runs its own systems on the data
  • You’d struggle to answer “what happens to our data when we leave?”
  • Someone has asked you to confirm a partner deleted something, and you had no way to know

“Deleted on termination” becomes something you can show

Every data processing agreement you’ve signed contains a deletion clause. Every one of them is enforced by trust.

Auditors ask how you know. Regulators ask what you did. Customers ask what happens to their information when a vendor relationship ends.

With NakodaX, the answer stops being a policy document and starts being a record: access was withdrawn on this date, and here is every attempt to open it since.

The questions everyone asks

Do our partners have to change how they work?
They add one step to read the files, at setup. After that it runs without anyone thinking about it.
What if a partner refuses?
In practice they rarely do, because the setup asks very little of them: one short step, once. Vendors, agencies and resellers generally do what their client requires. If a specific partner worries you, tell us on the call and we’ll be honest about whether we fit.
Does our data get stored with you?
No. It moves from your systems to theirs. We handle permission, never the contents.
How fast does revoking take effect?
Their next run. Not eventually, and not after a support ticket.
What kinds of data does this work with?
The everyday shapes: exports, extracts, feeds, reports, transfers. We’ll confirm your specific setup on a call.
What does it cost?
It’s priced by how many partner organisations you send to, not by how much data moves between you. Tell us your numbers and we’ll give you a straight answer.
How many partners can we manage?
As many as you have. Each one is controlled separately.

Make offboarding mean something

Book a call and we’ll map how data leaves your company today, and what it takes to be able to call it back.