# Document Metadata & SEO * **Page Title:** Documentation — VerixID * **Description:** Complete guide to VerixID: system mechanics, Record ID, Ownership Key, cryptographic hash functions, and compliance with data protection laws. * **Canonical URL:** `https://verixid.com/en/docs/` * **Application Version:** 1.2 * **Robots Rule:** index, follow * **Language:** en_US --- # Structured Data Schema (JSON-LD) ### TechArticle Entity * **Name:** VerixID Documentation * **URL:** `https://verixid.com/en/docs/` * **Description:** Comprehensive guide and technical reference for the VerixID document verification system. * **Publisher:** VerixID (`https://verixid.com/assets/images/logo.png`) ### Organization Entity * **Legal Name:** PT Verix Identitas Digital * **Brand Name:** VerixID * **URL:** `https://verixid.com` * **Description:** Mathematical digital asset integrity infrastructure providing proof of existence, Certificates of Authenticity, and digital forensics. Designed with a 1-year record TTL. * **Jurisdiction of Incorporation:** Indonesia * **Service Territory:** Global / ID ### SoftwareApplication Entity * **Name:** VerixID * **Category:** SecurityApplication * **Operating System:** Web * **Description:** Mathematics-based digital document integrity verification system. Anonymous, zero-custody, 1-year retention lifecycle. * **Offers:** Free tier for core Submit and Verify operations (IDR 0 / USD 0). --- # Main Content ## Header & Navigation * **Brand:** VerixID — Mathematical Witness for Digital Assets (`https://verixid.com`) * **Primary Navigation:** * [Submit File](/#dropzone) * [Verify Record](/en/verify/) * [COA System](/en/coa/) * [Documentation](/en/docs/) * **Call to Action:** [Register File Now](https://verixid.com) --- ## VerixID Documentation Everything you need to know about how VerixID operates—from core cryptographic hashing principles to regulatory compliance standards. ### User Guides * **For General Users:** Start with our introductory guide at [/en/learn](/en/learn/) * **For Developers & Auditors:** This technical documentation portal (`/en/docs`) --- ## Table of Contents 1. [Overview](#overview) 2. [System Mechanics](#system-mechanics) 3. [Quick Start Guide](#quick-start-guide) 4. [Record ID](#record-id) 5. [Ownership Key](#ownership-key) 6. [Hashes & Cryptography](#hashes--cryptography) 7. [Ledger & Immutability](#ledger--immutability) 8. [Data Retention & TTL](#data-retention--ttl) 9. [Certificate of Authenticity (COA)](#certificate-of-authenticity-coa) 10. [COA vs. Ledger Records](#coa-vs-ledger) 11. [Identity Claims](#identity-claim) 12. [Ownership Verification](#ownership-verification) 13. [Specimen COA](#coa-specimen) 14. [Evidentiary Use in Court](#coa-in-court) 15. [Legal Position](#legal-position) 16. [EIT Law Compliance](#eit-law-compliance) 17. [Data Protection Act Compliance](#data-protection-compliance) --- ## Overview VerixID is a **digital document integrity system** powered by a web-based mathematical ledger. We do not host or store your source files—only their **cryptographic fingerprints** (SHA-256 hashes) are recorded on our ledger alongside authoritative, tamper-proof timestamps. > 💡 **Core Principle:** > Source files never leave your client environment. VerixID processes SHA-256 hashes calculated locally in your browser, guaranteeing absolute privacy. ### Core Services: 1. **Submit** — Commit the mathematical proof of a file's existence to the VerixID ledger to generate a unique Record ID. 2. **Verify** — Confirm whether a Record ID is active on the ledger and validate proof of ownership using an Ownership Key. 3. **Certificate of Authenticity (COA)** — A formal public artifact binding file integrity proof to a verified identity. --- ## System Mechanics VerixID functions as a **mathematical notary**: it attests that a specific document existed at a precise point in time, in an exact state, registered by a holder of a specific key. Nothing more, nothing less. ### Submission Workflow 1. Drag and drop any file into the upload zone. 2. The browser computes the file's **SHA-256 hash** locally; the source file is never transmitted to our servers. 3. The resulting hash digest is sent to the VerixID ledger alongside a UTC timestamp. 4. The system issues a unique **Record ID** and **Ownership Key**. 5. You receive a registration receipt containing both tokens. *Store these securely—they cannot be recovered if lost.* ### Verification Workflow 1. Input a Record ID on the [Verify](/en/verify/) page. 2. The system queries the ledger for matching entries. 3. If matched, registration metadata is displayed. 4. Provide the corresponding Ownership Key to demonstrate mathematical ownership. > ⚠️ **Important:** > Verification attests solely that a file's cryptographic hash is registered on our ledger. It does not certify author identity, document content validity, or legal copyright title. ### Record States * **Active:** Record is valid. Public ownership verification can be executed. * **Not Found:** The Record ID does not exist within the VerixID ledger. --- ## Quick Start Guide Get started with VerixID in 3 simple steps: 1. **Register Your File** Drag and drop your file on the homepage. Computation is completed entirely client-side—only the cryptographic hash is transmitted. 2. **Secure Your Record ID & Ownership Key** Download your registration receipt upon completion. Save both credentials securely. **The Ownership Key cannot be recovered** if lost. 3. **Verify at Any Time** Anyone can verify a Record ID on the public verification page without creating an account. Append the Ownership Key to perform an ownership check. > 🎉 **Pricing Notice:** > Standard Submit and Verify functions are **free forever**. Payment is required only when requesting a formal Certificate of Authenticity (COA). Learn more on the [COA Overview Page](/en/coa/). --- ## Record ID A Record ID is a **unique identifier** issued by VerixID for each ledger entry. *Example:* `vx202606cc1f5dd1` — an 18-character alphanumeric string. ### What Does a Record ID Represent? A Record ID serves as a ledger registration index. Conceptually, it functions like a shipping tracking number rather than the contents of the package itself. > 🔍 **Accessibility Note:** > Record IDs are public tokens that can be shared freely with counterparties for audit purposes. The **Ownership Key** must remain confidential. --- ## Ownership Key An Ownership Key is a **unique cryptographic token** generated at the time of file registration. It forms part of the protocol used to prove that a Record ID was generated under authentic conditions at a specific timestamp. ### Technical Characteristics * **Format:** A unique cryptographic string generated deterministically by the system. * **Confidentiality:** Highly sensitive secret token issued exclusively during registration. Raw keys are never stored on our servers. * **Recoverability:** **Non-recoverable.** If lost, an Ownership Key cannot be regenerated. VerixID stores only salted hash representations for validation. ### How the Ownership Key Operates 1. During submission, the system generates an Ownership Key derived from the combination of the *Record ID* and *File Hash*. 2. The key is hashed and bound to the ledger entry, secured by server digital signatures (Ed25519). This creates an immutable link between the file digest, registration timestamp, and proof of control. 3. During verification, the presented Ownership Key is evaluated against ledger entries to confirm that all payload parameters remain intact and untampered. > ⚠️ **Important:** > Losing an Ownership Key forfeits your ability to demonstrate cryptographic ownership of the Record ID. While the ledger entry remains intact, ownership verification cannot be executed without it. Store Ownership Keys with the same security as critical access keys. ### Ownership Key vs. Passwords An Ownership Key is not an account password and is never used for authentication or logging in. It is never transmitted as a plain credential, but evaluated as part of a mathematical proof. VerixID never possesses or stores raw Ownership Keys. --- ## Hashes & Cryptography A hash is a **mathematical fingerprint** of a data payload. Cryptographic hash functions like SHA-256 convert arbitrary file content into a unique, fixed-length 64-character hexadecimal string. ### Key Cryptographic Properties * **Deterministic:** The exact same file payload will always produce the identical hash digest. * **Avalanche Effect:** Modifying a single bit within a file produces an entirely unpredictable and drastically different hash digest. * **One-Way Function:** It is computationally infeasible to reconstruct source file payloads from a hash string. * **Collision Resistance:** It is practically impossible to find two distinct files that yield the same hash digest. ### Impact of Payload Alterations Two text files differing by only a single final digit yield completely divergent hash outputs: ```text File A: "Lease Contract No. 001" SHA-256: 3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c File B: "Lease Contract No. 002" SHA-256: 9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a