Free while we’re in preview

Get PrivacySweep

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

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, PrivacySweep is included in every plan along with the rest of the range.

This is not a recycle bin

privacysweep shred destroys files. There is no quarantine mode and no undo, and that is the point of a secure-delete tool rather than a gap in it. Give it a directory and it walks the entire tree beneath it. Test your arguments on a throwaway folder first so you know precisely what they select.

Without --apply it’s a dry run: every file it would take is hashed and listed and nothing on disk is touched. That listing is the check worth making every single time.

What `--apply` does

Each file is overwritten with random data for --passes rounds, three by default, with an fsync after each round, and is then removed. Afterwards you get a JSON proof-of-erasure record per file: the path, the size, the SHA-256 of the content as it stood before erasure, the pass count, and a UTC timestamp. --report FILE writes that out; otherwise it goes to stdout.

Worth being straight about one thing no userspace tool can solve: overwriting acts on the file as the filesystem presents it. Copies elsewhere, older versions in a backup, and blocks an SSD has already retired internally are beyond its reach.

Browser and app cache cleanup and the encrypted vault are roadmap. This build is the shredder and the report.

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.

CleanVault

Vertical Ready

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

EraseProof

Pro Ready

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

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 core engine: secure multi-pass random-overwrite deletion with a JSON proof-of-erasure report. Browser/app trace cleanup and the encrypted vault are still on the roadmap.

Naming status

Working name only — brand verdict **RENAME** (High). Collision: Privacy Sweep. Use a more distinctive coined mark.

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.

PrivacySweep — secure file deletion with a proof-of-erasure report

Usage:
  privacysweep shred <path> [<path> ...] [--passes N] [--apply] [--report FILE]

Without --apply this is a dry run: nothing is touched, only listed.
With --apply, matched files are overwritten with random data for
--passes rounds (default 3), fsync'd each round, then removed.
This cannot be undone — there is no quarantine mode for shred.

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

PrivacySweep

Preview