Shield · Privacy

Privacy modes

The mode decides what the SDK stores in the browser and how much it sends about the browser. No mode reads what a visitor types: no passwords, no card numbers, no form values.

strict

Maximum privacy — consent denied or strict regulatory contexts.

No visitor IDNo _fip_vid cookie, no localStorage.
Session-only IDCookie → sessionStorage → the tab's window.name → in-memory fallback.
Minimal browser contextUser agent, language, timezone only. No advanced fingerprinting.
Form metadata and outlineField types, the labels printed on the page, button text. Never values.
No form snapshotWhen strict is the mode you configured, no picture of any form is taken.

balanced default

Recommended for most websites.

Session cookie_fip_sid, 30-minute rolling.
Visitor ID_fip_vid, 30 days, kept in a cookie and in localStorage.
Full page contextPage, referrer, UTM.
Form metadata and outlineField types, the labels printed on the page, button text. Never values.
Form snapshotShield may ask one visitor's browser per form version for a picture of the form with every value blanked, so the dashboard can show what the form looks like. Turn it off with captureFormSnapshots: false.
Standard browser metadataLanguage list, platform, screen and viewport size, whether cookies and touch are available.

advanced

Stronger repeat-visitor detection.

Everything in balancedIncluding the form snapshot.
Retention hintEvents carry the retention hint extended instead of standard.
Hashed IDsCustomer-provided hashed IDs supported, as in every mode.
Same hard floorStill no raw sensitive fields.

In SDK 1.12.0 the browser sends the same fields in advanced as in balanced, and the visitor ID has the same default lifetime (30 days, set by visitorCookieDurationDays).

Consent integration

FindIP.init({
  siteKey: 'pub_xxx',
  consentRequired: true,
  noConsentMode: 'strict', // or 'disabled'
});

When consent is denied: noConsentMode: 'strict' continues in strict mode; noConsentMode: 'disabled' stops all tracking.

One exception in SDK 1.12.0: the form snapshot check reads the mode you configured, not the mode in force after consent was denied. On a balanced or advanced site, a visitor who declined consent can still be the one whose browser is asked for a picture of a form (every value blanked). To rule that out, set captureFormSnapshots: false or use noConsentMode: 'disabled'.

Never collected, in any mode

Form valuesWhat a visitor types or selects in a form: passwords, card numbers and every other field value.
Personal identifiersEmail addresses, phone numbers, names or addresses in plain form.
KeystrokesKeystrokes or mouse recordings.
Screenshots and recordingsA screenshot of the page or the screen, or a session recording. In balanced and advanced the SDK can take one picture of a single form, redrawn empty; Data Collection says exactly what that picture contains and what it can still show.
Page HTMLThe page's HTML is not sent.