MEET FINGERLYA clearer picture of every session.Explore the signals
Private browsing signals

Private. Not invisible.

A private window resets cookies, not the device. Fingerly reports when a session runs in a private window, keeps recognising the device behind it, and weights the finding as context rather than as a verdict.

  • Chromium browsersChrome, Edge and Brave.
  • FirefoxStandard and strict protection.
  • SafariOn macOS and iOS.
  • Privacy settingsBrowsers set up for privacy.
Private browsing

Know when storage keeps resetting. Metered paywalls, trial limits and one-per-customer offers all break in a private window. Knowing that a session is private explains why a visitor looks new to your cookies, while the visitor ID still recognises the device.

  • Private windows in Chromium browsers, Firefox and Safari
  • Validated in ordinary and private windows side by side
  • Tor Browser reads as private, as it should
  • Reported with a confidence and a low default weight

Two signals. Both web only.

Native apps have no private window, so these signals exist only for browsers. Both ship with modest weights.

SignalWebAndroidiOSWhat it means
Incognito mode4n/an/aThe session runs in a private browsing window.
Privacy settings6n/an/aThe browser is configured for privacy, such as blocked trackers or refused cookies.

Privacy settings needs several clues together before it fires, because most people who set them up are simply privacy-conscious.

A clue, never a verdict.

Plenty of people browse privately for ordinary reasons: a shared computer, a gift, a medical question. That is why incognito ships with a default weight of 4, well short of the threshold of 30, and why privacy settings sits at 6.

Browsers change how private windows behave. When a browser change makes a private-window clue unreliable, the rule is to stop reporting it rather than to report ordinary windows as private. A missed private window costs one detection; a wrong one costs trust in the whole score.

  • Low default weights, yours to change
  • The visitor ID is unaffected by private windows
  • Unreliable clues are withdrawn, not guessed

Privacy mode alone is never a fraud verdict. Read it alongside the device, the network and what the account is trying to do.

Where private windows reset the rules.

Most of the value is explaining behaviour your cookies cannot, at the moments limits are enforced.

  1. 01Metered paywalls
  2. 02Free trials
01

Metered paywalls

The meter follows the reader.

Count free articles against the visitor ID instead of a cookie, and use incognito as the reason a reader looks new.

Check at
Article views
Signals
Incognito modeVisitor ID
Paywall enforcement
02

Free trials

A fresh window is not a fresh customer.

A returning device in a private window starting another trial is worth a look before the trial is granted.

Check at
Free trial startSignup
Signals
Incognito modeVisitor IDNew or returning
New account fraud

About private browsing.

What incognito detection covers, and how to use it fairly.

Talk to the team
Does the visitor ID change in a private window?

Identity does not depend on cookies or browser storage, so a private window is recognised as the same device in the ordinary case. Browsers that randomise what they report are recognised less often, and the response says when it could not identify anyone.

Which browsers are covered?

Private windows in Chromium browsers such as Chrome, Edge and Brave, in Firefox, and in Safari on macOS and iOS. Coverage follows how each browser behaves, and a clue that stops being reliable after a browser update is withdrawn rather than guessed.

Should I block visitors in private windows?

Rarely. Private browsing has many innocent uses. Use it to explain why a returning visitor looks new, and to add context at trial starts and metered limits.

[ IDENTIFY ][ UNDERSTAND ][ DECIDE ][ FINGERLY ]
Less guessing. More knowing.

Make the next connection a trusted one.

Start with the signals, keep your own decisions, and pay only for what you identify. No credit card needed.