Last updated October 21, 2026

Privacy and data use

How this website and its research assistant handle information, and how to contact the LiveRamp privacy team.

Contacting the Coalition to Halt Abusive Internet Lawsuits

When you submit the contact form, LiveRamp collects your name, email address, reason for contacting us, message, and any optional organization, role, phone, location, organization-type or case-status details you provide. Please do not include patient or customer information, confidential settlement terms, or communications with your lawyer.

We use this information to review your experience or membership inquiry, acknowledge receipt, and arrange follow-up. The designated recipients are Noel at LiveRamp and Michael at Emergent DC, acting for the coalition. Submission does not authorize publication or automatically make an organization a coalition member. We ask for separate permission before publishing your name, organization or story. This form is for coalition follow-up and does not provide legal advice.

Google Cloud stores the private intake records and operates the form and delivery queue. Twilio SendGrid processes the email addresses and email content necessary to send acknowledgments and notifications. We disable email open and click tracking. We do not sell this information or share it for cross-context behavioral advertising.

Coalition representatives may use OpenAI’s AI-assisted tools to review inquiries, prepare draft replies, and research relevant public information about an organization or case before following up. Relevant submission text and business contact information may be processed by OpenAI for that review. Substantive replies and membership or publication decisions remain with coalition representatives. Private message text and contact details are not used as public web-search queries.

Our intake records and delivery status are retained for 90 days and removed by daily cleanup. The database retains seven automated backups and up to seven days of recovery logs, so deleted records may remain in those restricted backups until they rotate out. Provider security and delivery records may have their own retention periods. Email copies and AI-assisted follow-up records follow the representatives’ organizational retention and privacy-request processes and applicable provider terms. These copies are not automatically deleted when the website intake record expires.

The form uses short-lived keyed network and email counters to prevent abuse; they expire after at most 24 hours and are removed on the next scheduled cleanup. It does not set tracking cookies or persist form contents in browser storage. Automated delivery monitoring checks submission references and delivery status without reading your contact details or story. Form submissions are not supplied to the public research chatbot.

LiveRamp’s privacy team handles questions and requests concerning this form. Submit a privacy request to LiveRamp and identify this website and the email used for your submission. The team coordinates applicable requests with the coalition recipients. See the privacy-rights section below for additional information.

Who operates this website

LiveRamp funds, operates and publishes Wiretap Litigation on behalf of the coalition. This notice describes this website’s practices. LiveRamp’s privacy team handles this website’s privacy questions and requests.

No sale, advertising sharing or tracking cookies

We do not sell personal information collected through this website or share it for cross-context behavioral advertising. We do not use it for advertising profiles. Our own pages use no third-party advertising or analytics scripts, remote fonts or tracking cookies. Our explainer videos, captions and images are served by this website. Optional news videos use CBS News or YouTube players and load only when you select a report, as described below. We do not track visitors across other websites, including when a browser sends a Do Not Track or Global Privacy Control signal.

Optional third-party news videos

The opening KPIX report uses CBS News’ official player. Other inline news reports use their publishers’ YouTube channels. A player loads only after you select a report. When you do, your browser connects to that provider, which receives technical information such as your IP address, browser details and the site’s origin. Providers may use browser storage, show advertising and load their own service providers.

CBS playback is subject to Paramount’s privacy policy. YouTube playback uses privacy-enhanced mode at youtube-nocookie.com, which does not make playback anonymous. YouTube may ask some viewers to sign in. YouTube playback and links are subject to Google’s privacy policy. Links to other publishers are subject to those sites’ policies. You can read the business stories and use the rest of this site without loading a third-party news player.

The website and technical information

Google Cloud hosts this website. It processes technical information such as IP addresses, requested pages, browser details and timestamps to deliver and protect the service. Our project excludes new routine request access logs for this website, chat and API from its default logging destination. Sanitized application errors and operational measurements remain available for reliability and security. Short-lived rate-limit counters use keyed network identifiers and expire automatically; they are not used to identify visitors or group conversations.

Existing default infrastructure logs expire after 30 days. Administrative audit logs have separate retention, including Google Cloud’s required 400-day audit retention. Providers may process or retain technical information under their service and security terms. These application changes do not mean that no provider ever receives a network address.

Chat privacy and data use

The research assistant processes the question you enter and the context of your current conversation to answer your questions. Where needed to generate an answer, that information is sent to Gemini through Google Cloud. A message may contain personal information if you include it. Please do not enter personal, patient, customer, confidential or legally privileged information.

For new conversations, our application does not save questions, answers, tool arguments or conversation identifiers in its database. It retains content-free usage records, including token counts, processing time and success or failure, to enforce the daily AI spending limit and operate the service. Those records expire after 30 days and are ordinarily removed by daily cleanup within 31 days. They contain no conversation identifier.

Conversation context and unfinished text stay in the open page’s memory so you can ask follow-up questions. They are not saved in browser storage. Leaving or refreshing the page, selecting New conversation, or 30 minutes of inactivity clears the conversation. Opening the assistant on another page starts a fresh conversation. Earlier browser copies are removed when the updated assistant loads. New free-form answers are not shared among visitors through an answer cache.

Google processes questions and context under its service and security terms. Its currently enabled, project-isolated in-memory cache can retain model inputs and outputs for up to 24 hours; other provider retention depends on applicable settings and terms. We do not promise complete anonymity or zero retention throughout provider systems.

Earlier chat and contact records

On October 9, 2026, we removed previously stored chat text, answer excerpts, tool arguments and conversation identifiers from the active application database, and deleted the retired answer cache. Only content-free usage accounting remains. Older usage records without an expiry were assigned a 30-day expiry at cleanup. A database rule prevents new chat content or conversation identifiers from being saved in those usage records.

The earlier contact form was removed on September 27, 2026. Its messages, topics and optional reply addresses expire after 30 days and are ordinarily removed by daily cleanup within 31 days. Submission did not authorize publication of a sender’s identity, story or organization. Service outages can delay scheduled cleanup. Database recovery copies age out separately: the current configuration retains seven automated backups and seven days of recovery logs.

Maps and external links

Opening a map loads tiles from OpenStreetMap, which receives technical request information including your IP address and the chat site’s origin. Source links open independent websites with their own privacy practices.

Privacy questions and your rights

LiveRamp’s privacy team handles privacy requests for this website. Use Your Privacy Choices for the available request methods, or the contact methods in LiveRamp’s privacy policy. Please identify wiretaplitigation.com in your request so the team can route it to this website’s records.

Depending on applicable law, you may request access to or a copy of your personal information, correction or deletion, and exercise applicable opt-out and sensitive-information rights without discriminatory treatment. Requests may require proportionate verification and are subject to legal exceptions. An authorized agent may submit a request as described in LiveRamp’s California Privacy Notice. We do not collect additional identifying information solely to connect otherwise unlinked chat usage records to you.

LiveRamp’s general notices cover other LiveRamp activities as well. This website’s narrower commitments above—including no sale or advertising sharing of its visitor information—apply to information collected here.

Changes to this notice

We publish updates here with a revised date. We will provide additional notice before introducing materially different collection or uses where required. The contact form includes a notice explaining its collection and use of information.