Evidence by design.
Not by declaration.
V-PROOF is not added on top of their systems: it is integrated as an infrastructure layer underneath. It is connected to existing data flows, with evidence that a third party can verify.
They are not features. They are design constraints.
They make evidence verifiable regardless of who generates it and who holds it.
Evidence arises within the governed flow.
The footprint is generated at a specific point in the flow, linked to the context, the responsible party, and the asset that account for it, and is calculated based on the original data, before any processing.
The evidence can be checked later.
The cryptographic registry allows the integrity of the evidence to be verified regardless of who is in possession of it. The registry is queried using a reference or QR code, without accessing the organization’s internal systems. To verify a specific file, its digital fingerprint is calculated and compared with the one on record.
The V-Seal® makes it portable.
Sealed events become verifiable assets, complete with a human-to-AI ratio, approver identity, regulatory context, and verdict. A third party can verify them without accessing internal systems.
Six steps, from the AI that exists to the proof that gets verified.
We distinguish between what V-PROOF does today and what is part of its evolution, so that no one buys a roadmap as if it were a product.
- 01 · Evolution Discover Detect AI being used without registration
- 02 · Today Govern Inventory, risks, policies and owners
- 03 · Today Control Controls in V-PROOF Evolution flows : gateway and MCP for external tools
- 04 · Today Evidence Record with context, owner and fingerprint
- 05 · Today Test V-Seal of documents, commits and models
- 06 · Today Verify Public portal, without an account or access to your systems
Available today Evolution
From controlled flow to verifiable evidence.
The pipeline captures, calculates the fingerprint, seals, and records the cryptographic evidence. The sealing process uses cryptographic fingerprints: only the fingerprint of your documents is sent.
The V-Seal®: evidence asset by asset.
The auditor verifies the integrity of the asset and the context linked to it (declared authorship, date and regulatory framework) without accessing internal data. A QR code unlocks the verifiable evidence.
Cryptographic fingerprint of the original asset.
Time reference associated with cryptographic evidence.
Human-to-AI ratio and approver identity.
Regulatory framework and audit findings.
Illustrative example.
Maximum penalty for failing to comply with high-risk obligations, or 3 percent of total revenue.
Only the fingerprint is transmitted outside your organization: V-PROOF receives the fingerprint and the compliance metadata, not the content.
Each sealed asset records which part is human work and which part is AI-assisted, and who validated it.
Designed from the very beginning with European standards in mind.
Compliance is not an afterthought. This is how every architectural decision aligns with the requirements of the EU's most stringent frameworks.
For high-risk systems, Article 9 requires risk management; Article 12 requires event logs during operation; and Article 14 requires effective human oversight. V-PROOF generates evidence for each one, verifiable by a third party without needing to access internal systems.
Clause 7.5 requires control over documented information. V-Seal® provides verifiable integrity— asset by asset: a technical solution, not a mere claim.
It strengthens the traceability of the ICT risk management framework (Art. 5) and of the reliance on critical third-party providers (Art. 28): incidents, response decisions, critical changes, and controls.
V-PROOF is designed to operate in conjunction with the trusted services of the eIDAS framework. Article 41 establishes that an electronic time stamp cannot be denied legal effect on the grounds that it is electronic; the presumption of accuracy is reserved for qualified time stamps issued by a qualified provider.
The European Data Protection Supervisor published its checklist on human oversight. V-PROOF generates evidence of that oversight, including who, when and context, which can be verified by a third party.
The Civil Procedure Law admits electronic media as evidence (arts. 299, 326 and 384) and its assessment is the responsibility of the judge. V-PROOF strengthens the chain of evidence: it allows verification of integrity, chronology and correspondence with the recorded cryptographic fingerprint, which facilitates its contribution and, where applicable, the expert report.
What an architect asks before saying yes.
Does V-PROOF have access to my data?
Not in the sealing. V-PROOF works with the document's cryptographic fingerprint and compliance metadata; the original remains within its perimeter. Modules that use a language model do so with the provider and account configured by your organization, and a local filter reviews each message before it leaves.
What is V-Seal® and what does it contain?
V-PROOF's core cryptographic seal: the original asset’s cryptographic fingerprint, a timestamp associated with the cryptographic record, the human-to-AI ratio, the approver’s identity, the regulatory context, and the audit verdict. A third party can verify this without accessing internal systems. The specific architecture depends on the type of evidence and the workflow.
How does it fit into my architecture?
With an API-first architecture that integrates with existing systems without replacing them. The scope of each integration (events, connectors, and metadata) is defined during the assessment, and some deployments may require minor process changes. The platform is in production with clients in industrial manufacturing and legal consulting.
How can a third party verify the evidence?
The evidence includes a cryptographic fingerprint associated with the asset and its context. The record is accessed via a reference or QR code. To verify that a specific file matches, its fingerprint is calculated and compared with the one on record.
Can V-PROOF evidence be presented to regulators?
This is verifiable technical evidence, not a declaration of compliance. A regulator or auditor can independently verify that the document has not been altered since it was sealed. It is intended to support registration, documentation, and monitoring obligations; its assessment in a specific procedure is determined on a case-by-case basis by the competent authority.
Assess your evidence architecture.
Executive session with a customized roadmap. No long-term commitment and no changes to what’s already working. Deliverables included.
The examples describe potential uses of technical evidence. The applicability of each standard depends on the product, its intended use, the entity, and the legal framework. V-PROOF is not a substitute for legal assessment, industry certification, or the effective implementation of controls.