Coming soon

This workflow is in development and is not available yet. It is a preview of a planned application built on the IP Vault evidence engine.

Register your interest
For AI governance, compliance and model teams

Show what your model saw, and who was in the loop.

Create a time-stamped record of datasets, prompts, human oversight and training checkpoints without uploading model weights or sensitive training data.

Training-cutoff snapshots
Prompt, seed and HITL records
TDM reservation evidence
No model weights uploaded

Evidence record

AI Governance

Coming soon
Record status Sealed and timestamped
Time source eIDAS qualified + Bitcoin
File storage Your cloud or local drive
Version Linked to prior certificate
Verification Shareable public record
Included in the archive
Declaration Manifest .tsr .ots ZIP

The problem

What makes this hard to prove today

Most evidence problems are not about whether a file exists. They are about whether you can show what it was, when it existed and that it has not changed since.

Training data changes over time

Proving the exact corpus state at training time is hard after the fact, especially when datasets are updated in place.

TDM opt-outs need evidence

Organisations need to show they respected machine-readable reservations in place at the relevant time.

Human oversight must be documented

US and UK authorship rules and the EU AI Act require a record of human involvement, not just an output.

Synthetic media needs authentication

Deepfakes make authentic corporate media and executive communications harder to trust.

What you get

An evidence pack you can actually use

IP Vault produces the sealed record. Your team keeps control of the files and decides who receives the verification link.

01

A dataset or checkpoint seal

Hash dataset versions, DVC or lakeFS checksums, or model weight files without uploading them.

02

A prompt and curation record

Capture prompts, model versions, seeds and human review steps in the declaration.

03

A TDM reservation snapshot

Record the machine-readable signals in place at the training cutoff.

04

An oversight record

Document who reviewed what, when, and why a version changed.

How it works

Three steps, no new storage platform

1

Define the record

Choose the dataset snapshot, checkpoint, prompt log or oversight event that needs to be fixed in time.

2

Seal the snapshot

The digest and declaration are timestamped externally and anchored to Bitcoin.

3

Share the evidence

Give auditors, counsel or partners a verification record without exposing the underlying model or data.

Regulatory context

Built for AI record-keeping and provenance

IP Vault creates evidentiary records. It does not certify AI Act conformity, audit a model or provide legal advice.

EU AI Act, Articles 12, 14, 50 and 53
EU Copyright Directive 2019/790, Article 4
US Copyright Office AI registration guidance
UK CDPA 1988, s.9(3)
NIST AI Risk Management Framework 1.0

Who it is for

Built for teams that have to show their work

Talk to us about your workflow →
Chief AI officers AI governance and compliance counsel Enterprise marketing and content teams GPAI providers Fine-tuning and RAG teams AI insurers

Common questions

The short answers

Do you need our model weights?
No. Hash the weight files or dataset locally and seal the digest and manifest.
Can we prove a TDM opt-out was in place?
You can seal a snapshot of the signals and the date they were recorded.
Does this make us AI Act compliant?
No. It supports record-keeping and oversight evidence; compliance depends on your full governance programme.
Can we record human review?
Yes. The declaration can capture reviewer identity, action, timestamp and reason for change.

Create the record now, decide who sees it later

Start with a single protection run. Keep the archive, share the verification link, and add revisions when the work changes.