Scope
Share only the part someone needs.
Pages or slides of a document, rows and columns of a data file, chosen parts of a codebase.
NakodaX Security
A layered approach to security.
From encryption to secure hosting on Google Cloud, NakodaX offers a layered approach to protecting your information.
- AES-256 encryption
- Encrypted in transit
- Every open on record
NakodaX holds the keys and the permissions, not a readable copy of the sensitive work it protects. Each product locks content at a different point on its way to the people you choose.
How it works
Locked, then checked.
- 01
Lock
Your content is locked with AES-256 before it is shared.
- 02
Share
Send it, stream it or ship it. Recipients get the locked version.
- 03
Check
Every open asks NakodaX for the key. Your rules decide the answer.
- 04
Record
Each open is logged. Change your mind and access ends.
Features
Protection in layers
With NakodaX, you combine several protection controls in one platform, with no need to source and connect separate tools for your team.
1
Who gets in
Choose who opens what.
Separate
Every recipient on their own.
Each recipient is controlled independently, so ending one never touches the others.
Locked before it leaves
AES-256, applied before anything is shared.
2
For how long
Give access an end.
Expire
Access that ends on a date you set.
Trials, pilots and deals close on their own.
Limit
Cap how many times it opens.
Set a number of opens. When they are used, it stops opening.
Checked on every open
Every open asks NakodaX first. Your rules decide.
3
Take it back
Withdraw access. Check the record.
Revoke
Withdraw access at any time.
It takes effect on the next attempt to open.
Audit
A record of every open.
Who opened what, and when. Yours to see.
Nothing held hostage
If you leave, we help you unlock everything you hold.
For your review
What your reviewer asks first.
Encryption
AES-256 for documents, data and code. Everything in transit is encrypted. Documents are encrypted in your browser before upload.
Secrets
Secrets are stored in Google Cloud Secret Manager.
Hosting
Production runs on Google Cloud, deployed with redundancy. Permissions, rules and access history are held there.
Availability and backups
The platform scales and is monitored with Google Cloud Monitoring. Backups, snapshots and disaster recovery are in place. Opening a protected file needs a connection to us, which is how revoke works.
Documentation and questionnaires
Security documentation is available on request from security@nakodax.com. Send us your questionnaire and we will answer it directly.
Report a vulnerability
Email security@nakodax.com. We respond, we fix, and we credit researchers who report responsibly.
What we can see
We hold the keys, not a readable copy.
Locked in your browser
Documents
- We hold
- The locked file, its keys, your rules and who opened it.
- Readable only
- On your device and your recipient's screen.
Straight to the recipient
Data
- We hold
- Keys, licences and a record of each run. Never your rows.
- Readable only
- In your systems and your recipient's.
Locked before it ships
Source code
- We hold
- Keys, licences and a record of every deployment.
- Readable only
- In memory, inside a licensed, running process.
NDA text is the one thing we can read, so it can show before a document unlocks.
AI Protection
A readable file can be pasted into an AI tool. A protected one stays locked.
A forwarded or downloaded copy stays locked until permission is checked. NakodaX does not use AI on your files.
See what AI Protection coversAnswers
Security questions
3 topics, 9 answers. Open a topic to see its questions.
What we hold
3 questions
Where is our information held?
Permissions, access rules and access history are held by us, on Google Cloud. Documents are stored locked, and NakodaX does not store your data. For source code, we keep the keys and the licences.
Does NakodaX store our source code?
We keep the keys and the licences. Your repository stays with you, and the protected copy goes where you choose to publish it.
Does NakodaX use AI on our files?
No. NakodaX does not use AI on your documents, data or source code, and never trains models on your content.
If things change
3 questions
How fast does revoke work?
On the next attempt to open. Software already running at a customer stops on its next check in.
What happens if we stop being a customer?
You keep your files. We walk you through unlocking everything you hold before the relationship ends. Nothing of yours is held hostage.
For your review
3 questions
Can you produce records for an audit?
Yes. Access history shows who opened what, and when.
Do you have a security questionnaire on file?
Send us yours. We answer them properly rather than pointing at a portal.
How do I report a vulnerability?
Email security@nakodax.com. We respond, we fix, and we credit researchers who report responsibly.
Updated
Have a review process?
Send it over. We would rather answer it than schedule a call about scheduling a call.