CREATORSEAL™ Glossary

A cryptographic hash function that creates a unique fingerprint of a file. If the file changes, the fingerprint changes. SHA-256 is widely used across digital verification systems and provides strong integrity checking.

A cryptographic hash function similar to SHA-256, but with a longer output and a higher security margin. CREATORSEAL™ uses SHA-384 as part of its stronger long-term proof direction because it provides more room for future durability while serving the same core purpose: creating a unique fingerprint of a file.

Both SHA-256 and SHA-384 are cryptographic hash functions used to create a unique fingerprint of a file. SHA-256 is widely used and strongly established. SHA-384 produces a longer hash and offers a higher security margin. In practical terms, both can verify whether a file matches its recorded fingerprint. The difference is mostly about long-term strength and durability. CREATORSEAL™'s direction favors SHA-384 where stronger future-facing proof is preferred.

A fixed-length string of characters generated from a file's contents using a mathematical function. A hash acts as a digital fingerprint: unique to the file, impossible to reverse into the original content, and different if even a single byte changes.

A unique digital signature generated from the exact contents of a file using a hash function. If the file changes even slightly, the fingerprint changes. This is the foundation of how CREATORSEAL™ connects a proof record to a specific version of a file.

An internet standard that defines how trusted timestamps are created and verified. RFC 3161 timestamps are issued by recognized Timestamp Authorities and are widely accepted as credible evidence that data existed at a specific point in time.

An extension to the RFC 3161 timestamp standard that adds support for using stronger hash algorithms in timestamp tokens. RFC 5816 helps ensure that timestamp proof remains credible as cryptographic standards evolve.

An internet standard that defines the structure and maintenance of evidence records for long-term digital evidence preservation. RFC 4998 provides a framework for keeping proof verifiable even as cryptographic algorithms age.

The sequence of digital certificates linking a timestamp token back to a trusted root authority. A complete certificate chain helps establish that the timestamp was issued by a recognized and trustworthy source.

Information confirming that the certificates used in a proof record had not been revoked at the time the timestamp was issued. Including revocation data strengthens long-term verification by proving the certificates were valid when used.

The act of creating a proof record for a file using CREATORSEAL™. When you seal a file, a cryptographic fingerprint is generated locally and linked to a timestamp, a Seal ID, and proof metadata — without uploading the file itself.

A unique identifier assigned to each proof record created by CREATORSEAL™. The Seal ID connects the cryptographic fingerprint, timestamp, and proof metadata into a single verifiable record.

A documented, verifiable record showing that a specific file existed in a specific form at a specific moment in time. CREATORSEAL™ is built as proof-of-record infrastructure — not a copyright office, not a legal service, but a system designed to help creators establish documented timelines.

A human-readable summary issued after sealing that references the file fingerprint, Seal ID, timestamp, and related metadata. The receipt is not the proof itself — it summarizes the underlying proof-of-record. The evidence bundle contains the real machine-verifiable proof.

The machine-verifiable proof material behind a CREATORSEAL™ seal. An evidence bundle contains the cryptographic data, timestamp tokens, certificate chains, and verification metadata needed for independent verification. This is the real proof — not the receipt.

An optional branded reference copy of the original file, which may include a Seal ID, short hash preview, and verification URL. The sealed display copy is a presentation artifact — the canonical proof applies to the original file that was hashed and sealed.

A proof record composed of cryptographic fingerprints, timestamps, and supporting metadata stored in a structured, tamper-evident format. Structured proof records provide durability because the components can be independently verified and are difficult to alter after the fact.

A structured record designed to preserve the verifiability of digital evidence over extended time periods. Evidence records may include hash renewal data and updated cryptographic references to ensure proof remains checkable as standards evolve.

A linked series of proof records that together document the lifecycle of a creative project. Each sealed version adds a new link, creating a stronger cumulative record than any single timestamp alone.

The documented record of how a creative work developed over time. By sealing multiple versions, creators can build a creation history that shows the evolution of their work — often more persuasive than a single proof point.

A sequence of sealed records showing different versions of the same project. Version history helps demonstrate that a work was developed progressively, supporting claims of original authorship through documented creative lineage.

The practice of creating a proof record before sharing, sending, or publishing a file. CREATORSEAL™ is designed for this moment — helping creators document their work before it leaves their hands.

A verifiable sequence of proof records showing when specific versions of a file existed. A documented timeline can help establish priority and support claims about who created what, and when.

A recorded moment in time expressed in Coordinated Universal Time. CREATORSEAL™ timestamps document when a file's fingerprint was sealed, providing a time-anchored proof point that is independent of local time zones.

The process of checking whether a file matches a previously recorded proof record. Verification confirms that the file fingerprint, timestamp, and Seal ID align — supporting the claim that the file has not been altered since it was sealed.

The ability to verify a proof record without relying solely on CREATORSEAL™'s systems. Because the proof is based on open cryptographic standards and trusted timestamps, it can be examined by third parties.

The process of generating a file's cryptographic fingerprint directly in your browser, on your device. The file itself is never uploaded to CREATORSEAL™'s servers — only the resulting hash is used to create the proof record.

The approach of performing all file fingerprinting and hash generation within your web browser rather than on a remote server. This means your file never leaves your device during the sealing process — only the resulting fingerprint is transmitted.

An architectural principle meaning that privacy protections are built into the system from the ground up, not added afterward. CREATORSEAL™ operates on this principle: it does not need your file contents to create a proof record.

The ability to verify a proof record years or decades after it was created, even if original certificates expire or issuing authorities change. CREATORSEAL™'s architecture is designed to support proof that remains meaningful over time.

The planned process of updating cryptographic references within a proof record before the underlying algorithms or certificates lose their strength. Scheduled renewal is part of responsible long-term proof maintenance.

The creator name or identity associated with a CREATORSEAL™ proof record. This is the name that appears on the Receipt of Provenance Record and connects the sealed file to a specific person or entity.

CREATORSEAL™ currently supports PNG, JPG, WEBP, SVG, and PDF. These are the file types creators most often need to protect before sharing. The fingerprinting process works locally in your browser for all supported formats.