--
title: "A Working Glossary for Digital Footprint Checks"
description: "Twelve terms that do not translate cleanly, and the two that change your decisions when you read them the wrong way."
tags: ["privacy", "glossary", "digitalfootprint", "terminology"]
canonical_url: https://digital-footprint-health.shop/blog/chinese-digital-footprint-glossary
The place a footprint check actually breaks down is the vocabulary, not the interface. Community slang and tool definitions overlap without matching, and a literal translation moves the question without anyone noticing.
Two of these terms cause most of the damage. Both of them are words people are confident they already understand.
1. Why the vocabulary does not line up
Privacy vocabulary does not map one to one across languages, and a mismatched reading changes which posts you decide to handle.
The obstacle in a footprint check is rarely the interface. It is the vocabulary, and specifically the words that look like they have an exact equivalent in another language and do not.
Community slang points at incidents. Tool interfaces use definitions set by vendors. Their coverage overlaps without matching, so a literal translation quietly changes the question you think you are answering.
2. Archive is not backup, and the difference has consequences
Archive and backup behave in opposite ways during a cleanup: a backup follows the source data, an archive is a snapshot that keeps the posts you deleted.
A backup follows its source. Change the source and the backup changes with it. An archive is a snapshot from one moment, so posts you delete afterwards are still inside it, with their original text.
That is not a technicality. It means the archive file on your machine becomes sensitive data the moment your cleanup finishes, because it concentrates everything you decided to remove. Store it accordingly and treat the password as a separate problem from the file.
3. Rate limit is not a penalty
Rate limit gets misread as an account penalty, which leads people to abandon a deletion job that would have resumed on its own.
When a deletion job slows or stops, the first assumption is usually that the account has been restricted. Most of the time the API call allowance has run out and the job picks up again on its own after a wait.
Abandoning a job at that point is how people end up with a half-cleaned timeline and no record of where it stopped. Knowing the term is what stops the wrong reaction.
4. Three trace types that get overlooked
Three trace types get overlooked: romanised name forms, handle reuse across platforms, and replies rather than top-level posts.
Romanised names are the first one. A name written in pinyin matches in a search box in a completely different way from the characters. Someone who cannot find you by your name may still assemble years of your posts using the romanised form.
Handle reuse across platforms is the second, and it pushes the practical weight of linkability higher than any model setting implies. Replies are the third. People audit their own posts and skip the replies they left under someone else's, which carry the same information and live in the same archive.
5. Learning the words by task instead of by alphabet
The vocabulary is worth recognising by task rather than memorising: what you request, what you run, what you delete, what you file.
Split the list by what you are doing rather than by alphabet. When you request your data, the words that matter are archive, portability and format, because they determine which file you receive.
When you run a check, it is check, exposure and linkability, because they determine how you read the report. When you start a cleanup, it is deletion, rate limit and pause, because they determine how the job behaves. When you go the legal route, it is erasure and the specific regulation, because those determine whether you act in the product or file a formal request. Recognising the words on screen is the whole requirement.
Practical takeaways
- Privacy vocabulary does not map one to one across languages, and a mismatched reading changes which posts you decide to handle.
- Archive and backup behave in opposite ways during a cleanup
- Rate limit gets misread as an account penalty, which leads people to abandon a deletion job that would have resumed on its own.
- Three trace types get overlooked
- The vocabulary is worth recognising by task rather than memorising
The requirement is recognition rather than recall. The two places where it genuinely matters are export and authorisation, because both present choices in English and both are hard to undo once a selection is made.
The longer version with the reference detail is here: https://digital-footprint-health.shop/blog/chinese-digital-footprint-glossary
Top comments (0)