CrashPlan Legal Hold vs Q1 Defensible Legal Hold

CrashPlan Legal Hold preserves and collects backup data tied to legal matters as part of eDiscovery. A preservation policy sets which files are kept and for how long; a matter applies that policy to a group of users. CrashPlan collects regular file updates from custodians’ devices without notifying them, and the hold’s backup set is not shown in the CrashPlan app. Data access and policy changes are logged for audit, and CrashPlan says it retains file timestamps, permissions, and directory paths. An open API and integration documentation let an existing eDiscovery platform access preserved data. Collection requires an active hold and an active CrashPlan app on the target device. Console collection is unavailable for archives using an Archive key password or Custom key, though the data remains preserved. Custodians continue using a subscription while a matter is open. Releasing a custodian or closing a matter starts permanent deletion of data preserved by that hold. Pricing is on request; there is no free plan.

Q1 Defensible Legal Hold is an application suite for legal hold management, data preservation, and data collection. It manages customizable holds from issuance through release, including custodian and administrator notices, scheduled reminders, escalations, timeline notices, release notifications, and system-wide reporting. Automated procedures apply legal-hold metadata to connected repositories while allowing continued data use. Other automated processes can cull, collect, validate, and preserve copies of potentially relevant artifacts. Q1 says its backend engages with more than 200 source data repositories and names Nuix and Relativity as downstream processing and review integrations. The suite includes notice creation, management, escalation, and auditing functions and is presented for legal firms and corporations. Q1 describes the workflows as defensible and court admissible, but does not name a security certification or compliance standard. The product pages do not specify operating systems, deployment options, mobile apps, or an API. Pricing is on request, with a demo or contact route offered.