Employees
Opening documents, reading sensitive information and sharing files.
NoData · Platform
The whole story: the connection, the decision before disclosure, control over what is disclosed, and a cryptographic receipt before release.
IThe problem and the connection
02 · The problem
Every time someone or something requests information, a transaction takes place. Employees, applications, partners, customers and AI agents start them all day. But control is fragmented.
The problem is not only who has access. It is whether every information transaction is permitted, constrained, enforced and provable before it happens.
03 · The connection
Every request has two sides: someone asking for information, and a source holding it. The request creates a connection between them, and the connection is where the transaction happens. Control has to move to the transaction itself.
On supported paths and deployments, the connection works without exposing the protected information, without taking control of the keys, and with cryptographic proof of every protected release.Holds on the paths and deployments where the architecture guarantees it.
IIThe mechanism
04 · The category
Control is no longer just about who can access information. It is about governing every transaction through which information moves.
Who can access this resource?
Can this operation happen, with this information, by this identity, through this channel, under these conditions, right now?
A transaction is not authorized just because an identity is trusted or a connection exists. NoData evaluates the request against the policy that applies and enforces the permitted outcome at the protected operation.
The policy determines what the transaction can do.
05 · The NoData principle
Information can be stored, transferred or held without granting the ability to read it. NoData separates holding encrypted information from the ability to disclose it. Every request is computed again. The key is released per request, or withheld. The decision is enforced at the key, before protected information becomes readable.
Information stays sealed. Permission is computed. Disclosure is controlled.
06 · Control over what is disclosed
One document can open differently for different people. Each part is released only to whoever the policy allows, and the rest stays sealed. Nobody has to receive the original to work with the part they need.
Working since February 2026 in Seal Studio, the document editor, and the scanner that finds the sensitive parts.
07 · Every transaction surface
Opening documents, reading sensitive information and sharing files.
Requesting records, reading documents and running approved operations.
Retrieving data, calling APIs and reaching protected resources.
Reading records and exposing only the permitted fields.
Receiving information and acting across organizational boundaries.
Reaching the information and services your organization provides.
Different identities. Different channels. Different operations. One governing mechanism. One policy framework. One evidence architecture.
IIIThe products
08 · The platform
Each cube shows what goes in and what you get. Open one only if you want the details.
09 · How it works
Someone or something asks for information or an action: a person, an application, an organization or an AI agent.
A connection forms between the requester and the source: a governed link inside one organization, Mycelium between independent parties.
NoData evaluates identity, device, context, the action and the policy of each side that applies.
A signed receipt of the decision is written before protected information is released. No receipt, no release.
Only once the receipt is written is the decision enforced, where information could become exposed. For encrypted information, at the key.
Released in full, released in part, or withheld.
Records what happened.
Decide who may access.
Computes and enforces what this transaction may do, before protected information is released, and proves the release.
Not monitoring after the transaction. Governing before disclosure.
10 · Mycelium in action
Demonstration · sample document
The sender decides what may leave. The receiver decides what it is willing to accept. The stricter policy wins.
1 crossed6 withheld
The stricter policy wins.
Runs in your browser on a sample document. Nothing is uploaded.
A connection is not open access. Revoking a connection blocks future requests. It does not delete or retract information that was already disclosed.
IVThe proof
11 · The evidence map
Every protected release writes a receipt before disclosure. The receipts add up to an evidence map of the activity that passes through NoData, so an investigation of those transactions starts from evidence, not from reconstruction.
Evidence is part of enforcement.
12 · Independent cryptographic proof
Ordinary logs depend on the system that wrote and stores them. NoData writes cryptographic receipts that can be checked on their own.
A signed receipt for every protected release.
Each receipt is linked to the one before it.
Check a receipt with pinned public keys, without calling NoData.
Hourly batches anchored in Bitcoin (OpenTimestamps), Sigstore Rekor and an external witness.
Production, measured 13 Nov 2026; the first three over the last 30 days. Anchoring runs in hourly batches after release; the signed receipt itself is written before the protected release. Anchoring is not available on an air-gapped install.
VDeployment and integration
13 · Deployment
Start on managed infrastructure.
Run inside your private cloud environment.
Database, control plane, gateway and information inside your infrastructure. Keys generated and kept in your own Key Vault.
The licence is a signed file verified locally, with no call home. The Capsule agent keeps working offline and sends its queued work when the connection returns.
14 · Beyond the perimeter
Information moves between employees, suppliers, customers, partners and outside systems. Protected information stays governed through managed transactions beyond the network perimeter. The policy stays attached to the information.
15 · Digital vault
On a normal day the holder alone opens it. Changing the holder needs the holder and an admin together. Recovery needs the organization’s recovery words, an admin who is not the requester, and a waiting window the holder can see. Two admins together still cannot become the holder.
16 · Connect any system
What each connection can do depends on the integration and the deployment path. All integrations →
VIAdoption
17 · Every scale
Start with one Capsule. Grow without changing the processor underneath.
18 · For developers
Build around the NoData processor: evaluate transactions, define permitted capabilities, enforce before protected release, govern AI agents, and get signed receipts you can verify yourself.
const decision = await nodata.authorize({ subject: "agent://analyst", asset: "finance/forecasts", action: "read" }); if (decision.verdict === "allow") { // Continue with authorized access }
Illustrative SDK and MCP connections. A short technical integration is not the same as complete enterprise onboarding; deployment, policy design and key-management requirements vary by environment.
19 · Early Access
NoData is measured like infrastructure: by decisions. Grants, policy checks and revocation are on no meter. During Early Access, every plan starts with a conversation.
The processor itself, with a monthly decision allocation.
Policies, people, enforcement and evidence. Microsoft 365 and Google Workspace included.
Institutional governance, a custom decision allocation, sovereign deployment on your infrastructure and keys.
20 · Security & trust
Trust should be demonstrated, not requested.
Your employees request information. Your applications retrieve it. Your partners exchange it. Your AI agents use it. The question is whether each transaction is governed before information is exposed.
NoData doesn’t just control who gets access. It governs what information is released, under what conditions, and proves it before release.
NoData governs the transaction.Mycelium connects the participants.
Your data. Your control. Your proof.