fullstory-privacy-controls

To configure Fullstory privacy controls, apply a three-mode model using fs-mask for PII fields like names and emails, fs-exclude for highly sensitive inputs like passwords, and fs-unmask for non-sensitive navigation elements to ensure compliant data collection.

Element inheritance ensures children automatically inherit parent privacy rules across web and mobile platforms. When conflicts arise, the most restrictive rule prevails, meaning a masked parent will keep child elements masked even if marked for unmasking.

Yes, Fullstory privacy controls support PCI and HIPAA compliance on mobile apps by applying platform-agnostic rules. You can exclude sensitive health or payment data from sessions while selectively unmasking navigation elements to analyze user funnels.

The best way to implement a Private by Default deployment is to exclude or mask all data by default, then selectively apply fs-unmask only to specific navigation and product data elements needed for analytics, verifying the replay results afterward.

An fs-unmask rule may not work on child elements because Fullstory privacy controls enforce restrictive inheritance. Children inherit parent rules, and the most restrictive rule prevails, meaning an fs-mask on a parent overrides any fs-unmask attempts on its children.

You use a platform-agnostic three-mode model for the core logic, but you need platform-specific implementations for web and mobile. The Skill defines the inheritance rules generally, then links to specific execution files for each platform environment.