Project Safety

Respect the source. Define the handling.

Local processing is one part of responsible collection work. Access, derived information, review and retention also need a clear plan.

Explore in a private demo ↗

Preserve the original record

The discovery workflow uses derived information to make source material easier to find. Original files remain the reference for checking a result. Duplicate or similarity findings do not require destructive cleanup.

Process an agreed collection

Each evaluation defines what may be accessed and processed. A representative sample is often the best place to start. Ownership, permission to use the material and any access restrictions are discussed before processing.

Treat derived information as collection data

Transcripts, recognized text, thumbnails, indexes and exported findings can also contain sensitive information. Their storage, access and retention belong in the handling plan.

Keep review separate from inference

Speaker labels, recognized words and suggested relationships can be wrong. Review important findings against the source and keep uncertain results distinguishable from confirmed conclusions.

Agree on project closeout

Decide which working files and results are retained, returned or removed at the end of an evaluation. Removing a project is not a promise of secure erasure from every storage device or backup. Any sanitization requirement must be separately specified and verified.

Protect a managed configuration

Workstation access, maintenance and recovery procedures are defined for the engagement. The agreed configuration determines the protection and recovery measures included in the engagement.

Keep website inquiries separate

The contact form accepts project descriptions, not archive uploads. Do not put confidential records, credentials or restricted content into an inquiry. Read the website privacy notice.

LET’S EXPLORE IT TOGETHER

Bring us an archive problem.

Tell us about your collection and the question you need to answer.