Can users see a deletion history or audit log on redact.dev?
This fact-check may be outdated. Consider refreshing it to get the most current information.
Executive summary
Redact.dev is a consumer-facing app that runs deletion workflows locally on a user’s device and markets features like preview mode, scheduling and “disappearing mode” for automatic deletions — the company states deletion logic executes on the user’s machine and message data does not pass through Redact servers [1] [2]. The product pages repeatedly advertise preview/select modes and local archiving options but do not mention a user-visible deletion history or centralized audit log for actions performed by the app in the available documentation [3] [4] [5] [6] [2].
1. What Redact says it does — local deletions and preview options
Redact’s marketing and help content emphasize that deletion workflows “run on your device” and that the app offers Preview Mode and Select & Delete flows so users can see what will be removed before committing, plus scheduling/“Disappearing Mode” for automated runs [1] [5] [2]. Product pages for multiple services describe a preview step and “select and delete” batch options intended to give users visibility into candidate items before deletion [3] [4] [5].
2. The explicit claim about servers and message data
Redact’s FAQ/blog states plainly that “the deletion workflow runs on your device, and message data does not pass through Redact servers,” framing the product as privacy-first and local-only for deletion execution [1]. That technical posture reduces the need for a centralized server-side audit trail from a privacy point of view, because the company presents itself as not retaining message content centrally [1].
3. No mention in available pages of a persistent, user-facing audit log
Across Redact’s service pages and blog content reviewed here, the company documents preview modes, local archiving, scheduling, and that the deletion process is irreversible, but none of the cited pages describes a visible deletion history, action audit log, or exportable activity trail that a user can consult after runs [3] [4] [5] [6] [2]. Available sources do not mention a consolidated, user-facing audit log showing each deletion action and its timestamp.
4. Why an audit trail matters — compliance and accountability context
In adjacent industry discussions, redaction and deletion tools aimed at compliance often include “audit logs” as a core feature because logs show who did what and when — a requirement in many regulated settings (healthcare, legal) and a best practice described in third‑party redaction guidance [7] [8]. Redactable, a different vendor, explicitly markets audit trails and redaction certificates for compliance; that contrast shows the kind of documentation customers ask for when tracking deletions [7].
5. Two plausible explanations for the absence of an audit feature in Redact’s docs
First, Redact’s local-first architecture may mean it deliberately avoids storing action histories centrally to reduce privacy risks — consistent with its “runs on your device” claim [1]. Second, Redact may offer only ephemeral, on-device records (e.g., a local preview file or archived content) rather than a server-hosted audit trail; product pages mention local archiving options but do not detail a durable action log or export feature [9] [5].
6. What users should check before relying on Redact for auditable deletion
If you need an auditable record (for workplace compliance, legal defensibility, or corporate governance), request explicit documentation from Redact showing whether the app records: (a) a timestamped action log; (b) the identity of the local account that ran the job; and (c) an exportable trail you can keep off-device. The public pages reviewed here do not provide those confirmations [1] [2].
7. Conflicting signals and reputational context
Redact positions itself as privacy-focused and local-only [1], which can be a selling point for consumers but a limitation for enterprises that require centralized auditing [7] [8]. Independent reviews and user reports are mixed; Trustpilot shows varied customer experiences which include billing and usability complaints, though those reviews do not specifically confirm or deny audit-log functionality [10].
8. Bottom line: answer to “Can users see a deletion history or audit log?”
Available sources state Redact provides preview and scheduling features and runs deletions locally [5] [1] [2], but they do not describe a user-accessible deletion history or centralized audit log; therefore, available sources do not mention a visible, exportable audit log of actions taken by the app [3] [4] [5] [1].
Limitations: this analysis relies only on the provided Redact pages and related sources; product features can change and the company may offer undocumented or enterprise features not covered in these pages. For definitive assurance about audit logs, request Redact’s current technical documentation or an explicit vendor statement.