01 / TRACE
Access with defined permissions
Selected documents, a specified recipient and a defined access period. We are developing permission granting and revocation mechanisms that can be adapted to application-specific roles.
All projects
DOCUMENTS / DATA / ACCESS CONTROL
Rewinit TRACE
Documentation and client data under control.
We are developing a shared layer for access control, activity records and document verification in applications handling client data. TRACE is intended to support selective sharing, access expiry and document integrity checks.
Prototype developmentAs of 26 October 2026
Explore TRACE in practice.REWINIT TRACE / R&D
The right document reaches the right person. Its history stays verifiable.
Documents, client data and permissions connect many everyday workflows. We are developing TRACE as technology for different applications, from Notes Lekarza to Notes Prawnika. Each use case requires access rules and document workflows tailored to its context.
02 / TRACE
An activity history to revisit
Publication, read and sharing records help teams trace document activity. Versioning and cryptographic proofs support integrity checks for a specific document version.
03 / TRACE
Shared technology, different uses
Notes Lekarza: patient documentation. Notes Prawnika: case files and client documents. These are intended applications for TRACE; integrations with these products remain to be developed and verified.
Documents off-chain. Proofs on the ledger.
In the TRACE architecture, documents are held in encrypted storage or remain in their source repository. Aggregated cryptographic commitments are published to the blockchain. Document contents, client data and detailed activity records remain off-chain.
As of 26 October 2026
Prototype development
The prototype covers medical-documentation and customer–store scenarios. Local verification covered source-repository document exchange, access revocation, data isolation and commitments recorded on Hyperledger Fabric. The public demo uses prepared data and simulated browser operations. Further use cases and application integrations are next steps.
Revoking access blocks subsequent reads through the system but does not remove copies downloaded earlier. An integrity proof concerns consistency with a recorded version, rather than the truth of its contents.
We welcome conversations with partners building software for professionals about a pilot: document workflows, user roles, repository integration and verification of the sharing process.
Discuss TRACEExplore the idea behind TRACE.
Selected documents, defined access and a history to revisit. Discover the direction of TRACE in a short animation.
What are we developing in TRACE?
Prototype functionality has been verified locally for medical and commerce scenarios. The public demo presents the concepts using prepared data; real product integrations remain a next step.
Documents and versions
Upload PDF, JPG and PNG files and publish source documents. Each version has its own identifier and cryptographic digest, linking an operation to a specific file.
A defined recipient and expiry
A grant covers specified document versions and a specific recipient. New documents require a separate decision. Access has an expiry and can be revoked.
Document activity history
Publication, reads, sharing and access revocation are recorded in an activity history. Authorised users can review activity within the relevant profile.
Roles and representation
The medical prototype distinguishes patients, clinicians, providers and operators, and supports representation verification. A separate commerce profile covers customers and stores, with data access separated between the two scenarios. Further sectors require tailored rules.
Integrity verification
An exported proof package supports checking a specific document against its recorded commitment. The blockchain holds aggregated commitments; detailed audit records remain in the application.
Repositories and data exchange
The code includes encrypted file storage, a source-repository gateway and selected FHIR operations for the medical scenario. Connections to real systems require agreed integration and acceptance.
Explore TRACE in practice.
Try the TRACE interactive presentation: prepared documents, roles, sharing scope and access revocation. It covers medical and customer–store scenarios with synthetic data.
- Select a prepared document and version.
- Switch roles and review the scope of access.
- Try time-limited sharing and permission revocation.
- Explore the activity history and a sample integrity proof.
TRACE / DEMO
Documentation and client data under control.
The presentation uses prepared data and simulates permission changes in the browser. Sample proofs originate from a local Fabric network. The demo does not submit new network transactions or accept document uploads.
From prototype to application deployment.
- Developed
Prototype core
Portal, permissions, versioning, activity records and cryptographic commitments.
- Publicly available
Interactive demo
An interactive presentation with prepared data: roles, document versions, sharing, revocation and sample proofs.
- Next phase
A shared TRACE layer
Adapt document models, roles and access rules for further uses and agree integration contracts.
- Development direction
Notes Lekarza and Notes Prawnika
Verify product scenarios and prepare a pilot. Integrations with these applications are not currently presented as complete.
We welcome conversations with partners building software for professionals about a pilot: document workflows, user roles, repository integration and verification of the sharing process.
Discuss TRACE