Digital footprint versus browser fingerprint

One thing worth flagging up front: clearing a canvas hash does not log you out. A digital footprint is the trail of names you already gave a site. A browser fingerprint is a measurement the page takes of the engine you opened. People mash those into one word and then wonder why a new user agent did not unset a saved card.

I keep the split boring on purpose. If a sentence works with either word, the sentence is sloppy. This note sits in Browser fingerprinting so the cluster does not treat a leftover login as a GPU string.

Footprint is a name you already typed

A footprint starts when you type an email, save a card, accept a first-party cookie, or recover an account with a phone. The site stores a person. Later visits reuse that person. Opening a new profile folder does not unset the recovery SMS. Painting a new WebGL renderer does not unset billing.

That trail can live in several places at once:

None of that is what browser fingerprinting measures. The measurement does not need your name. The footprint is the name.

Operators collapse the words because both can join visits. Joining is not the same mechanism. A leftover login joins you because the cookie is still there. A leftover GPU string joins you because the engine still answers the same way.

Fingerprint is a measurement

A page asks the process questions. How many cores. Which renderer. What hash does canvas return. What timezone does Intl report. The answers are useful when they stay put and when they agree with each other. That is the whole idea.

The surfaces we actually cover are that measurement, applied on a local Windows profile. They are not an account system. MaskWright has no login and no cloud profile sync. Separate profiles are separate folders under {Electron userData}/maskwright-data. Separate folders are not separate payment instruments.

A new fingerprint in the same folder is the collapse in practice. You changed the measurement and kept the cookies. The site still has the session. You only changed the engine answers.

I test coherence, not vibes. If timezone, language, and the exit country disagree, that is a fingerprint problem. If the same Gmail is signed into two profiles, that is a footprint problem. Mixing those diagnoses is how people reroll a seed to wash a login.

Where the two trails meet on one PC

Shared user-data. Two authorized brands in one Chromium directory are one footprint with two tab titles. Isolation without a separate --user-data-dir is a session switcher.

Shared recovery. Two profiles that use the same inbox or the same card are one footprint no matter how clean the WebGL table is.

Shared hardware. Cross-browser fingerprinting can join Chrome and Firefox on one NIC through IP, GPU family, and screen size. The footprint may also join them if you signed both with the same Google account. Two mechanisms, one desk.

Shared myths. A MAC address is not a canvas hash and it is not an email. We do not hide MACs. Blaming the adapter for a leftover login is the sloppy label again.

What fading cookies do not settle

After third-party cookies, Topics, CHIPS, and first-party sets change how some ad graphs work. They do not retire first-party logins. They do not retire fingerprints. A headline that says cookies are dead, so now it is all fingerprinting, skipped the login. A headline that says cookies are dead, so now it is all footprint, skipped the engine.

Fingerprint spoofing versus tracking prevention is the product fork on the engine side. Reducing signal is a privacy-browser move. Painting a coherent desktop identity is an isolation move. Neither move deletes a card on file.

I do not reroll a seed to wash a login. I do not import cookies into a new face and call it a new citizen. I do not claim the inject hides a processor fingerprint.

What I check when someone says footprint

I ask whether they mean a name or a measurement.

If they mean a name, I look at cookies, inboxes, and payment. If they mean a measurement, I test the profile for coherence and stability across launches.

Authorized work still starts with a right to the account. The footprint is that right, plus the leftovers you chose to keep. The fingerprint is whether the profile looks like one browser while you use that right.

FAQ

Can I shrink my digital footprint by spoofing canvas? No. Canvas is a measurement. Your email and your card are still on file.

Does a new MaskWright profile give me a new footprint? It gives you a new folder, a new cookie store, and a new fingerprint seed. It does not give you a new legal identity, a new inbox, or a new card.

If I clear cookies, is the fingerprint gone too? No. The engine can still answer the same way. And localStorage plus IndexedDB can still hold ids the cookie clear missed.

Use footprint for the graph of names. Use fingerprint for the engine bundle. If a sentence works with either word, rewrite the sentence.