fullstory-privacy-controls

Implement Fullstory privacy controls to prevent sensitive data capture.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/rcmaples/btx --skill fullstory-privacy-controls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstory-privacy-controls
Source: https://github.com/rcmaples/btx/tree/main/.claude/skills/fullstory-privacy-controls
Command: npx skills add https://github.com/rcmaples/btx --skill fullstory-privacy-controls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers implement Fullstory privacy controls to prevent sensitive data from being captured during session replay.

Core Features & Use Cases

  • Exclude, Mask, and Unmask modes explained with practical examples to balance privacy and analytics.
  • CSS selector rules, Form Privacy, Private by Default, and guidance for mixed content scenarios.
  • Use Case: Integrate privacy controls into a banking UI to protect PII while preserving navigation analytics.

Quick Start

Start by implementing the fs-exclude on highly sensitive fields, apply fs-mask to PII where needed, and reserve fs-unmask for safe UI elements; verify results in the Fullstory privacy settings.

Frequently Asked Questions about fullstory-privacy-controls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Fullstory privacy controls to prevent sensitive data capture in session replay?

Fullstory privacy controls prevent sensitive data capture during session replay by using Exclude, Mask, and Unmask modes. You apply fs-exclude to highly sensitive fields, fs-mask for PII, and fs-unmask for safe UI elements to balance privacy with analytics.

What is the difference between fs-exclude, fs-mask, and fs-unmask CSS selectors?

fs-exclude removes elements entirely from session replay, fs-mask conceals text content while preserving layout, and fs-unmask reveals safe UI elements. These CSS selector rules balance strict privacy compliance with actionable analytics data.

How do I configure Fullstory Form Privacy and Private by Default for a banking UI?

Configure Form Privacy and Private by Default to protect PII in banking UIs by masking all text inputs automatically. You then selectively apply fs-unmask to safe elements to preserve user navigation analytics without exposing sensitive financial data.

Can I use Fullstory data privacy controls for mixed content scenarios on web applications?

Yes, Fullstory data privacy controls support mixed content scenarios across web applications. You combine CSS selector rules with Exclude, Mask, and Unmask modes to handle dynamic content while meeting compliance requirements and preventing PII capture.

How do I test and troubleshoot Fullstory privacy settings to ensure PII is not captured?

Test and troubleshoot Fullstory privacy settings by verifying CSS selector rules and Form Privacy configurations within the Fullstory privacy settings interface. This ensures fs-exclude and fs-mask properly prevent sensitive PII capture during active session replay.