A Working Glossary for Digital Footprint Checks

Twelve terms you will meet in practice

Term	What it means here	Common misreading
Digital footprint	Every traceable item you have left on a platform	Assuming it only covers posts you wrote
Archive	A snapshot the platform exports, covering posts, likes, messages	Treating it as a backup that updates itself
Check / audit	Read-only analysis that scans risk without changing anything	Treating a check as cleanup
Exposure	How far information can be obtained by a third party	Assuming only seen information counts
Linkability	Whether separate accounts can be tied to one person	Assuming a handle change is enough
De-identification	Removing fields that point directly at a person	Assuming removing a name finishes the job
Erasure request	A legal request for a platform to delete data	Assuming it reaches third-party reposts
Data portability	A request for a copy of your data	Confusing it with the right to erasure
Resurfacing	Old content being dug up and spread again	Assuming it only happens to public figures
Doxxing	Someone gathering and publishing your personal details	Assuming a prior check caused it
Rate limit	A cap on how often an API can be called	Assuming the account is being punished
On-device processing	Data parsed on your machine, never uploaded	Assuming anything in a browser is on-device

The first row deserves a note. In everyday use, footprint gets narrowed to what I posted, while the real scope is wider: likes, reposts, the following list, links in your bio, and reused handles or avatars on other platforms all count as traces.

The two terms that cause the most damage

The first is archive. In casual use it overlaps with backup, but the two behave in opposite ways during a cleanup. A backup follows the source data, so it updates when the source changes. An archive is a snapshot from one point in time, so posts you delete afterwards still exist inside it, with their original text.

That has a practical consequence. Once the cleanup is done, the archive file on your machine is itself sensitive data. It concentrates everything you decided to remove. Treat it accordingly, as described in storing an archive safely.

The second is rate limit. When a deletion job pauses or slows down, the first reaction is usually that something is wrong with the account. Most of the time the API call allowance has simply run out and the job resumes on its own. See how API rate limits affect deletion.

Three trace types that get overlooked

The first is romanised names. Once a Chinese name is written in pinyin, it matches in a search box in a completely different way from the characters. Someone who cannot find you by your Chinese name may still pull years of your posts together using the pinyin form. Handling for this is covered in cleaning up pinyin name traces.

The second is handle reuse across platforms. Reuse is common, and that pushes the practical weight of linkability higher than a model setting suggests.

The third is replies. People focus on their own posts and skip the replies they left under someone else's. Replies appear in the archive too, and they carry the same information. Do not leave them out of the scope.

Learning the terms by task

1. Requesting your data: archive, data portability and JSON decide which file you end up with.
2. Running the check: check, exposure and linkability decide how you read the report.
3. Starting a cleanup: deletion, rate limit and pause decide how the job behaves.
4. Going the legal route: erasure, GDPR and CCPA decide whether you act in the product or file a formal request.

None of this needs memorising, only recognising on screen. The two places where it matters most are export and authorisation, both of which present English options. Chinese-specific guidance is collected at a footprint guide for Chinese-speaking users.

About Digital Footprint Health

Digital Footprint Health (digital-footprint-health.shop) presents its interface and reports with Chinese and English side by side. Upload your X data archive and it parses every tweet on your own device, returning a score from 0 to 100 and flagged items by category; the check is free and read-only. If a term is unclear, running one check and matching the report categories against your actual posts teaches more than looking it up. Scope and pricing are on the pricing page, you can start free from the homepage, and related reading is on the blog.