Utilize for Free for both Relativity Server & RelativityOne
Audio Redaction Workflows
Intelligent Voice supports Data Subject Access Requests under GDPR, FOIA, etc. as well as redacted productions and disclosures for civil litigation and regulatory requests for both Relativity Server and RelativityOne.
Potentially sensitive audio is easily reviewed, thanks to a zoomable waveform for longer recordings, the ability to navigate directly to a sub-second elapsed time in the recording, and the 0.1 times real-time playback rate increments in the
Intelligent Audio / Video Player.
Redactions are created by click and drag across the zoomable waveform or by direct timestamp entry, with the redacted audio track replaced with either silence, a continuous beep, or white noise.
Intelligent Audio / Video Validation flags up any corrupt or encrypted media at Search Set or Workspace level, for which redactions will neither be possible nor required.
Redacted objects integrate with Relativity’s own native production processes for both single file downloads and bulk production sets.
Each step in the redacted production is available Single File, or as a Bulk Process, or as combinations of the two:
- Creating a Redacted Copy of the Native file
- Swapping the Redacted Copy in to become the Native
- Producing the Redacted Copy
- Reverting the Native to the original uploaded file
Both redacted and unredacted objects can be combined into a single Relativity production set, with the same production processes followed whether files within the production set have been redacted or not.
Supported Audio Redaction Scenarios
Intelligent Voice in Relativity supports the following redaction scenarios:
- Teams with different expertise - e.g.: one team focuses on profanity or irrelevance, whilst another team focuses on assessments of privilege.
- Hierarchies within a team - e.g.: where paralegals apply draft redactions for approval, and reviewers confirm and approve.
- Different requesting parties - e.g.: multiple parties on the same call recording, with the attorneys for different parties requesting different redactions to the same recording.
- Sequential or overlapping requests regarding the same party - e.g.: where a case custodian submits a DSAR mandating a response ahead of the case disclosure schedule, and with separate redactions required.
- Separate regimes & redaction rules within a given jurisdiction - e.g.:
- Disciplinary
- Regulatory
- Litigation
- Criminal Justice
- Variations in privacy requirements across different jurisdictions - e.g.:
- New York versus Frankfurt
- California versus Texas
Any and all combination of these scenarios are concurrently supported within both RelativityOne and Relativity Server for free.