browser fingerprinting privacy

Browser privacy and fingerprinting

Understand why simple information can become a tracking signal when combined excessively.

Detected——

Capabilities0/8

Browser

Browser—

Version—

Engine—

User-Agent—

Environment

Platform—

Language—

Languages—

Timezone—

Touch points0

Capabilities

Cookies—

LocalStorage—

SessionStorage—

Service Worker—

WebGL—

WebAssembly—

Clipboard—

Online—

Reading happens locally and does not send User-Agent, timezone or capabilities to analytics.

Continue in the tool

Open full tool

More pages for this tool

How to interpret it

Timezone, language, viewport and capabilities are common. The risk appears when many signals are combined to create a unique browser impression.

Quick example

Lookup

Input: Idioma + timezone + APIs
Expected output: diagnóstico útil, mas deve ser limitado

Use the result as technical reference and confirm official sources when there is operational impact.

Check

Input: browser fingerprinting privacidade navegador
Expected output: browser fingerprinting privacy

The main tool remains interactive; this page organizes the search intent.

Full tool FAQ

What is a User-Agent?

User-Agent is a string sent by the browser in HTTP requests and exposed via JavaScript. It usually includes browser, engine, operating system and historical compatibility tokens.

Why can the User-Agent be misleading?

What are User-Agent Client Hints?

Can timezone and language identify a person?

Why check WebGL, storage and clipboard?

Does private mode change the results?

Does this tool detect a full fingerprint?

When should I share this information?

Frequently asked questions

Does this page fingerprint me?

Timezone, language, viewport and capabilities are common. The risk appears when many signals are combined to create a unique browser impression.

Does the tool work locally?

Yes. The main interface runs in the browser and avoids uploading sensitive data when the feature depends on local hardware.