Set up your bannerConfigure Your ToolsSession Recording and Heatmaps

Fullstory

How to configure Fullstory at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service

Overview

This guide explains how to implement different privacy configurations for Fullstory and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The Fullstory browser snippet (fs.js) for session replay and digital experience analytics. Fullstory, Inc. is a US company.

What the service does in this scope. fs.js attaches listeners to browser events to recreate sessions. The first-party fs_uid cookie (1 year) groups sessions for anonymous users and tracks the user across sessions and pages; fs_cid (1 year) stores the consent state. Capture can be delayed until consent with _fs_capture_on_startup = false and started with FS('start'). Fullstory's default is to capture (unmask) content, unless the account uses Private by Default, where text is masked unless explicitly unmasked. Calling FS('setIdentity', { uid, … }) links sessions to a known user.

Legal role. Fullstory is controller only for its own domains; for customer sites it acts as processor under its DPA.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskPrivate by Default; anonymous users only; capture starts after consent.
Configuration B — Higher riskStandard capture (unmask by default, blocklist with .fs-mask / .fs-exclude); setIdentity with user ID and email; capture after consent.

No configuration without prior consent. fs_uid persists for a year; no consent-free configuration is documented.

Step 1 — Configure Fullstory

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service
2Capture startwindow['_fs_capture_on_startup'] = false before the snippet; FS('start') in the Consenter callbackAfter consentAfter consent
3Privacy modePrivate by Default (onboarding or via Fullstory Support)Private by DefaultStandard (blocklist)
4Element rulesSettings > Data Capture and Privacy > Privacy (.fs-exclude, .fs-mask, .fs-unmask)Unmask only non-personal elementsMask/exclude sensitive elements
5User identificationFS('setIdentity', { uid, properties })Not usedUsed (user ID, display name, email)
6Data regionAccount data centre (EU option)EUEU or US
7WithdrawalFS('shutdown') on withdrawalConfigureConfigure

Step 2 — Map the configuration in the Consenter Manager

Processing location. Fullstory, Inc. is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential processing and access location in all configurations.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiers, IP addressDevice identifiers, IP address, Authentication-derived identifiers, Direct identifier
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP addressBrowsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided data, direct identifier, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationCookie 1 year; data per contractCookie 1 year; data per contract
Processing locationEU data centre; United States as potential access locationEU or US data centre; United States as potential access location

Privacy-policy follow-up

  • Fullstory as processor; session replay; cookies fs_uid, fs_cid; masking mode; identification (B); data centre; US provider and potential access by US authorities.

Verification checklist

  • No fs.js capture or fs_uid before consent.
  • Replays reviewed for unmasked personal data.
  • FS('shutdown') on withdrawal.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page