How does ROOTKey know what changed in a file?
Short answer
Every version of a file, table or record gets a unique fingerprint, sealed in an independent public registry with a timestamp. ROOTKey continuously compares your data with that sealed record, so any change is caught and explained: what, who, when and where. It then restores only what was altered to the last version proven valid, cryptographically verified.
- Fingerprint
- SHA-256for every version, with a timestamp
- Detection
- Continuouswhat, who, when and where
- Scope
- File · table · rowonly what was altered
- RTO
- < 4 hoursContractual on Enterprise, a target on platform plans
Why a hash alone is not enough
A photo, a date of birth, an IBAN. Today a forgery is a handful of edited pixels or a single changed cell.
Comparing hashes answers one question: did it change? Not what, who, when or where - and not which version to trust.
The three layers of the technology
The ROOTKey platform symbol is three stacked layers: each one is a component of the technology, from the top down.
Layer 1
Independent public registry
Every version of every file, table or record gets a unique fingerprint, sealed in an independent public registry with a timestamp.
Layer 2
Cryptography
The cryptography inside ROOTKey’s systems and in the independent public registry, linking every version to its proof. A SHA-256 fingerprint for every version, every critical workflow in its own dedicated, encrypted vault, and cryptographically anchored records that prove exactly what happened, when and by whom.
Layer 3
Pixel- and cell-level comparison
Whatever the file, ROOTKey compares it with its sealed original and shows only what was altered. Today a forgery is a handful of edited pixels or a single changed cell.
1. Anchor: a fingerprint for every version
Every version of every file, table or record gets a unique fingerprint, sealed in an independent public registry with a timestamp.
- Fingerprint
- SHA-256
- Record
- Permanent digital record
- Status
- ✓ Sealed in the independent public registry
2. Detect: what changed, who, when and where
ROOTKey continuously compares your data with the sealed record. Any change is caught and explained: what, who, when and where.
- Who
- User, account or integration
- What
- Row, cell or field · before and after
- When
- Sealed date and time
- Where
- System · repository · table
The altered parts light up against the sealed original - with who changed them, when and where.
3. Recover: only what was altered, proven clean
Restore the last version proven valid, down to one file or one row - not a backup that may be compromised.
Only what was altered returns to the sealed original, cryptographically verified.
Every backup is independently verified for integrity before any recovery operation begins.
One-click recovery restores the exact state of your data, from any snapshot, in under 4 hours: contractual on the Enterprise tiers, a target on platform plans.
Proof anyone can check
Cryptographically anchored records prove exactly what happened, when and by whom - providing verifiable accountability and regulator-ready audit reports.
Every critical action produces an independent proof that external auditors can verify without access to the original data.
Immutable verification
Every document is cryptographically matched against immutable trust records.
Issuer authenticity
Verify organisational ownership and digital provenance.
Enterprise-grade integrity
Built for NIS2, DORA and institutional compliance workflows.
To check a document you received, use the public verification portal together with its document identifier. The file is sent to the ROOTKey validation service and compared with its registered record.
Any file, one kind of proof
PDF, images, Word, Excel, PowerPoint, tables and databases: whatever the file, ROOTKey compares it with its sealed original and shows only what was altered.
Frequently asked questions
Is ROOTKey a backup solution?
No. Backup restores systems. ROOTKey proves whether the restored data can be trusted - they are complementary, not competing.
Do you store our data?
On the SaaS platform, ROOTKey hosts your data in the EU. With a private cloud or on-premise deployment, your data stays wherever you decide. For recovery, encrypted snapshots are stored according to your configuration.
How does ROOTKey support GDPR Article 5 data integrity?
GDPR Article 5(1)(f) requires personal data to be processed with appropriate security. ROOTKey's cryptographic hash anchoring proves whether personal data has been modified or altered after processing.