Definitions
Product glossary
Plain-English definitions for sealing, verification, Trust Badge, Document Requests, and related terms — aligned with what Opcilo actually checks today.
- Document sealing
Fingerprinting a file and storing it with a verification code and link so anyone can check the sealed version later.
- Document integrity
The sealed file bytes match the record Opcilo stored when the document was sealed. Shown on public verify as Document integrity.
- Tamper-evident
Changes after sealing can be detected by comparing the file to the sealed record. It does not mean the file cannot be edited offline.
Does not mean: Not the same as making a file uneditable or proving every statement inside is true.
- Verification code
A short public code (typically eight characters) that identifies a sealed document for lookup on Opcilo verify pages.
- Verification link
A URL that opens the public verify experience for a sealed document, usually embedding the verification code.
- Issuer verification
The issuer workspace completed business verification — Know Your Business (KYB), a check that the organization behind the workspace is a real business. Email-verified accounts are not Issuer Verified.
- KYB (Know Your Business)
Know Your Business: Opcilo’s business-verification process for an issuing organization. Completing KYB is what unlocks the Issuer Verified label and Trust Badge. It is not person identity verification (that remains Not checked).
- Trust Badge
Visual and public-profile signal that the issuer is Issuer Verified after business verification. Not a verdict on document truth.
- Chain of custody
Issuer-side activity about a sealed document (for example sent, opened, downloaded) available in Pro engagement views — not a court certification by itself.
Does not mean: Not a public ledger of every verification event by every viewer.
- Digital signature
A cryptographic signature over a document or message, typically from an e-sign or PKI workflow. Opcilo may preserve a signed PDF without validating that signature.
Does not mean: Opcilo does not currently report Signature Verified on public verify.
- Cryptographic hash
A fixed-length fingerprint of file bytes. Matching hashes support document integrity checks.
- SHA-256
The hash algorithm Opcilo uses to fingerprint sealed document bytes for integrity verification.
- Document provenance
Evidence about origin and custody of a sealed document — for example who sealed it and issuer verification status — not proof that every claim in the file is true.
- Document Request
Structured collection: create a checklist, share a secure link, receive submissions, review items, send a response, resubmit rejected items, and reach final confirmation.
- Request-item Verified
Requester marked the item accepted. This is requester review — not seal Document integrity and not person Identity Verified.
Does not mean: Document Request item Verified means the requester accepted the upload. It does not mean Opcilo sealed the file or checked the uploader’s identity.
- Needs resubmit
After the requester sends a review response, rejected items reopen so the recipient can replace only those files.
- Final confirmation
All required items are Verified (requester review) and the request is completed.
- Business Inbox
Authenticated workspace inbox for sealed documents and shares your organization receives (/app/inbox).
- Recipient Wallet
Public device wallet (/wallet) where recipients keep verified seals handy without an app install — distinct from Business Inbox.
- Identity Verified
Person identity verification. Not checked today — never marketed as available.
Does not mean: Person identity verification is not available as a product claim today.
- Signature Verified
Cryptographic signature validation of the uploader or signer. Not checked today — not the same as a preserved signed PDF.
Does not mean: Preserving a signed PDF is not the same as validating a digital signature.