Know what’s on your site before a plaintiff’s firm does
A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.
Website analytics software has become the subject of an increasingly expensive wave of privacy litigation. Among the companies caught in the middle is FullStory, Inc., commonly branded as Fullstory, a provider of digital experience analytics and session replay technology that allows businesses to reconstruct how visitors interact with websites and mobile applications.
What began as a series of consumer privacy lawsuits alleging unauthorized interception of electronic communications has evolved into a broader legal problem involving software vendors, website operators and their insurance carriers.
In August 2026, Evanston Insurance Company, part of Markel Group, filed a federal lawsuit concerning $5 million in disputed insurance coverage for Fullstory. According to reporting on the complaint, Fullstory maintained that its legal defense costs had already exceeded $10 million. Bloomberg Law reported that Fullstory had faced at least 30 proposed class actions.
For businesses using Fullstory, Hotjar, Microsoft Clarity, Contentsquare, Mouseflow, Smartlook, Lucky Orange and similar technologies, the litigation raises an uncomfortable question: Is the financial benefit of recording website visitors worth the potential legal exposure?
The answer increasingly depends on how these technologies are configured, when they begin collecting information, what information they transmit and whether the website operator has obtained legally sufficient consent.
What is Fullstory and why is it being sued?
Fullstory provides behavioral analytics software that helps businesses understand how customers interact with their digital properties. Product managers, marketing departments, developers and user experience teams use the platform to identify website errors, abandoned shopping carts, customer frustrations, conversion problems and usability issues.
Unlike conventional analytics platforms that primarily report aggregate traffic statistics, session replay technology can reconstruct individual browsing sessions. Depending on the implementation and privacy configuration, session replay software may collect:
- Mouse movements, clicks and scrolling activity.
- Interactions with forms and search fields.
- Page navigation and browsing sequences.
- Text entered into website elements, potentially before submission.
- IP addresses, device characteristics and approximate location.
- Changes to the document object model (DOM).
- Customer identifiers and information supplied through integrations.
- Network information and application error logs.
The technology does not necessarily record a literal video of a visitor’s screen. Instead, it collects information about the structure of a webpage and the visitor’s interactions, allowing the session to be reconstructed later.
This distinction is technically important, but it does not necessarily resolve the legal questions surrounding interception, consent and third-party access. Plaintiffs’ attorneys have argued that the simultaneous collection and transmission of website interactions to external software providers constitutes unlawful electronic surveillance under federal and state privacy laws.
Fullstory and other session replay providers have disputed such characterizations, and several courts have dismissed claims against the technology providers or their customers. Nevertheless, successful defenses have not prevented additional lawsuits.
Fullstory’s $5 million insurance coverage lawsuit
On August 4, 2026, Evanston Insurance Company filed Evanston Insurance Company v. FullStory, Inc., Case No. 2:26-cv-08618, in the U.S. District Court for the Central District of California. The insurer sought a declaratory judgment concerning its obligations under a $5 million excess insurance policy.
The dispute centered on whether Fullstory had properly exhausted the underlying insurance coverage necessary to trigger the excess policy. According to Insurance Business, Fullstory claimed that its defense expenses had exceeded $10 million. Evanston disputed whether the expenses qualified toward exhaustion of the underlying coverage.
Two days later, on August 6, 2026, Fullstory filed its own lawsuit against Evanston in the Northern District of Illinois. The case, FullStory, Inc. v. Evanston Insurance Company, Case No. 1:26-cv-09416, alleged breach of an insurance contract.
The competing lawsuits illustrate a problem facing businesses throughout the digital advertising and analytics industries. Purchasing cyber insurance does not automatically guarantee that every privacy-related lawsuit, defense invoice or settlement will be covered.
The $10 million figure represents reported defense expenses asserted by Fullstory, not a regulatory fine or damages award. The insurance dispute itself does not establish that Fullstory violated any privacy statute.
For cyber insurers, however, the litigation offers a concrete example of how wrongful collection claims can generate substantial legal expenses without a conventional cybersecurity incident. A ransomware attack, stolen credentials or compromised server is not required. The underlying allegations concern the operation of software that businesses intentionally installed on their own websites.
Fullstory privacy lawsuits and court decisions
Fullstory has been involved in litigation directly as a defendant and indirectly through lawsuits against businesses accused of deploying its software. Several decisions provide insight into how courts are evaluating these claims.
Graham v. Noom and Fullstory
In Graham v. Noom, Inc., 533 F. Supp. 3d 823 (N.D. Cal. 2021), plaintiffs sued weight-loss platform Noom and Fullstory over allegations that session replay software unlawfully intercepted communications between consumers and Noom’s website. The plaintiffs asserted claims under the California Invasion of Privacy Act (CIPA).
On April 8, 2021, U.S. District Judge Laurel Beeler granted motions to dismiss. The court reasoned that the plaintiffs had not adequately alleged that Fullstory was independently eavesdropping rather than providing a service that enabled Noom to record and analyze its own customer interactions.
A website operator may argue that a session replay provider acts as its service provider or technological extension rather than an independent third-party interceptor. Plaintiffs, on the other hand, frequently argue that the vendor’s independent access to information, its technical capabilities or its contractual data-use rights make it a third party to the communication.
Different courts have taken different approaches to this question. Businesses should not assume that the reasoning in Graham will automatically dispose of every CIPA claim involving session replay software.
Hasson v. Fullstory and the Mattress Firm website
In Hasson v. FullStory, Inc., Pennsylvania resident Kenneth Hasson alleged that Fullstory intercepted his electronic communications while he visited the Mattress Firm website. The lawsuit asserted claims under Pennsylvania’s Wiretapping and Electronic Surveillance Control Act and common-law privacy principles.
A federal district court initially dismissed the lawsuit in 2023 for lack of personal jurisdiction. On September 5, 2024, the U.S. Court of Appeals for the Third Circuit vacated that dismissal and sent the case back for further consideration of Fullstory’s contacts with Pennsylvania.
The appellate decision did not establish that Fullstory had unlawfully intercepted communications. It addressed whether the company could be sued in Pennsylvania. The decision nevertheless illustrates the difficulty of relying exclusively on jurisdictional defenses when software is deployed across websites accessible to consumers throughout the United States.
Schnur v. Papa John’s International
The Third Circuit considered Schnur v. Papa John’s International, Inc. alongside the Hasson appeal. The plaintiff alleged that Papa John’s used Fullstory session replay technology to intercept visitors’ electronic communications without their consent.
Unlike the Hasson case, the appellate court affirmed the dismissal of the lawsuit against Papa John’s for lack of personal jurisdiction. The two outcomes illustrate how similar allegations involving the same technology can produce different procedural results. Neither outcome established a nationwide legal exemption for businesses utilizing session replay software.
Oliver v. Noom: Another Fullstory-related lawsuit in 2026
On July 10, 2026, a Pennsylvania federal court dismissed another proposed class action involving Noom’s alleged use of Fullstory. In Oliver v. Noom, Inc., Case No. 2:22-cv-01857, plaintiff Ariel Oliver alleged that Noom’s website incorporated session replay technology capable of collecting detailed visitor interactions and potentially personal information.
U.S. District Judge William S. Stickman IV determined that the plaintiff had not sufficiently pleaded an injury necessary to establish federal standing. The court permitted the plaintiff to amend the complaint. For defendants, standing remains an important defense in website tracking litigation. For businesses, however, even a successful motion to dismiss can follow years of litigation and considerable legal expense.
Which privacy laws apply to Fullstory and session replay software?
Unlike traditional data breaches, session replay lawsuits frequently rely on statutes originally enacted to address telephone wiretapping and electronic surveillance. Attorneys have adapted those statutes to modern digital tracking technologies.
| Privacy law | Potential exposure |
|---|---|
| California Invasion of Privacy Act (CIPA) | Unauthorized interception, eavesdropping and certain tracking-device allegations |
| Electronic Communications Privacy Act (ECPA) | Interception of electronic communications |
| Pennsylvania Wiretapping and Electronic Surveillance Control Act | Interception without legally sufficient consent |
| CCPA/CPRA | Improper disclosures, opt-out failures and processing violations |
| GDPR and European ePrivacy rules | Unlawful processing, insufficient consent and excessive collection |
| Washington My Health My Data Act | Collection or sharing of consumer health information |
| Video Privacy Protection Act (VPPA) | Certain disclosures linking consumers to video-viewing activity |
| State consumer protection statutes | Misleading privacy disclosures or unfair business practices |
| Common-law intrusion upon seclusion | Allegedly offensive intrusions into private activity |
Not every law applies to every implementation. Liability depends on the information collected, the parties receiving it, the applicable jurisdiction, the purpose of processing and the surrounding circumstances.
California Invasion of Privacy Act
CIPA remains one of the most frequently invoked statutes in website tracking litigation. California Penal Code Section 631 addresses certain forms of wiretapping and unauthorized interception of communications.
Section 638.51, which regulates pen registers and trap-and-trace devices, has also become the subject of extensive litigation involving website tracking technologies, although its application to ordinary website analytics remains contested.
Under Section 637.2, qualifying CIPA violations can carry statutory damages of $5,000 or three times actual damages, whichever is greater. The availability and calculation of damages depend on the specific claim and the court’s findings. Businesses receiving CIPA demand letters may therefore face settlement demands substantially greater than the cost of the software that allegedly caused the violation.
Federal Electronic Communications Privacy Act
The federal Wiretap Act, as amended by ECPA, prohibits certain intentional interceptions of electronic communications. Litigation involving session replay software frequently centers on whether the technology intercepts the contents of communications contemporaneously, whether the vendor is a party to the communication and whether valid consent exists.
The federal statute contains exceptions and defenses, including certain circumstances involving party consent. Nevertheless, the operation of session replay software before a visitor receives a privacy disclosure or makes a consent decision creates an avoidable legal vulnerability.
Recent privacy fines and regulatory actions businesses should know about
Private class-action litigation is only one component of the financial risk associated with website tracking. State attorneys general, federal regulators and European data protection authorities are also scrutinizing the collection and disclosure of consumer information through digital technologies.
The following enforcement actions involve broader website tracking and data-sharing practices. They should not be interpreted as findings against Fullstory itself.
Polaris: $1.06 million in coordinated privacy enforcement
On November 19, 2026, Minnesota Attorney General Keith Ellison announced a $150,000 settlement with Polaris Industries following an investigation under the Minnesota Consumer Data Privacy Act. The California Privacy Protection Agency, also known as CalPrivacy, imposed an additional $910,986 administrative fine.
According to the Minnesota attorney general’s announcement, some website trackers failed to honor browser-based privacy signals such as Global Privacy Control (GPC). The agency also identified problems with identity verification for opt-outs and required disclosures. The resolution includes quarterly scans and changes to internal compliance procedures.
This is especially relevant to businesses deploying session replay software alongside advertising pixels and other analytics technologies. Regulators are looking beyond the existence of a privacy policy or consent banner and examining whether the underlying technology behaves as represented.
BetterHelp: $7.8 million privacy settlement
Online mental health counseling platform BetterHelp agreed to pay $7.8 million to resolve Federal Trade Commission allegations involving the disclosure of consumer health information for advertising purposes. According to the FTC, the information disclosed included email addresses, IP addresses and responses to health-related questions.
Although the enforcement action did not specifically concern Fullstory, it demonstrates the consequences of allowing sensitive information collected through a website to reach external technology providers. A session replay implementation on a healthcare website, insurance application, fertility platform or online pharmacy could create comparable risks if sensitive interactions were improperly captured or disclosed.
Healthcare tracking technologies under federal scrutiny
In July 2023, the FTC and Department of Health and Human Services issued a joint warning to approximately 130 hospital systems and telehealth providers concerning online tracking technologies. The agencies identified risks associated with the unauthorized disclosure of information about medical conditions, diagnoses, medications, treatments and healthcare visits.
Healthcare organizations should pay particular attention to session replay because it may reveal considerably more context about a visitor’s activities than conventional advertising pixels. Even when text fields are masked, interactions with specific buttons, checkboxes and website elements may reveal sensitive information about an individual.
Fullstory and GDPR: European regulators target session replay
The United States is not the only jurisdiction examining session replay technology. In February 2026, France’s data protection authority, the Commission Nationale de l’Informatique et des Libertés (CNIL), published a draft recommendation specifically addressing session replay tools.
The draft recognizes legitimate commercial applications for session replay, including identifying technical errors, improving website usability and assisting customers experiencing difficulties. However, it also addresses the need to define processing purposes before deployment and configure the technology according to those purposes.
That distinction matters under the GDPR’s principles of purpose limitation, data minimization and data protection by design and by default. A business cannot simply collect an entire browsing session because the technology makes that possible and subsequently decide which information might be useful.
European website operators must also consider applicable ePrivacy requirements governing access to or storage of information on users’ devices. Describing a technology as first-party analytics or cookieless does not automatically exempt it from consent requirements.
Depending on the nature of the infringement, GDPR administrative fines can reach €20 million or 4% of worldwide annual turnover, whichever is higher. The CNIL’s February 2026 document was a draft recommendation, rather than a regulatory fine against Fullstory.
What cookies does Fullstory use?
According to Fullstory’s cookie documentation, the platform uses several first-party cookies and browser storage mechanisms.
| Cookie or identifier | Typical duration | Purpose |
|---|---|---|
fs_uid |
1 year | Associates visitor activity across pages and sessions |
fs_cid |
1 year | Stores the visitor’s Fullstory consent state |
fs_lua |
30 minutes | Records the timestamp of the visitor’s last activity |
_fs_tab_id |
Until tab closes | Session storage identifier supporting multi-tab playback |
Fullstory uses first-party cookies rather than relying on conventional third-party advertising cookies. This configuration offers certain privacy advantages, but businesses should not confuse first-party cookies with strictly necessary cookies. A first-party cookie can still be used to process personal information, facilitate behavioral analysis and associate activity with an identifiable visitor. The classification describes how the cookie operates within the browser, not whether its deployment is legally permissible without consent.
Similarly, disabling cookies does not necessarily prevent other technologies from collecting or transmitting personal information. An effective cookie consent management platform must address the underlying scripts and data collection mechanisms, not simply remove cookies after they have already been created.
Does Fullstory record keystrokes?
According to Fullstory’s technical documentation, the software does not record individual keystrokes in the conventional keylogger sense. Instead, it can capture input change events containing text entered into website fields, subject to privacy configurations.
From a privacy perspective, the difference between recording individual keystrokes and recording the resulting text may provide little comfort to a consumer whose information was collected before submitting a form.
Consider a prospective customer who begins completing an insurance application, enters personal information and subsequently decides not to submit the application. If the relevant input elements were not properly excluded or masked, session replay technology could potentially capture information that the visitor never intended to submit.
This creates particular risks for businesses collecting medical histories, prescription information, financial details, immigration and employment information, legal inquiries, information relating to children, personal identifiers and account credentials. The actual information captured depends on the software configuration, the website’s architecture and the applicable exclusion rules.
Fullstory’s privacy features: Are they enough?
Fullstory offers several privacy controls designed to reduce the risk of collecting sensitive information. Businesses should understand and utilize these features rather than assume the software is inherently noncompliant.
The company’s privacy documentation describes privacy modes and element-level controls that can restrict collection.
| Privacy mode | General approach | Relative collection exposure |
|---|---|---|
| Full Capture | Records eligible content unless restricted | Higher |
| Form Privacy | Adds protections focused on form fields | Configuration-dependent |
| Private by Default | Masks text unless expressly permitted | Reduced |
Masking versus excluding information
Fullstory’s .fs-mask functionality prevents the original text of designated elements from being transmitted, while retaining certain structural and interaction information. Its .fs-exclude functionality provides stronger protection by excluding designated elements and their associated interactions from capture, subject to documented technical limitations.
Imagine a healthcare questionnaire asking whether a visitor has diabetes, cancer, HIV or another medical condition. Masking the text of the questionnaire might conceal the words while preserving information about which options the visitor selected. Someone familiar with the website’s layout could potentially infer the answer.
Businesses should also review HTML attributes, URL parameters, network requests, console logs and custom events. Sensitive information can appear outside the visible text of a webpage. Most importantly, masking is not a substitute for consent. A masked session can still contain identifiers and behavioral information subject to privacy laws.
Does Fullstory start recording before cookie consent?
According to Fullstory’s developer documentation, data capture ordinarily begins once the installation snippet has initialized the software and retrieved the capture script. Fullstory provides mechanisms to delay that process until the visitor grants consent. However, those mechanisms must be properly implemented.
A business that installs Fullstory through Google Tag Manager, a WordPress plugin, a Shopify integration or directly within its website code may inadvertently allow recording to begin before the visitor interacts with the cookie banner.
| Incorrect implementation | Consent-controlled implementation |
|---|---|
| Page loads → Replay starts → Visitor rejects | Page loads → Replay blocked → Visitor grants consent → Replay starts |
| Data may already have been transmitted before the visitor rejects. | If consent is refused, replay remains blocked. |
Fullstory provides a configuration setting to delay capture:
window['_fs_capture_on_startup'] = false;
This setting must be applied before the relevant Fullstory initialization. Once appropriate consent has been obtained, the current Browser API allows data capture to begin:
FS('start');
If consent is subsequently withdrawn, capture can be stopped:
FS('shutdown');
However, the shutdown state does not automatically persist across website page loads. This creates another potential compliance problem for websites that fail to maintain the consumer’s preferences consistently throughout the browsing journey.
A properly configured consent management platform should prevent unauthorized script execution where required, maintain the consumer’s preferences across pages and respond to changes in consent status. Merely invoking Fullstory’s element-level consent API does not necessarily disable all session recording or prevent separately configured customer identity information from being transmitted.
Businesses should distinguish between consent to record a session and consent to capture specific elements within that session.
Why session replay is particularly risky for certain industries
A website selling office furniture generally presents a different privacy risk from a website helping patients determine whether they qualify for addiction treatment.
| Industry | Examples of potentially sensitive interactions | Indicative risk |
|---|---|---|
| Healthcare | Symptoms, diagnoses, medications, appointments | Very high |
| Financial services | Income, debt, account details, financial applications | Very high |
| Insurance | Medical questionnaires, claims, underwriting information | Very high |
| Legal services | Confidential inquiries and descriptions of legal problems | Very high |
| Education | Student records and information concerning minors | High |
| E-commerce | Customer identifiers, shopping behavior, checkout information | Moderate to high |
| Media and entertainment | Viewing activity potentially linked to identifiable consumers | Moderate to high |
| General corporate websites | Contact forms and behavioral analytics | Configuration-dependent |
For some organizations, the appropriate response may be to disable session replay entirely on sensitive pages rather than rely on individual masking rules. Patient portals, authenticated financial dashboards, legal intake questionnaires and insurance application pages deserve particularly careful consideration.
Session replay alternatives face similar litigation risks
Fullstory is far from the only technology provider operating in this market. Other commonly deployed session replay and behavioral analytics platforms include Hotjar, Microsoft Clarity, Contentsquare, Mouseflow, Smartlook, Lucky Orange and PostHog.
Replacing Fullstory with another session replay provider does not automatically eliminate the underlying legal exposure. The relevant questions remain substantially the same. What does the software collect? When does collection begin? Where is the information transmitted? Can the provider use the information independently? What happens when a consumer rejects tracking?
Businesses should evaluate these technologies based on actual network behavior and contractual arrangements rather than marketing claims about privacy compliance. The inclusion of a vendor in this list does not imply that the vendor has violated any law.
The growing problem of wrongful collection for cyber insurers
Historically, many organizations purchased cyber insurance primarily to protect themselves against ransomware, data breaches, business interruption and network security incidents. Website tracking litigation has introduced a different category of exposure: wrongful collection.
Rather than alleging that an unauthorized criminal gained access to company information, plaintiffs allege that the business itself collected or shared information without appropriate authorization. The technology may have operated exactly as designed.
This distinction creates difficult questions for insurance carriers and brokers:
- Does the policy cover unlawful collection as well as unauthorized disclosure?
- Does it cover alleged wiretapping violations and statutory damages?
- Are tracking technologies subject to specific exclusions?
- Are defense costs included within policy limits?
- How are related claims aggregated?
- What happens if underlying coverage is disputed or insufficient?
The Fullstory insurance litigation provides a useful case study because the dispute concerns the financial consequences of defending numerous privacy claims, not simply whether the underlying software can legally operate.
Even if a business ultimately defeats every consumer claim brought against it, the costs associated with attorneys, forensic investigations, discovery and insurance coverage disputes can be substantial. Cyber insurers have a financial incentive to encourage policyholders to identify and remediate problematic website tracking configurations before claims occur.
What happens when a business receives a Fullstory privacy demand letter?
A business accused of unlawfully deploying session replay technology may receive a prelitigation demand letter, an arbitration demand or a proposed class-action complaint. The claimant may allege that the business intercepted private communications, disclosed personal information to an unauthorized recipient or installed tracking technology without obtaining consent.
In many cases, the claimant’s attorneys may seek information concerning:
- The date Fullstory was installed.
- Previous versions of the website and cookie banner.
- Historical privacy policies.
- Contracts and data processing agreements with Fullstory.
- Consent management records.
- The categories of information collected.
- Session recording retention periods.
- Revenue generated through the website.
- Communications with developers concerning privacy configurations.
Businesses should involve legal counsel, notify applicable insurers in accordance with policy requirements and preserve relevant evidence before making changes that could affect litigation.
Remediating a website after receiving a demand letter can reduce future exposure, but it does not necessarily resolve allegations concerning historical activity. Organizations that maintain historical scanning reports, timestamped consent records and documented configuration changes are generally better positioned to investigate such claims than businesses that have no record of how their tracking technologies operated.
How to audit Fullstory for data privacy compliance
Organizations using Fullstory should conduct a technical and legal assessment before assuming their existing configuration is sufficient. The following checklist provides a starting point.
- Identify every website, subdomain and mobile application using Fullstory.
- Test whether Fullstory initializes before the visitor makes a consent choice.
- Confirm that rejecting applicable tracking permissions prevents unauthorized collection.
- Test withdrawal of consent and subsequent page navigation.
- Enable Private by Default or appropriately restrictive capture settings.
- Exclude sensitive pages, forms and account interfaces.
- Inspect network requests, URL parameters, console logs and custom events.
- Review Fullstory’s data processing agreement and permitted data uses.
- Review retention periods, deletion procedures and access permissions.
- Update privacy notices to accurately explain session replay.
- Test applicable Global Privacy Control and state-law opt-out requirements.
- Maintain historical consent records and technical audit reports.
- Review cyber insurance coverage for wrongful collection claims.
- Repeat testing after website, plugin and tag management changes.
Businesses should conduct these assessments using clean browser environments and different geographic locations. A configuration that works correctly for a visitor in California may operate differently for a visitor in Germany or Minnesota.
Testing should also include visitors who ignore the cookie banner, reject optional tracking, return with previously saved preferences or enable browser-based privacy signals.
Frequently asked questions about Fullstory privacy lawsuits
Is Fullstory illegal?
No. Fullstory is not inherently illegal. Session replay technology has legitimate commercial applications and can be deployed with appropriate privacy safeguards. Legal exposure arises from how the software is used, the information it collects and whether applicable privacy requirements are satisfied.
Has Fullstory been sued for wiretapping?
Yes. Fullstory has faced proposed class-action lawsuits alleging unauthorized interception of electronic communications. Litigation has involved California and Pennsylvania privacy statutes, among other legal theories. Several claims have been dismissed, while other proceedings have involved appeals and further litigation.
Has Fullstory been fined $10 million?
The reported $10 million figure concerns legal defense expenses asserted by Fullstory in connection with its insurance dispute. It is not a verified regulatory fine, settlement payment or damages award against Fullstory.
Is Fullstory GDPR compliant?
Fullstory provides privacy controls and contractual mechanisms intended to support GDPR compliance. However, GDPR compliance depends on the individual customer’s implementation, processing purposes, legal basis, transparency practices and other obligations. Purchasing software that offers GDPR compliance features does not automatically make the purchasing organization’s processing lawful.
Does Fullstory require cookie consent?
Where applicable privacy and electronic communications laws require consent for its tracking activities, businesses must obtain valid consent before those activities begin. The answer depends on jurisdiction and implementation. From a litigation risk management perspective, obtaining affirmative consent before commencing nonessential session replay is generally a more defensible approach than recording visitors automatically.
Can Fullstory record passwords and credit card information?
Fullstory provides default exclusions for conventionally coded password fields and certain payment card fields. Businesses should nevertheless verify that customized forms and nonstandard website elements are properly excluded.
Does Global Privacy Control automatically disable Fullstory?
Not necessarily. Businesses must configure their tracking technologies to respond appropriately to GPC and other applicable opt-out mechanisms. Whether GPC legally requires stopping a particular session replay implementation depends in part on whether the processing involves regulated sales, sharing or targeted advertising. Businesses may also choose to apply more restrictive controls.
Can a business be sued for using Fullstory even if Fullstory itself has successfully defended similar claims?
Yes. A lawsuit against a website operator may involve different facts, contractual relationships, jurisdictions and privacy configurations. A prior dismissal involving another business does not provide blanket immunity.
How Captain Compliance helps businesses manage Fullstory and session replay risks
The problem with website privacy compliance is that it rarely involves a single tracking technology. A typical enterprise website may contain session replay software, advertising pixels, chatbots, analytics platforms, embedded video players, customer identification tools and marketing automation scripts.
Each addition or website update creates the possibility that information will be collected or transmitted in a manner inconsistent with existing privacy disclosures or consumer preferences.
Captain Compliance helps businesses identify, monitor and manage these technologies through its privacy compliance platform. Its capabilities include continuous website and cookie scanning, automated script blocking, geographically adaptive cookie consent banners, consent record management, Global Privacy Control support, dynamic cookie policies, privacy notices and data subject rights management.
Rather than relying on a static privacy policy or a cookie banner that merely informs visitors about tracking, businesses should verify that the underlying technology actually respects consumer choices.
For organizations deploying Fullstory, the objective is not necessarily to eliminate session replay. It is to ensure that session replay serves a defined business purpose without creating unnecessary regulatory, litigation or insurance exposure.
Fullstory’s reported eight-figure defense expenses should give every general counsel, chief privacy officer and cyber insurance underwriter a reason to examine how session replay software is being used.
A tool installed to identify why visitors abandon shopping carts should not become the reason a company is defending a multimillion-dollar privacy lawsuit.
Put this into practice
Turn privacy guidance into working controls.
Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.