Free while we’re in preview

Get EraseProof

Shred by policy on a schedule, and keep a ledger that proves it happened.

The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.

One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.

Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.

One file — no installer
Runs on your machine, offline
Source code published below

Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, EraseProof is included in every plan along with the rest of the range.

What the ledger is for

Nine months from now someone asks what became of the client files from the March engagement. EraseProof appends one JSON line per erased file to a ledger you name: the path, the size, the SHA-256 of the content immediately before it was destroyed, the policy name, the pass count and a UTC timestamp. The write is strict O_APPEND. An existing ledger is never truncated or rewritten, so every run that ever touched it is still in there.

Policies, not filenames

You define named policies in a JSON file, each pairing a directory with a glob, an age filter and an overwrite-pass count. Then you run one by name from cron or Task Scheduler, over and over. eraseproof scan temp-cleanup shows what currently matches and touches nothing.

This one really does delete

run --apply overwrites each matching file with cryptographically random data for the policy’s pass count, fsyncing after each pass, then removes it. No quarantine, no undo, no recovery. That is the job. Run scan first.

ledger reports cumulative totals per policy across every run that ever appended to the file. Auto-discovery of browser and app cache locations isn’t in this build. You name the directories yourself.

Reading on the job itself

How to securely delete files (and when not to bother) On a spinning hard disk, overwrite the file and it is gone. On an SSD you cannot reliably overwrite anythin...

The rest of Privacy Eraser

Getting rid of things properly. Overwriting files for good, clearing the traces programs leave, proving it happened, and auditing a fleet.

PrivacySweep

Simple Ready

Overwrites files with random data, removes them, and records what it destroyed.

CleanVault

Vertical Ready

Knows that Firefox hides your history in places.sqlite. And a hundred places like it.

TraceGuard

Team Ready

Checks every laptop's cache and history trails against a written policy.

Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams

A working CLI prototype of the recurring-erasure engine: named policies (path + pattern + age) scanned or run on demand, multi-pass random-overwrite deletion, and a cumulative append-only JSON-lines proof-of-erasure ledger you can audit across every run, ever. Scheduled/background execution and a system-tray UI are still on the roadmap.

Recorded session

Recorded terminal session showing EraseProof running — A real recorded session — EraseProof’s actual output, captured by running the shipped binary.

What it draws on

Existing paid software whose best ideas shaped this program: O&O SafeErase, east-tec Eraser, Folder Lock, CCleaner Professional.

Command line

There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.

EraseProof — policy-driven, recurring secure erasure with a
cumulative append-only proof-of-erasure ledger

Usage:
  eraseproof scan   --policy FILE <policy-name> [--json]
  eraseproof run    --policy FILE <policy-name> --ledger FILE [--apply] [--passes N]
  eraseproof ledger --ledger FILE [--policy NAME] [--json]

scan is read-only: it previews which files currently match a named
policy's target directory, glob pattern, and age filter. Nothing is
touched.

run without --apply is a dry run identical in spirit to scan, framed
as "this run would erase". With --apply, every matching file is
overwritten with random data for the policy's pass count (or
--passes, default 3), fsync'd each pass, then removed — the same
mechanism PrivacySweep uses for shred. One JSON-lines record is then
APPENDED to --ledger per erased file; prior runs' records (possibly
from other policies, at other times) are never truncated or rewritten.

ledger prints a summary of the cumulative ledger: total files erased,
total bytes, and a per-policy breakdown, optionally filtered to one
--policy name. This is the durable proof of everything ever erased.

Recorded from the shipped binary, not written by hand.

Windows (amd64) macOS (Apple Silicon) macOS (Intel) Linux (amd64)

Source

Every file the program is built from:

console.go · console_test.go · guided.go · main.go

SHA-256 checksums · build instructions & scope notes · full build plan

EraseProof

Preview