cAuth Evidence Assistant

Smartly scan web resources, verify cAuth Evidence, seal files, manage identity and open the existing complaint workflow: cAuth – Digital Evidence Assistant for Your Browser Verify. Seal. Trust. cAuth is a browser extension designed to help users discover, inspect, create, manage, and monitor digital evidence through a unified interface. Instead of opening multiple tools, manually recording hashes, uploading files to different services, or constantly switching between systems, cAuth brings key evidence workflow steps into a single Side Panel inside the browser. cAuth is a professional tool for individuals and organizations to verify the integrity of digital documents, web resources, and digital data. Pages – Monitor Evidence and Claims Pages is the central monitoring area of cAuth. From here, users can search and review public claims, monitor evidence status, and receive real-time updates when information changes. What can you do? Search for Evidence by name or related information. Filter results using advanced filters. Monitor the latest claims. Receive real-time updates without constantly refreshing the page. Open a claim to review its status and related information. View recorded ownership information available at the time of execution. Track statuses such as Sealed, OTS, and other verification-related information. Access or initiate the complaint workflow when an issue requires review. Why use it? As the number of evidence records grows, relying on manual visual tracking or scattered files can easily lead to confusion. cAuth provides a centralized place to: Find → Filter → View → Verify → Act Scan – Discover Website Resources and APIs The Scan section helps users analyze the current website to identify technical resources and data that may be relevant to verification workflows. cAuth can help identify different resource types, including: API endpoints REST APIs GraphQL JSON Fetch/XHR External resources Previously discovered or scanned resources Failed scans that require further review Resources are organized into groups so users can quickly understand their status: API / Scanned / External / Failed Why use it? A modern website can load dozens or even hundreds of different resources. When everything is checked manually, it can be difficult to determine where data comes from, distinguish internal resources from external ones, identify which APIs are actively used, or repeat the inspection process consistently. cAuth turns this into a structured, visual, and faster workflow. Evidence – Centralized Evidence Management The Evidence section is where users review and manage Evidence recorded by cAuth. Each Evidence record may contain important information such as: File or resource name Evidence ID SHA-256 Registration time Status OTS PAdES Identity Key Related ownership information Additional verification data Long hash values are displayed in a compact format to keep the interface clean, while the complete value remains available when needed. Why use it? When working with digital documents, one of the most common questions is: “Is this file still identical to the original file?” A hash provides a technical fingerprint that can be used to compare changes in data. cAuth helps users keep Evidence records in one place instead of manually managing disconnected records. Seal File – Inspect and Create Evidence The Seal File section is designed for local document and data workflows. Users can select a file for cAuth to analyze and help identify its content type automatically. The system can distinguish between content such as: Original file OTS PDF record/certificate Evidence package Related files cAuth can generate and verify the SHA-256 hash of a file before the sealing workflow begins. Typical workflow: Select file → Analyze → Identify file type → Generate hash → Verify → Seal & Create Evidence During the process, cAuth may display ownership information and Identity Key information associated with the execution context. Users can also access the complaint workflow when an issue related to Evidence is discovered. Why use it? Instead of simply storing a file on a computer and remembering when it was created, users can build a structured evidence record that makes later comparison and verification seamless. Identity & eKYC – Identity Key The Identity & eKYC section is dedicated to legal identity information and the Identity Key. This area is intentionally separate from the Public Profile. Identity Key includes: Legal full name National ID / Passport Date of birth Date of issue Place of issue Phone number Address The Identity Key is used in workflows that require Evidence to be linked to a verified identity. When legal information changes, cAuth follows the process: Re-verify → Key Rotation rather than simply editing a field in an existing Identity Key. Why use it? For evidence workflows, it is important to clearly distinguish between Legal identity and Public-facing information. Identity Key allows cAuth to maintain these two layers separately, so users can manage legal identity information without exposing all of it in their public profile. Public Profile – Instant Updates The Public Profile contains only information intended for display, such as: Display name Organization Role Introduction Users can update and save these details immediately without going through Re-verify & Key Rotation. Why use it? Legal identity information usually changes infrequently, while public profile information may change more often. Separating the two allows users to update public profile details quickly while keeping legal identity data secure in the Identity Key. Re-verify & Key Rotation When Identity information needs to change, cAuth provides a dedicated Re-verify & Key Rotation workflow. The purpose is to create a new Identity Key that reflects the newly verified identity data instead of modifying the legal data of an existing active Identity Key. This is particularly us…