Public pages use no advertising trackers. The secure portal uses an essential session cookie and the service providers described in our privacy policy.

Skip to main content
← Back to Resources
Remediation·November 2, 2026·3 min read

Session Replay on Healthcare Sites: Masking Settings by Vendor

A source-based guide to Clarity, Fullstory and Hotjar masking controls, what masking changes, and how healthcare web teams can verify their configuration.

PR
Privacy Resolve
Last reviewed November 2, 2026

Session replay can collect a representation of a page and the visitor's interactions with it. Masking changes selected content before the vendor receives it. Excluding an element or a page can apply a different boundary. The exact setting, the page's content and the behavior actually observed all matter.

For a healthcare website, begin with a clear question: which pages and interactions should this vendor receive at all? A masked text field is one setting within that wider decision.

Three controls to distinguish

Masking replaces selected content with a substitute. Depending on the product, other information about the element or the interaction may still be collected.

Exclusion or page targeting limits which elements or pages are included. Check each vendor's definition rather than treating these words as interchangeable.

Consent control determines whether collection is allowed to begin or continue under the site's chosen consent design. Masking and consent are separate controls. A masking setting alone does not demonstrate that a refusal stopped vendor contact.

Microsoft Clarity

Microsoft documents three site-wide modes: Strict masks all content, Balanced masks content it classifies as sensitive, and Relaxed leaves page content visible while still masking input boxes and dropdowns. Balanced is the documented default. Input boxes and dropdowns are masked in every mode.

Administrators can also configure element rules or use the documented masking attributes. Microsoft says changes apply to new recordings, may take up to an hour and cannot alter earlier recordings. Review the rules that apply to actual condition names, appointment details and other sensitive text displayed outside input fields.

Source: Microsoft Clarity masking documentation.

Fullstory

Fullstory distinguishes Exclude, Mask and Unmask. With Private by Default enabled, text is masked unless allowed. Its documentation says masked text is transformed before collection, while interaction events involving masked elements can still be captured.

Exclusion is more restrictive: excluded elements and their children are omitted, including interaction events directed at them. Fullstory also says web images cannot be masked, so images requiring protection should be excluded. Inspect the account's selected privacy mode, URL rules, element rules and any permitted exceptions.

Sources: Private by Default and Fullstory privacy settings.

Hotjar and Contentsquare

Use the documentation for the actual platform in the account. Contentsquare's current guidance for insights.hotjar.com describes site-wide, page-specific and element-specific suppression, including text and images. It states that suppression occurs before the session is sent and that later setting changes do not apply retroactively.

The same page directs app.contentsquare.com customers to separate masking instructions. Confirm the platform and the active settings rather than relying on an older Hotjar checklist or a product name alone.

Source: Contentsquare guidance for suppressing collected data.

Check the wider data flow

Review the page address, visible page content, interaction information and any identifiers separately. Also check other vendors on the page and any server-to-server forwarding. A replay vendor's masking rules do not govern those separate routes.

Use a controlled test environment with dummy information. Compare behavior before a consent choice and after rejection, and repeat after the documented setting changes take effect. Review both the information leaving the browser and what appears in the vendor account. Keep the time, affected page, applicable settings and observed result together.

Do not put real patient information into a test or submit a live intake, appointment or contact request to check a replay configuration.

What to retain after making changes

  • The product and account or project whose settings changed.
  • The affected pages and elements, including content outside form fields.
  • The privacy mode, exclusion rules, exceptions and consent configuration.
  • The change date, the time a new test was run and the result observed.
  • The separate review of other browser recipients and server-side forwarding.

Retest when layouts, forms, integrations or vendors change. A setting that matched the old page may not cover a newly added element.

See Does Your Reject Button Actually Stop Tracking? for the refusal test and Remove Unauthorized Website Trackers for a broader remediation sequence.

Sources

Vendor documentation and links checked on November 1, 2026. Product controls can change, so review the current documentation and the account's actual settings before making a change.

General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.