Privacy and data use.

The website and videos.

The public website uses no third-party advertising or analytics scripts, remote fonts or tracking cookies. The demonstrations use no browser storage. If you choose to send a contact message, it is sent to the project’s chat service as described below. The demonstrations use invented information in page memory. Videos, captions and images are served from this website.

Google Cloud hosts the website and processes technical request information needed to deliver it, such as IP address, requested page, time and browser details. The project’s default infrastructure log retention is 30 days. This is separate from chat records described below.

Contact messages.

When you select Send message, the contact page sends your chosen topic, message and optional reply email to chat.wiretaplitigation.com. The project stores them in a private inbox in Google Cloud. Public visitors cannot read submissions. Sending does not authorize publication of your identity, story or organization.

Anti-abuse controls use a keyed hash of a network-derived client identifier. Contact messages expire after 30 days; a daily cleanup removes expired records, ordinarily within 31 days. Service outages can delay cleanup. A receipt confirms storage for project review; it does not promise a reply. Save a copy downloads the note to your device without submitting it.

The research assistant.

“Ask a question” opens chat.wiretaplitigation.com, a separate application. It sends your question and conversation context to its configured AI service to generate a response. Questions, answer excerpts, tool activity and service diagnostics may be recorded in the application database. First-turn questions and responses may also be cached for reuse with matching queries. These records are not anonymous submissions merely because the page does not ask for your name.

Chat also loads third-party interface assets. Rate limits and other abuse controls may process network or session information. Do not submit confidential case details or sensitive personal information. Refreshing or starting a new conversation clears the visible conversation; it does not delete server records.

Chat query records and answer-cache entries created on or after September 25, 2026 at 20:51 UTC expire after 30 days. Expired cached answers are excluded from reuse; a daily cleanup removes expired records, ordinarily within 31 days. Service outages can delay deletion. Earlier chat records retain their previous policy and have no automatic deletion date. Infrastructure logs have the separate 30-day retention described above.

The deletion schedule applies to the active application database. Recovery copies age out separately: the current configuration retains seven automated database backups and seven days of recovery logs.

Links to other sites.

Source links open independent websites with their own data practices. A link is not an endorsement of their policies.

Contact the project about this notice. Include only the details needed to explain your question.