NoD△ta · Secure Digital Home verified live · prod

Secure Digital Homes · at scale

A Secure Digital Home for Every Client and Employee You Have.

Managed by organizations. Owned by people.

One API gives every client and employee a private capsule for documents, communication, AI access and personal records.

For every business, at any size, free to start. Not a patch on today’s compliance stack, but the layer built for tomorrow.

Get an API key → 🔓 Open a capsule Developer Guide Pricing

What NoData stores🔒 can’t be opened

🔑The key never leaves the person’s machine. The server holds ciphertext it cannot decrypt. Only the private key opens it.your key · your device · never uploaded

You give them the home. You never touch what’s inside.

No portals to build.
No encryption to manage.
No keys to hold.
No data to read. We never see inside.
No data you own by accident. The liability is theirs, not yours.
No breach surface. We store ciphertext we can’t open. (zero-knowledge)

Give it to everyone

One key. One command. Every customer a zero-knowledge home.

your terminal

# 1 · get a free sandbox key
curl -X POST https://api.nodatacapsule.com/v1/register \
     -d '{"company":"Acme"}'

# 2 · scan, classify, approve & seal — content-blind, on-device
npx @nodatachat/capsule-agent --vault-api \
     --source ./customer-docs --apply --zk

That’s the whole integration. Every folder becomes a per-customer capsule, encrypted on the machine, uploaded as ciphertext NoData can’t open. No portal, no key management, no crypto to write.

01Two ways to seal

Managed for speed. Zero-knowledge for proof.

Managed

The server encrypts at rest.

Text arrives over TLS, the server seals it under a KMS-wrapped key, and AI reads are denied by default until you grant a scope. The easy path, and the base for metered access.

text→ server seals → at-rest ciphertext → AI reads only granted tiers

Contract: the server can unwrap under authorization. Good custody, not blindness. NoData still never holds your key.

Zero-knowledge

The agent encrypts on your machine.

The capsule’s keypair is generated locally. Each document is encrypted to the capsule’s public key on-device; only ciphertext is uploaded. NoData holds a vault it can never open.

on-device encrypt→ ciphertext only uploaded → server can’t unwrap → private key decrypts

Contract: plaintext and the key never leave the machine. Proven byte-for-byte, live against production.

02Governed AI

AI reads what you grant. Nothing more. Ever.

Keep data out of AI by default. Open exactly what you choose, and prove what was read.

An AI agent gets a scoped grant and reads only the classifications inside it. Everything else is skipped, not filtered: the model never receives the bytes, so nothing can leak through a prompt.

In a zero-knowledge capsule, even a granted read runs client-side under the person’s key. NoData never decrypts for a model. Every read is a signed, verifiable receipt.

POST /ai-grants — grant an agent scoped classifications
POST /ai-read — deny-by-default enforcement + receipt
Scanner classifies locally with regex, never an LLM

🤖claims-bot · granted: public, internal

public brochure, claim intake● readable

internal policy notes● readable

confidential medical, financial🔒 denied

attorney_client privileged🔒 denied

Denied tiers are never sent to the model — not redacted after the fact. Deny-by-default: if it wasn’t granted, it doesn’t exist to the AI.

03What’s proven

The guarantees, and how they hold.

✓ verified live against production · ◐ enforced in code

🔒

Zero-knowledge seal is realAgent sealed on-device → uploaded ciphertext → downloaded → opened with the private key → recovered byte-identical plaintext. The server never held a decryptable copy.

verified live

🧭

Cross-tenant access is structurally impossibleEvery capsule is pinned to the minting key’s org; there is no code path to another org’s data.

verified live

🔍

The scan never sends data to a modelDeterministic detectors run locally; findings carry a field + type + suggested tier, never a matched value.

verified live

✍️

A human approves every policyThe capsule only suggests a classification; nothing seals without approval, recorded as a content-free receipt.

verified live

🤖

AI reads are deny-by-defaultAn agent reads only the classifications explicitly granted to it; everything else is skipped, not filtered.

in code

🧾

Receipts are tamper-evidentHash-chained (sha256 + chain HMAC), verifiable without NoData in the loop.

in code

04The surface

~14 endpoints. The capsule is the whole API.

Area	Endpoint	State
Onboard	POST /v1/register · /register/resend	✓ live
Capsules	POST·GET /v1/capsules · GET·DEL /v1/capsules/{id}	✓ live
Documents	POST·GET /v1/capsules/{id}/documents (managed + zk ingest)	✓ live
ZK read	GET /v1/capsules/{id}/zk-documents/{docId}	✓ live
AI control	POST /ai-grants · POST /ai-read (deny-by-default)	◐ code
Manage	/members · /revoke · /audit · /embed-token	◐ code
Scanner	/scan/findings · /scan/approve · /scan/execute · install-token	✓ live

05The scanner

Point it at a folder. Capsules fill themselves, content-blind.

regex + checksums · no language model

01 · SCAN

Local & autonomous

Walks the folder on the developer’s machine. Israeli-ID checksum, IBAN, card Luhn, secrets, EN/HE PII, privilege — all deterministic.

02 · SUGGEST

A tier, with a reason

public / internal / confidential / attorney_client per file, grouped one capsule per customer. Values never recorded.

03 · APPROVE

The human decides

The capsule only suggests. You approve each policy, the legal record, as a signed, content-free receipt.

04 · SEAL

Only the approved

Managed, or --zk for on-device encryption. Only ciphertext + the label you approved ever leaves.

Pricing

Access Compute

$0.20 / 1,000 governed access decisions

First 10,000 decisions / moincluded
Human reads (control)flat
Machine / AI reads (compute)metered
Per document sealed$0.05
Capsules · base feefree · $0

The double win

Who buys, and why

It pays for itself the first portal you don’t build, and the first breach you don’t own.

The customer gets a lasting, portable vault they truly own, surviving even if the vendor disappears.
The organization gets a top-secure area for sensitive data and a liability shift: it can prove it never held the keys.
The developer writes almost no crypto. Point the scanner, approve, done.

NoD△ta · Secure Digital Home verified live · prod

Secure Digital Homes · at scale

A Secure Digital Home for Every Client and Employee You Have.

Managed by organizations. Owned by people.

One API gives every client and employee a private capsule for documents, communication, AI access and personal records.

For every business, at any size, free to start. Not a patch on today’s compliance stack, but the layer built for tomorrow.

Get an API key → 🔓 Open a capsule Developer Guide Pricing

What NoData stores🔒 can’t be opened

🔑The key never leaves the person’s machine. The server holds ciphertext it cannot decrypt. Only the private key opens it.your key · your device · never uploaded

You give them the home. You never touch what’s inside.

No portals to build.
No encryption to manage.
No keys to hold.
No data to read. We never see inside.
No data you own by accident. The liability is theirs, not yours.
No breach surface. We store ciphertext we can’t open. (zero-knowledge)

Give it to everyone

One key. One command. Every customer a zero-knowledge home.

your terminal

# 1 · get a free sandbox key
curl -X POST https://api.nodatacapsule.com/v1/register \
     -d '{"company":"Acme"}'

# 2 · scan, classify, approve & seal — content-blind, on-device
npx @nodatachat/capsule-agent --vault-api \
     --source ./customer-docs --apply --zk

01Two ways to seal

Managed for speed. Zero-knowledge for proof.

Managed

The server encrypts at rest.

Text arrives over TLS, the server seals it under a KMS-wrapped key, and AI reads are denied by default until you grant a scope. The easy path, and the base for metered access.

text→ server seals → at-rest ciphertext → AI reads only granted tiers

Contract: the server can unwrap under authorization. Good custody, not blindness. NoData still never holds your key.

Zero-knowledge

The agent encrypts on your machine.

The capsule’s keypair is generated locally. Each document is encrypted to the capsule’s public key on-device; only ciphertext is uploaded. NoData holds a vault it can never open.

on-device encrypt→ ciphertext only uploaded → server can’t unwrap → private key decrypts

Contract: plaintext and the key never leave the machine. Proven byte-for-byte, live against production.

02Governed AI

AI reads what you grant. Nothing more. Ever.

Keep data out of AI by default. Open exactly what you choose, and prove what was read.

An AI agent gets a scoped grant and reads only the classifications inside it. Everything else is skipped, not filtered: the model never receives the bytes, so nothing can leak through a prompt.

In a zero-knowledge capsule, even a granted read runs client-side under the person’s key. NoData never decrypts for a model. Every read is a signed, verifiable receipt.

POST /ai-grants — grant an agent scoped classifications
POST /ai-read — deny-by-default enforcement + receipt
Scanner classifies locally with regex, never an LLM

🤖claims-bot · granted: public, internal

public brochure, claim intake● readable

internal policy notes● readable

confidential medical, financial🔒 denied

attorney_client privileged🔒 denied

Denied tiers are never sent to the model — not redacted after the fact. Deny-by-default: if it wasn’t granted, it doesn’t exist to the AI.

03What’s proven

The guarantees, and how they hold.

✓ verified live against production · ◐ enforced in code

🔒

verified live

🧭

Cross-tenant access is structurally impossibleEvery capsule is pinned to the minting key’s org; there is no code path to another org’s data.

verified live

🔍

The scan never sends data to a modelDeterministic detectors run locally; findings carry a field + type + suggested tier, never a matched value.

verified live

✍️

A human approves every policyThe capsule only suggests a classification; nothing seals without approval, recorded as a content-free receipt.

verified live

🤖

AI reads are deny-by-defaultAn agent reads only the classifications explicitly granted to it; everything else is skipped, not filtered.

in code

🧾

Receipts are tamper-evidentHash-chained (sha256 + chain HMAC), verifiable without NoData in the loop.

in code

04The surface

~14 endpoints. The capsule is the whole API.

Area	Endpoint	State
Onboard	POST /v1/register · /register/resend	✓ live
Capsules	POST·GET /v1/capsules · GET·DEL /v1/capsules/{id}	✓ live
Documents	POST·GET /v1/capsules/{id}/documents (managed + zk ingest)	✓ live
ZK read	GET /v1/capsules/{id}/zk-documents/{docId}	✓ live
AI control	POST /ai-grants · POST /ai-read (deny-by-default)	◐ code
Manage	/members · /revoke · /audit · /embed-token	◐ code
Scanner	/scan/findings · /scan/approve · /scan/execute · install-token	✓ live

05The scanner

Point it at a folder. Capsules fill themselves, content-blind.

regex + checksums · no language model

01 · SCAN

Local & autonomous

Walks the folder on the developer’s machine. Israeli-ID checksum, IBAN, card Luhn, secrets, EN/HE PII, privilege — all deterministic.

02 · SUGGEST

A tier, with a reason

public / internal / confidential / attorney_client per file, grouped one capsule per customer. Values never recorded.

03 · APPROVE

The human decides

The capsule only suggests. You approve each policy, the legal record, as a signed, content-free receipt.

04 · SEAL

Only the approved

Managed, or --zk for on-device encryption. Only ciphertext + the label you approved ever leaves.

Pricing

Access Compute

$0.20 / 1,000 governed access decisions

First 10,000 decisions / moincluded
Human reads (control)flat
Machine / AI reads (compute)metered
Per document sealed$0.05
Capsules · base feefree · $0

The double win

Who buys, and why

It pays for itself the first portal you don’t build, and the first breach you don’t own.

The customer gets a lasting, portable vault they truly own, surviving even if the vendor disappears.
The organization gets a top-secure area for sensitive data and a liability shift: it can prove it never held the keys.
The developer writes almost no crypto. Point the scanner, approve, done.