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.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Private by Default; anonymous users only; capture starts after consent. |
| Configuration B — Higher risk | Standard 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 area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Capture start | window['_fs_capture_on_startup'] = false before the snippet; FS('start') in the Consenter callback | After consent | After consent |
| 3 | Privacy mode | Private by Default (onboarding or via Fullstory Support) | Private by Default | Standard (blocklist) |
| 4 | Element rules | Settings > Data Capture and Privacy > Privacy (.fs-exclude, .fs-mask, .fs-unmask) | Unmask only non-personal elements | Mask/exclude sensitive elements |
| 5 | User identification | FS('setIdentity', { uid, properties }) | Not used | Used (user ID, display name, email) |
| 6 | Data region | Account data centre (EU option) | EU | EU or US |
| 7 | Withdrawal | FS('shutdown') on withdrawal | Configure | Configure |
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 field | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers, IP address | Device identifiers, IP address, Authentication-derived identifiers, Direct identifier |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address | Browsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided data, direct identifier, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Cookie 1 year; data per contract | Cookie 1 year; data per contract |
| Processing location | EU data centre; United States as potential access location | EU 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.jscapture orfs_uidbefore 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