Changelog
Roadmap
Help Articles

Have something to say?

Tell us how we could make the product more useful to you.

Create a way to un-triage from the redact screen

Sometimes, from the redact screen you realise that something should not have been triages (e.g. an email chain that contains duplicates of the previous email copies). It would be great to be able to untriage those directly from the redact screen instead of having to try and find them again in the triage screen.

Harry Mustoe-Playfair 3 days ago

💡

Feature Request

Completed

Deleted files leave source uploads and attachment blobs in storage

When a file is deleted, the database rows are removed and the logs report success, but the underlying objects stay in Cloud Storage indefinitely. Evidence (production, 16 July deletion, still present 20 July) Logs show the full happy path: Attachments cleaned up and unreferenced blobs queued for reap, Starting async PDF cleanup, File deleted successfully. Despite this, thousands of attachment blobs remain under the project's attachments/ prefix in the uploads bucket. The original uploaded source files also remain under the user's uploads/ prefix — they do not appear to be removed by the delete path at all. Four days later none of these objects have been reaped. Why it matters This is a retention and data-protection gap, not just wasted storage. A customer who deletes their content — often the whole point of a redaction workflow — still has the original documents and attachments held on our infrastructure, including personal data belonging to third parties. Deletion must actually delete. Suggested next step Verify the reap queue is receiving rows and is actually being drained, confirm the delete path removes the source upload as well as attachments, and backfill a cleanup for objects already orphaned by past deletions.

Harry Elliott 7 days ago

2

Bugs

Completed

File deletion intermittently returns 500 before eventually succeeding

Deleting a file from a project intermittently fails with a 500 before a later retry succeeds. Observed repeatedly on 15-16 July in production. Evidence One file returned 500 on four consecutive delete attempts, then succeeded. A second file returned 500 twice before succeeding. A third returned 500 twice the previous day. One delete returned 200, and an immediate repeat of the same request returned 404 — so the client cannot tell a real failure from an already-completed delete. Why it matters Deletion is a data-protection operation. A customer clearing their own content sees an error and cannot tell whether the data was removed. Repeated retries also mean the cleanup path runs more than once for the same file. Suggested next step Capture the underlying error behind the 500 (the response body is generic), make the delete idempotent so a repeat returns success rather than 404, and surface a clear outcome to the user.

Harry Elliott 7 days ago

2

Bugs

Completed

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.

Harry Elliott 7 days ago

Bugs

Redaction comment quick selection

Having to type similar comments while redacting is very tiresome. It would be useful to have some presets to quickly click/choose from: TPD: Third party personal data NPD: Not the requester’s personal data SEC: Security-sensitive information LPP: Legal professional privilege CON: Confidential information OOS: Out of scope DUP: Duplicate already provided This would speed up the redaction process considerably, and keep things consistent across files. It would be great if you could quickly add your own redaction reasons as well?

Harry Mustoe-Playfair about 1 month ago

💡

Feature Request

Ability to mark files/emails as "Complete" in redact mode

We are going to be redacting several thousand emails and documents. We need to know whether we’ve finished processing each file - sometimes files might have no redactions, so we need to be able to mark these as ‘complete’ to be able to track our progress. Add to that, the ability to filter by “Complete” or “Incomplete”

Harry Mustoe-Playfair about 1 month ago

💡

Feature Request

Completed

Wordlist redact numbers are all over the place

When doing a redaction using a wordlist, the numbers it shows are all over the place. For example, for one keyword it shows 250 matches across 100 items. Then, when inspecting, it shows “Redact 4223 matches” Then, when clicking the “Redact 4233 matches” it changes to a confirm button: “Redact 4223 matches of 40”

Harry Mustoe-Playfair about 1 month ago

2

Bugs

Completed

Increase upload rate limit

When trying to upload many files, I get the error: Upload Rate Limit You're uploading too quickly. Please wait 30 seconds before uploading more files. This really shouldn’t be happening - the whole point of this application is to upload many files and emails! Either the rate limiting should be handled transparently, or the limit should be removed?

Harry Mustoe-Playfair about 1 month ago

1

Bugs

Open and import password-protected PDFs

Password-protected PDF attachments now show a clear "password-protected" notice instead of locking the page up — but there's still no way to get at the contents. Add a way to unlock these files: prompt for the password when previewing or importing, then store an unlocked copy so the document behaves like any other — preview, search, redact and export. Raised off the back of the locked-out display bug report.

Harry Mustoe-Playfair about 2 months ago

💡

Feature Request

Completed

Implement stable sorting algorithm / Multiple column sorting

When you sort emails by a column that has a lot of duplicate values (e.g. sorting by “From”) and then take an action on an email, the order of the emails can jump around randomly. The emails should remain in the same order, even if one is triaged. This could be solved by including a final ordering param (e.g. always have a final order by ID or date). It would also help to be able to sort by multiple columns, e.g. From ASC subject ASC

Harry Mustoe-Playfair about 2 months ago

1

Bugs

Completed

Bulk actioning on emails (>~200 selected)

When doing a bulk action on >200 emails approx, it comes up with a 400 error: Failed to perform bulk action: Request failed with status code 400 The only way to do is a page at a time at the moment. There is a corresponding logged error: location: "body" msg: "Invalid value" path: "emailIds" type: "field" With a bunch of email ids

Harry Mustoe-Playfair about 2 months ago

Bugs