Covered on screen
The underlying content may still be present.
3Comp Secure / Redaction & disclosure
Redaction
you can prove.
A clearer path to securely identify, review and remove sensitive information from documents and emails — with evidence from source to disclosure.
In development · Explore the planned workflow
Correspondence summaryIllustrative document · Fictional content
The information below relates to your request.
A conversation with Alex Example was recorded in the case notes. Please review the third-party information before disclosure.
Follow-up contact: Redacted
Suggested finding. Your decision.
Third-party name · Needs contextual review
01 Source02 Working copy03 Disclosure
Automated detection.
Human-controlled decisions.
Built for defensible disclosure
A disclosure is more
than a document.
It is a decision about what someone should receive — and what needs to stay protected.
Data subject access requests can bring together correspondence, personal information and details about other people. Privacy and information governance teams need context, considered decisions and a clear record of what was released.
RedactAssura is being designed for that whole journey: DSAR and GDPR disclosure, sensitive information review and the evidence behind the final artefact.
The intended workflow
From source to disclosure.
Every decision connected.
Six clear stages. One accountable path through the material.
-
01
Collect
Establish the sourceBring together material in scope and preserve its original context.
-
02
Detect
Surface candidatesIdentify potential sensitive information for a reviewer to assess.
-
03
Review
Make the decisionConsider the request, third-party information and disclosure context.
-
04
Redact
Apply the decisionRemove selected information from a separate working copy.
-
05
Validate
Check the outputCheck the disclosure artefact before authorising its release.
-
06
Release
Keep the evidenceConnect the approved disclosure to the decisions behind it.
RedactAssura is in development. The workflow shown is an illustrative product concept; the authenticated redaction application is not yet available.
Detection with context
Find what matters.
Decide what stays.
A suggested match starts a review. It does not make a legal decision.
The planned detection workflow brings possible names, contact details, financial information and custom terms into view. Reviewers consider each finding in context, including information about third parties.
- Select category
- Review findings
- Redact selected
Accept a relevant finding, ignore a false positive, or add a manual redaction. A “redact similar” action would still require the reviewer to consider the other occurrences.
Suggested categoriesThird-party information 03Names 06Email addresses 02Phone numbers 01Addresses 01Financial information 02Sensitive information 01Custom terms 04
Candidate / 01 of 03
Third-party name
“A conversation with Alex Example was recorded in the case notes.”
Fictional example. The reviewer determines whether this information should be disclosed.
AcceptIgnoreRedactRedact similar+ Manual redaction
Real redaction
Hidden isn't
redacted.
A dark rectangle can hide words on screen while leaving the underlying information recoverable. A disclosure process needs to consider the data in the file, as well as what a viewer displays.
RedactAssura's intended approach is a sanitised disclosure artefact, checked before release. Supported formats, sanitisation behaviour and validation checks will be confirmed as the product is implemented and tested.
Discuss your disclosure requirementsSanitised and checked
Selected information removed
Output validation must confirm removal within the supported format.
Evidence through the workflow
Keep the original.
Account for the outcome.
The intended model separates the source, the review workspace and the released disclosure — with an evidence trail connecting them.
Original
Preserved source
The reference point for the review, kept separate from disclosure output.
Working copy
Human review
Detect · Review · Redact · Undo
A considered space for decisions.
Released disclosure
Sanitised output
A separately checked artefact approved for the intended recipient.
A timeline you can explain
Illustrative audit sequence for the planned product.
- Source uploaded
- Sensitive information detected
- Reviewer decisions recorded
- Manual redactions applied
- Disclosure validation completed
- Disclosure generated
For privacy & information governance teams
From DSAR
to disclosure.
A focused redaction workflow within your wider response process.
Start with the scope of the request and the material your team has collected. Review the requester's information alongside third-party details, make appropriate disclosure decisions, and check the final output before release.
Your organisation retains responsibility for the response, applicable exemptions and legal judgement. RedactAssura is not a promise of automatic GDPR compliance or a deployed DSAR case-management service.
Read the ICO's guide to subject accessPrivacy teams
Review personal information with the context of the request in view.
Information governance
Connect handling decisions, reviewer accountability and disclosure evidence.
Controlled disclosure
Prepare a considered release while keeping source material separate.
Redaction categories
Sensitive information
takes many forms.
Examples of review categories that inform the product design. These are not a verified detection coverage list.
Personal information
Names and other identifiers that need a contextual review.
Third-party information
Information about people other than the requester.
Contact information
Email addresses, telephone numbers and postal addresses.
Financial information
Account references and financial details within scope.
Sensitive information
Potentially sensitive material requiring careful judgement.
Custom information
Organisation-specific terms and case-specific review criteria.
Security & governance
Control belongs
in the process.
The planned product is shaped around deliberate handling of sensitive material. Implementation and validation must establish these controls before a live service can make operational assurances.
- Controlled processing
- Define what is in scope, who may review it and where processing is authorised.
- Human review
- Keep responsibility for disclosure with an accountable reviewer.
- Audit evidence
- Retain the context and decisions that explain a redaction.
- Secure disclosure
- Check and authorise the output for its intended recipient.
- Separate artefacts
- Distinguish the preserved original from the working copy and released file.
One Secure family
Focused on disclosure.
Part of something broader.
RedactAssura brings a focused redaction and disclosure proposition to the 3Comp Secure family, alongside privacy governance, security assurance and accountable action.
Explore the 3Comp Secure portfolioRequest a Demonstration.
Talk to us about the planned RedactAssura workflow, your disclosure challenges and early demonstration availability. Please describe your requirements without sharing documents, DSAR material or sensitive personal data.
Prefer email? Write to [email protected].