Browser fingerprinting
A tracking technique that identifies a device by combining browser and hardware signals, such as fonts, GPU strings, and timezone, into a stable identifier.
Browser fingerprinting is a way of identifying a device without cookies. A website reads dozens of attributes the browser exposes: user agent, screen resolution, installed fonts, GPU vendor and renderer strings, timezone, language, hardware concurrency, audio processing output, and canvas rendering results. No single attribute identifies you, but the combination is often unique. Because the fingerprint is computed from the device itself, it persists after cookies are cleared and can follow a user across sites that share a fingerprinting provider.
Fingerprinting matters in two directions. For privacy, it means clearing cookies or using private windows does not reset your identity, since the underlying signals stay the same. For professional work, it means that two browser sessions on the same machine look like the same device even when cookies are separated. Anyone running QA across configurations, verifying ads by region, or managing client accounts for an agency needs each environment to present its own coherent set of signals, not a copy of the host machine's.
Oculr addresses this with fingerprinting built into the browser engine itself, in native C++, not JavaScript patches layered on top. Controlled surfaces include the user agent, platform, hardware concurrency, device memory, WebGL vendor and renderer strings, client hint metadata, and seeded per-profile noise for canvas, WebGL, and audio output. Each profile presents the same identity on every launch, and every release is regression-tested against public fingerprint test suites and real-device baselines.
