Free data broker removal tracker

Track removal requests and their evidence

A submission receipt, a provider response and a listing check tell you different things. This blank tracker gives each its own dated columns, one row per request, and a place to record what remains unverified.

Opens in Excel, Google Sheets, Numbers or another CSV editor. It has no example entries, formulas or macros.

Start with the privacy request kit to choose a route and prepare the request.

Keep a separate history of observations

Use one summary row per request in the tracker. Use one new row per receipt, response or check in this blank log, linked by a request reference you choose. Keep earlier observations when a listing changes or returns.

Downloading either file does not send a request, and this page has no upload for a completed sheet.

Choose a private request reference and enter it in the tracker's Request reference column.

For each observation, record the actual date and time zone, destination URL, access result and who or what supplied the evidence.

Record the provider's stated scope separately from what you observed. Keep a secure evidence reference rather than full documents in the sheet.

Add the next supported action and review date. The log does not schedule reminders or verify a result.

What each tracker column records

The tracker has no status to select. Each stage has its own dated columns, and an empty cell means not yet recorded.

Submission: the date and receipt show a request was sent and received.

Provider response: the reply shows what the provider says it did, within its stated scope.

Listing check: a loaded page without the listing shows only that it was not visible on that date. A blocked page is inconclusive.

Supported outcome: record the evidence behind any result and what remains unverified.

Columns in privacy-request-tracker.csv, in file order
Column	What to record
Request reference	A private reference you choose. Use the same reference in the evidence log.
Site or service	The site, broker or service that shows the listing.
Listing URL or reference	The exact listing URL, or the provider's own reference for it. Record the specific listing, not a general search page.
Request type	What you asked for, such as an opt-out, suppression, deletion, correction or search-result removal. Each has a different scope.
Request channel	How you sent it, such as the provider's form, privacy email address or account settings.
Official route source	Where you confirmed the route on the provider's current website or help center.
Submitted date	The date you sent the request. A submission alone does not establish any outcome.
Receipt or confirmation reference	The acknowledgment, ticket or confirmation reference. It shows the request was received, not completed.
Verification required	What the provider asked for to confirm identity or authority, such as an email link.
Verification completed date	The date you completed that step. Leave it blank while the step is pending.
Provider response and stated scope	What the provider says it did and what that covers. A suppression confirmation does not prove deletion of other copies.
Provider response date	The date of that response.
Follow-up sent date	The date of any follow-up you sent through the official route.
Listing check result	What you saw at the exact listing: still visible, not shown on a page that loaded, or inconclusive.
Listing check date	The date of that check. Add each later check to the evidence log.
Listing check access limits	Any CAPTCHA, login page, rate limit or error. A blocked check is inconclusive.
Outcome evidence reference	Where you stored the screenshot, email or response that supports a result. Keep the files in secure storage, not in the sheet.
What remains unverified	What you could not confirm, such as other copies, search results or the original source record.
Next review date	When you plan to check again. Use the provider's stated deadline where it gives one; there is no universal recheck interval.
Notes	Anything else that helps you follow the request. Leave out passwords, full government ID numbers and identity documents.

Keep the observations separate

Check the route and match. Use the linked guide as a starting point, then check the provider's current official instructions. Match more than a name before acting. Record the particular listing or source you intend to address.
Record submission. Save the submission date and a secure reference to the receipt. A receipt establishes that a request was received; it does not establish removal.
Record the provider's response. Keep its date and stated action. A suppression confirmation does not prove deletion of source records or other copies.
Record a separate visibility check. Note the URL or search context, date and what actually loaded. A CAPTCHA, login page, rate limit or access-denied page makes the check inconclusive. A successfully loaded route without the targeted listing supports only that observation, at that time.
Choose the next review date. Use the provider's stated deadline and your situation. There is no universal completion time, confirmation-link lifetime or fixed recheck interval.

If the request stalls

Read the stated reason before repeating a request. An expired link may require a new link through the official route. A denied request may involve eligibility, verification, a wrong match or an exemption. Record the next supported step instead of marking the listing removed.

If a listing appears again, review its match and current route before submitting another request. Keep the new observation separate from the earlier result.

Handle identity checks and evidence carefully

Check the recipient, purpose and current requirements before sending identity documents. Keep documents and screenshots in secure storage; use a reference in the sheet. Avoid storing government ID numbers, passwords or full identity documents in a shared spreadsheet.

Google is a separate request

For personal data still present on a live page, check Google's eligible personal-information route. If the source has changed or disappeared but Search shows old information, use the outdated-content route. Eligible requests can run alongside source removal. Record Google's decision separately; a full or query-limited removal does not remove the source page. Choose the appropriate search-removal route.

What this template does

Each download is a blank spreadsheet you fill in yourself. It does not submit requests, validate identity documents, schedule checks or independently verify removal.

Frequently asked questions

Which file should I use?

Use the request tracker for a current summary. Use the evidence log for repeated dated observations. Give the request a private reference and record that reference in both files.

Does the spreadsheet submit or verify removal?

No. It is a template you fill in yourself. It does not submit requests, check identity, schedule reviews or independently verify removal.

What should I record after a denial?

Save the provider’s reason and date. Review the match, eligibility, verification and stated scope, then record the supported next step. Do not mark the listing removed or repeatedly submit an unchanged request.

Should I overwrite an earlier check?

Keep the earlier observation and add a new row. Different dates or access conditions can produce different results. Preserve any provider response separately from your visibility checks.

Can I share the tracker publicly?

Keep it private. Store documents and screenshots securely and use references in the sheet. Do not include passwords, full government identifiers, recovery codes or complete identity documents.