Glossary

An append-only record of every action taken on a document — who accessed it, when, from where, and what they did. Once an entry is added, it cannot be modified or deleted.

The state of a document being under the protection and control of doclish. A document in custody is encrypted, fingerprinted, and subject to the full 7-step pipeline.

A downloadable PDF that certifies a document's chain of custody, integrity status, fingerprint, and compliance badges. Separate from the document itself.

Step 7 of the custody pipeline. The process of sending a document to a recipient via encrypted share link, email, or print — with access logging at every point.

A multi-step routing sequence that moves a document through a series of actions — email, transfer, verification — in a defined order. Each stop is logged to the chain of custody.

A temporary link generated when a user requests account closure. Provides access to download all documents for 3 days before permanent deletion.

A SHA-256 cryptographic hash generated at the moment a document enters custody. This unique identifier is used to verify that the document has never been altered.

The process of parsing a document's content and metadata when it first enters the system. Part of Step 1 (Intake) in the custody pipeline.

Step 1 of the custody pipeline. The moment a document enters the system — it is ingested, fingerprinted, classified, indexed, and registered as a custody record.

Step 5 of the custody pipeline. The process of comparing a document's current SHA-256 hash against its registered fingerprint to confirm it has not been tampered with.

Any document or data held in doclish custody. Subject to encryption, integrity verification, retention policies, and full chain of custody tracking.

Step 6 of the custody pipeline. The policy governing how long a document is preserved. Default is 45 years, aligned with HIPAA, CJIS, and FRCP Rule 26 requirements.

An encrypted, time-limited URL that grants access to view a document without transferring the document itself. All access through a secure link is logged to the chain of custody.

Step 2 of the custody pipeline. Documents are encrypted with AES-256 at rest and stored in Cloudflare R2 with automatic replication.

A custody reassignment. The document does not move — ownership changes from one custodian to another. The original chain of custody is preserved and the transfer is logged.

Step 3 of the custody pipeline. All document movement between systems and people is protected by TLS 1.3 encryption and authenticated token validation.

A document status indicating that its SHA-256 fingerprint matches the original hash recorded at intake. No tampering detected.