Georgia Website Tracking, Privacy & Wiretap Litigation

Published by Crandall Consulting · Informational litigation intelligence · Last intelligence update: October 12, 2026

Lawsuits, demand letters, tracked matters, and reported claims are counted separately and are not interchangeable. Last intelligence update: October 12, 2026.

Current Landscape

The supplied Georgia data reports zero tracked lawsuits, zero tracked demand letters, and zero tracked matters, with a risk label of “Lower.” These figures describe the supplied tracking data, not the absence of litigation or legal risk throughout Georgia.

The identified statute is the Georgia Eavesdropping Statute (Ga. Code § 16-11-62). Listed technologies include tracking pixels, Google Analytics, Google DoubleClick, Google Tag Manager, cookies, form-submission tracking, persistent identifiers, and session-replay tools, among other digital features. No case summaries were supplied, so these technologies cannot be connected to specific Georgia allegations, holdings, standing determinations, or procedural rulings.

Current Litigation Activity

Current litigation component: 0/100.

Current Filing & Litigation Trends

No filing trend can be established from the supplied data. The reported counts are zero, and no case summaries or historical counts were provided to assess changes over time.

Precedent Landscape: What Courts Have Decided

Precedent component: 50/100. Litigation activity (volume) and precedential risk (authority of decisions) are measured separately — a high number of filings does not by itself indicate strong plaintiff-favorable binding precedent.

No decided precedent with a clear substantive direction is currently tracked.

A settlement is not a binding precedent, and a procedural dismissal (for example, for lack of standing) is not a holding that the underlying technology is lawful. Where courts disagree, that disagreement is reflected rather than resolved.

Current Laws & Relevant Statutes

• Georgia Eavesdropping Statute — Ga. Code § 16-11-62

Regulatory Enforcement

Regulatory enforcement component: 0/100. Regulatory enforcement (agency investigations, sweeps, settlements, guidance, rulemaking) is tracked separately from private litigation and is never counted as a lawsuit.

No specific enforcement actions are itemized for this jurisdiction.

Agency Guidance

Regulatory trend: insufficient data.

Global Privacy Control / Opt-Out Signals

Limited data

GPC / universal opt-out exposure component: limited data — this component is excluded from the overall risk guideline for this jurisdiction until researched (remaining components are reweighted accordingly).

GPC / universal opt-out privacy rights are a different legal theory from wiretap / interception litigation, though both affect third-party website data flows.

Learn more about Global Privacy Control → · How GPC posture is weighted in the risk guideline →

Changes Coming in the Next 24 Months

Forward-looking (24-month) component: 0/100. Enacted changes with future effective dates may affect a jurisdiction's forward-looking risk, but are not presented as currently enforceable.

Coming Into Effect (Enacted)

No enacted future-effective laws identified in our latest research cycle.

Legislation to Watch (Pending)

No pending website-privacy legislation identified for this jurisdiction in our latest research cycle.

Important Cases & Tracked Matters

No cases are currently tracked for this jurisdiction. This reflects our tracked source set, not an absence of litigation.

Technologies Appearing in Claims

• Website tracking pixels
• Meta pixels
• Google pixels
• Instagram
• Facebook
• Algorithmic feeds
• Age assurance
• Push notifications
• Beauty filters
• Visible like counts
• tracking pixels
• website tracking technologies
• Google Analytics
• Google DoubleClick
• Tracking pixels
• Cookies
• Form-submission tracking
• Other tracking technologies
• session replay code
• session replay / keystroke capture
• tracking technologies (general)
• Google Tag Manager
• persistent Google 'cid' identifier
• Meta Pixel
• session-replay tools

Historical Risk Guideline

What Businesses Should Review

As practical review steps, businesses can inventory any listed technologies they use and document their configurations, collected data, recipients, and purposes. They can also review associated notices, consent flows, vendor arrangements, and access controls. These are suggested review areas, not requirements or conclusions established by any supplied Georgia court decision.

Data Quality

9 source(s), 4 primary; evidence is fresh.

Methodology & Limitations

Statistics on this page are generated by the Crandall Consulting litigation intelligence engine. Publicly available sources (court and government materials, recognized legal press, professional analysis, and industry reports) are discovered through automated web research, classified into a tiered source hierarchy, and reduced to structured facts with full source provenance. Risk guidelines and evidence-confidence scores are computed by a deterministic formula from those stored facts — never by an AI model directly (AI explains findings; it never assigns a score). Counts labeled "tracked" reflect matters identified in our source set and are not official court statistics.

The overall risk guideline is composed of six deterministically weighted components: statutory structure (25%), current litigation activity (25%), prior precedent (18%), GPC / universal opt-out posture (15%), regulatory enforcement (9%), and the forward-looking 24-month horizon (8%). When a state's GPC status is limited data, that component is excluded and the remaining weights are renormalized — limited data never reads as lower exposure. Current litigation activity is measured over recent windows (velocity), not lifetime volume, so a jurisdiction with high historical activity but declining current filings reflects that decline. Litigation activity (volume) and precedential risk (authority of decisions) are measured separately. Full details are on the methodology page.

Sources

• Missouri Attorney General Petition Against H&R Block, TaxSlayer, and TaxAct Concerning Website Tracking Pixels — Missouri Attorney General · Tier A (Primary authority)
• Utah Secures $12.2 Billion Settlement With Meta Over Child Safety Practices — Governor Spencer J. Cox · Tier A (Primary authority)
• $4.25M Wellstar Health tracking pixel class action settlement — Top Class Actions · Tier D (Industry data)
• Doe v. CRH Healthcare, LLC et al, 1:2025cv06353 — Document 35 — U.S. District Court for the Northern District of Georgia, via Justia · Tier A (Primary authority)
• Doe v. Wellstar Health System, Inc. — Wellstar Data Privacy Settlement Administrator · Tier B (Authoritative secondary)
• Doe v. Wellstar Health System, Inc. — Wellstar Data Privacy Settlement Administrator · Tier B (Authoritative secondary)
• Deidun v. Humana, Inc — Lawsuit Complaint (Document #1 Filed 01/23/2026) — DocketNexus · Tier A (Primary authority)
• Planned Parenthood Sued Over Website Trackers That Allegedly Sent Patient Booking Data to Google — OpenClassActions · Tier D (Industry data)
• U.S. Cybersecurity and Data Privacy Review and Outlook – 2025 — Gibson, Dunn & Crutcher LLP · Tier E (General web)

All State Pages