How to Use Eraser for Data Broker Requests, More Privately

Eraser is a free, open-source project for handling data broker opt-out requests from your own computer. The maintained continuation offers a browser interface and command-line tools. It can use your email account to send requests and track replies, while keeping its profile and history in local files. That design gives you more direct control, but it also means your device and configuration need protection.

Get the current copy from its source

Start at the maintained Eraser project on GitHub or its official project site. Read the release notes and install instructions for your operating system. Avoid downloads from search ads, file mirrors, or unrelated repositories. The original repository is archived or may have moved; use the maintained source for current instructions.

The project documents prebuilt releases and installation with Go. If you build it yourself, follow the current repository steps and inspect the files before running them. Keep the app on your own computer. Do not put your personal profile, configuration, or request history on a public web host.

Start with a dry run

Before any email is sent, review the current configuration and use Eraser’s dry-run mode. Check which names, regions, categories, and recipients are included. Remove brokers you do not want to contact. If you would rather not give the app mail credentials, use the manual-send workflow documented by the project and send each message from your own mail client.

Limit what the configuration contains

Eraser may need details such as names, addresses, phone numbers, or prior addresses to find a matching record. The current 2.0 project can encrypt stored mail passwords with an optional passphrase; other local profile and history data still need protection. Enter only information you are comfortable sending to the brokers you select. Use an app-specific password rather than your primary mailbox password. If you choose to store it, set the project’s optional password-encryption passphrase and keep the configuration and local history out of shared folders and source-control repositories unless you have reviewed their privacy and encryption settings.

Protect the operating-system account that owns the files. Use full-disk encryption where available, keep software updated, and remove the configuration securely if you stop using the tool. Do not paste configuration contents, broker replies, or private records into support forums.

Treat each request as a decision

Some brokers ask for extra verification, may link to a web form, or may not be covered by the privacy rights available in your location. Review the current source guide before continuing. Skip a request if you do not understand who will receive the information or why it is necessary. A sent email or completed form means only that a request was submitted; it does not prove that all records were erased. Check the broker’s reply and revisit high-priority listings later.

Keep a minimal follow-up record

Record the broker, request date, and next follow-up date. Avoid storing the submitted identity details in a second spreadsheet. Eraser’s local history can help track replies, but it is still sensitive data: protect it like the configuration. If you want a list of starting points, use Vanishio’s searchable data broker directory.

Step-by-step plan

1. Install from the maintained project

   Use the current GitHub repository or official site to select the release and platform instructions. Confirm you are using drumandbytes/eraser, the maintained continuation.

   Privacy caution

   Do not use a public hosting account or third-party mirror for personal configuration files.

2. Choose what the tool can send

   Decide whether to use a mail app password or the documented manual-send mode. Start with a dry run and inspect the brokers and recipient routes.

   Privacy caution

   Never enter your primary mailbox password. Keep any app password out of shared documents and repositories.

3. Review and follow up

   Send only requests you have reviewed. Check confirmations and replies, then record the request date and outcome without duplicating sensitive identity details.

   Privacy caution

   Submitting a request does not prove deletion; some sites need extra steps or may not act.

Choose a removal path →

Frequently asked questions