Backlog
Under consideration
No Backlog issues
Next up
2Committed and queued
Secure send: deliver the finished SAR to the requester
Once a SAR is redacted, it still has to reach the requester safely. Today that usually means a password-protected ZIP over email, a USB stick, or a link from a tool nobody can audit later. Secure send would be a third workflow next to Redaction and Convert: send files securely, with full control over who can open them, for how long, and proof that they did. Sending Send straight from a finished export, or upload any files and send them (it works for things that aren't SARs too). One or more recipients per send, each with their own link, so access and the audit trail are per person. A covering message, with saved templates (for example "SAR response", "Clarification", "Extension notice"). Large exports are sent in parts, like downloads today. Access controls Expiry date on every link (a sensible default, capped by an organisation maximum). A one-time code emailed to the recipient, so a forwarded link doesn't work for someone else. An optional passcode on top, for you to share by phone or letter. A download limit, or view-only in the browser with no download. Revoke a link at any time, or extend it. Watermarking Stamp each page with the recipient's name or email address and the date, so a leaked copy can be traced back. Choose the position and opacity, or turn it off. Audit trail A log of every event: sent, code verified, opened, each file viewed or downloaded, revoked, expired. With date, time and IP address. Download it as a PDF or CSV and keep it with the redaction log and schedule as proof of disclosure. The date the requester first opened the files is recorded on the project, as evidence that you responded in time. Notifications Tell the sender when the recipient opens or downloads the files. Warn the sender when a link is about to expire without being opened, so they can chase or resend. Optional "I've received this" button for the recipient. Branding Your organisation's logo, colour and sender name on the email and the download page. A custom reply-to address, so replies go to your DPO inbox, not to RedactBox. Retention and organisation settings Sent files are deleted automatically when the link expires (or after a set number of days), and the audit trail is kept. Organisation admins can set defaults and minimums: maximum expiry, passcode required, watermark always on. Files stay on UK storage, the same as uploads. Why it matters It finishes the SAR inside RedactBox instead of handing off to email at the last step, and it's useful between SARs too (HR files, safeguarding records, FOI responses, anything sensitive that has to leave the organisation).
Import from and export to Google Drive and OneDrive
Most IT teams save their Microsoft Purview or Google Vault export straight into OneDrive, SharePoint or Google Drive. Today you have to download it to your computer and upload it again, which for a multi-GB export is slow and leaves a copy of personal data on a laptop. Import Connect Google Drive or OneDrive (including SharePoint document libraries) and pick files with the provider's own file picker. Import anything RedactBox already takes: Purview and Vault export ZIPs, PST, MBOX, EML, MSG, PDF and Office documents. Pick a whole folder and import every supported file in it, keeping folder paths. Files go straight from the cloud to RedactBox, never through your computer. Your plan's file size limits still apply. Only the files you pick are shared with RedactBox, not your whole drive. Export Save a finished export (ZIP or PDFs, plus the redaction log and schedule) to a folder you choose in Drive or OneDrive. Large exports are saved in parts, the same way they download today. A note is added to the project's activity log showing where and when it was saved. Notes Some Microsoft 365 tenants need an IT admin to approve the app before staff can connect it, so the help article needs a short "send this to IT" section. Pairs with Secure send: save the export to your drive, or send it to the requester, from the same screen.
In Progress
Actively being built
No In Progress issues
Done
59Recently shipped
Search to Redact Functionality
Being unable to search for specific keywords or specific emails was really problematic. I ended up exporting things back into outlook, deleting and sorting email chains and reimporting - which was time consuming.
The ability to share Projects
Allows you to share projects with other users on the platform.
Import common document attachments as PDFs (convert Office docs)
When an email has an attachment that's a common document type — Word (.doc/.docx), Excel (.xls/.xlsx), PowerPoint (.ppt/.pptx), and similar — let the user import it into the project as a redactable PDF. We already support importing PDF attachments directly into a project. The gap is the non-PDF document types: they'd need to be converted to PDF on import (a conversion step we don't have yet) before they can enter the redaction workflow. Goal: bring more attachment content into redaction — a user shouldn't have to download a Word/Excel attachment, convert it elsewhere, and re-upload it. Pick it from the attachment, we convert + import it as a PDF document in the project. Notes / scope: Reuse the existing 'import attachment as document' flow; add a convert-to-PDF stage for supported non-PDF types. Decide the supported set (Office formats first; maybe images, .rtf, .txt, .eml later). Conversion likely belongs on the worker / a conversion service (LibreOffice headless or similar) — needs design.
Upload Attachments from Emails
Grab attachments from emails, convert to PDF and then allow to redact.
Never-redact list: protect specific names from every redaction pass
A list of names, addresses or terms that must never be redacted, regardless of what a word list, Auto-Redact or Search & Redact would otherwise match. Why The requester's own name has to survive redaction, and so do things like the organisation's name or a case reference. Today a broad word list or Auto-Redact can catch them, and the only fix is to spot it and remove the redaction by hand — on every item. The ask A project-level "never redact" list that every redaction method respects. Simpler and independent of automatic name discovery, and useful on its own. Asked twice in support ("How do I use a whitelist of names that should not be redacted ever?" and "How do I whitelist certain names and email addresses which I don't want to redact?"). Logged from conversations 67 and 66.
Blank Pages at the beginning of PDF Exports
Fixed and deployed. Blank pages at the start of an exported PDF were caused by how documents authored in Word/Outlook declare their page layout: it forced a page break that left the document header alone on the first page, with the content pushed onto the next page (and, for multi-section messages such as bounce notifications, over several pages). The exporter no longer honours that author-supplied page layout, so the header and content now start together on page one. Genuine, deliberate page breaks are still respected. Note: this applies to documents processed from now on. PDFs that were already exported keep their existing layout — re-exporting the affected documents produces the corrected version.
[bug] Password protected PDF attachments cause locked out display
When a PDF attachment is password protected, the page prompts you for a password. When this is cancelled, it just prompts again, soft locking the page until you refresh.
Redaction Word Lists
I'd find it incredibly useful to be able to upload a list of pre-defined names, ideally via a CSV file, for the Search to Redact functionality. This would allow me to efficiently redact multiple specific names across documents, saving significant time compared to manually entering each name individually.
Embedded Image Redaction
Redact text and other content within images.
Add Header vs Body Filtering to Email Filter
This would be incredibly useful for our SAR triage process. We need more refined filtering options, like filtering on header vs. body, to effectively narrow down entire mailboxes and identify relevant emails before the redaction stage.