Encrypted doesn't have to mean unarchived.
Nota archives your organization's encrypted messages while your people keep the apps they trust. Your archive is encrypted separately from every other customer's, and the service that writes it can't read it back. We keep your records for compliance, and we never analyze or sell them. With customer-held keys, Nota can't read your stored records.
The problem
Secure messaging shouldn't put your records at risk.
End-to-end encryption keeps conversations private, and it also keeps them out of the archive your regulator, records officer or general counsel expects you to have. Most organizations end up banning the apps and hoping for the best, or moving people to modified versions that give up the protection they wanted in the first place. Nota gives you a better option: people stay on the real app, and you keep the record.
How it works
Three steps from first scan to proof.
-
Each person links Nota
They scan a code in their own app, the same way they would add a laptop. Nota appears in their device list, where they can see it at any time.
-
Nota keeps the record
Messages, edits, deletions, reactions and attachments are encrypted and archived as they arrive. Each one is saved before Nota confirms receipt, so a restart never costs you a message. When someone deletes a message or sets it to disappear, the archived copy stays.
-
You can prove it
Every record joins a tamper-evident chain, and each person has a running coverage log. Exports carry their own proof, so an examiner can check them offline without trusting Nota.
When the questions come
Help answering what you get asked.
When a regulator, investigator or your own counsel comes asking, Nota gives your team somewhere to look. Searching and exporting messages are part of Supervision.
What did they disclose?
Search a person's archived messages for a word or phrase, under an approved request, and read what matches.
AvailableWas that message edited or deleted?
Edits, deletions and disappearing-message settings are on the record, and the archived original stays.
AvailableWere they covered on that date?
Each person's coverage log shows when capture was running, and any gaps with their cause.
AvailableCan you prove these records are real?
Exports carry a proof file that anyone can check offline, showing each record matches what was captured.
AvailableWho has already seen these messages?
Every request, approval, search and export is on your audit trail, with the stated purpose behind it.
AvailableWho did they talk to, and who said what?
See everyone in a conversation, who sent each message, and search by the people involved.
PlannedWhy Nota
What you'll want to know about Nota.
Will we know if someone isn't covered?
See each person's status at a glance. Any gap is on the record with its start, its end and its cause.
Could anyone alter a record?
Records are only ever added. Edits and deletions become new entries, and a scheduled check confirms the chain is intact without reading a single message.
Who can read the messages?
Every request names a purpose, one person and a date range, and needs two approvers. Access expires after 72 hours, and each step lands in your audit trail.
Can we hand records to an examiner?
Export the messages and attachments in scope with a proof file. Anyone can verify the bundle offline, with no Nota account.
What if someone removes the device?
Nota notices, opens a gap and shows it on your dashboard, so you find out from Nota and not from an examiner.
How do we handle joiners and leavers?
Connect your identity provider and directory, and enrollment follows your groups. When someone leaves, capture continues through a 30-day hold.
Custody
You hold the key. Nota holds the locked archive.
Strong records programs split the power to read from the power to change. With customer-held keys, you hold the key and Nota can't read your stored records. Any change to them shows up when you verify. Capture still handles each message in memory while it archives it, under separate controls. You can check the archive yourself, within the limits we state in the documentation.
Available now
- Your records are encrypted separately from every other customer's.
- A capture service that can add records and can never read them back.
- Nota staff are denied access to your records, and any change to that is logged.
- An optional retention lock that nobody, including Nota, can undo before the term ends.
- A clean exit: when your key is destroyed, your archive is unreadable for good.
Attested capture
- Capture runs in a sealed environment that no operators can log into.
- Before your keys open, the environment proves cryptographically that it's running the exact software we approved for release.
- A tampered build can't unlock capture.
- Nothing can connect in to capture. Each customer's capture runs on its own, with access to that customer's records only.
Customer-held keys
- Encrypt your archive with a key in your own key system.
- Read your records with your key. Nota can't read them.
- Any change to the stored records shows up when you verify. With a retention lock, nobody can delete them before the term ends.
- Your key activity stays in your own logs.
- Withdraw the key and your records become unreadable.
- Available for keys in AWS KMS, with Standard or Attested capture. Google Cloud KMS and hardware security modules are coming. Hosted review is off.
Channels
One archive for every encrypted channel.
One set of records, one coverage view and one retention policy, whichever app the conversation happened in. Nota works with a widely used encrypted messenger today and more are on the way. Tell us which apps your people use, and we'll show you where each one stands.
Who it's for
Made for teams with a duty to keep records.
Watch it catch a problem.
In a live demo we enroll a test account, capture messages as they are sent, restart the service mid-stream and unlink the device on purpose. You see the gap appear, the export verify and the audit trail record every step.