Operating several access points while contributing safety infrastructure

Google

Google appears across this network as a platform operator, a supplier of identity-related infrastructure and a participant in safety-policy work. Its services can supply age information, control app distribution, disclose records to investigators and incorporate external safety assessments into search.

Google appears in several parts of this investigation because it operates services that other people and institutions depend on. Its roles include app distribution, search, payments and identity-related infrastructure. Each supplies a different practical capability, from determining what can be distributed to providing information a service uses to assess a user's age.

Its Google Wallet documentation describes an ID-pass route involving passport and face checks before information is shared. Google also publicly endorsed California's age-assurance legislation in September 2025. These records place the company on both the implementation and policy sides of age assurance: it supplies a technical route and participates in the argument over what services should be expected to do.

Its safety work has wider institutional connections. Google has WeProtect board representation and participated in the World Economic Forum's digital-safety principles group. Tech Against Terrorism credits Google Jigsaw with collaboration on Altitude, and ROOST names Google among its founding partners. These connections help circulate expertise and reusable tools across organizations.

Government interaction is concrete too. A sworn declaration reports that Google produced records in June 2025 concerning services investigated by San Francisco. Separately, Google's September 2025 StopNCII announcement described a planned rollout for search; completion was not established in the retained follow-up. Its structural importance is this breadth: Google can supply evidence, implement policy and decide how information travels through services used at enormous scale.

Assessment updated 2026-09-12

Detailed records and research

What the records show

22 August 2025 NCII payment-platform letterGoogle

requests proactive NCII seller payment-authorization removal

Letter dated 22 August 2025; announcement 26 August. Actual dispatch/receipt and response not acquired.

Addressed to Google Pay legal representatives: asks present controls and further action enforcing existing terms/acceptable-use policies against sellers of deepfake NCII tools/content. Seller-level scope; no named bank instruction, adjudication, compulsory response deadline or confirmed receipt/implementation. Not a general pornography ban.

GoogleWeProtect Global Alliance

Institutional board representation

Read 7 Sep 2026

Current published board participation, not an ownership share or evidence of a campaign-specific payment.

GoogleGoogle Canada age-assurance rollout

Announces Canadian rollout

Checked 14 September 2026; signature date unresolved

Google announces gradual rollout beginning in coming days.

GoogleAltitude — inspected public implementation

was named as Jigsaw collaborator in Altitude development

2024-07-22 – 2024-07-22

TAT announcement and reviews attribute co-development to Google Jigsaw and continuing advisory support. Existing Google identity reused with Jigsaw scope; no current unilateral repository veto, deployment or Canadian allocation inferred.

GoogleSan Francisco City Attorney’s Office

reportedly produced responsive records to a subpoena

2025-06-06 – 2025-06-06

Counsel says Google LLC produced records on6 June 2025 concerning ClothOff and Drawnudes. The declaration is primary sworn testimony about production; actual subpoena/production not acquired. No app, domain or payment shutdown implied.

GoogleSF Apple/Google notices — July 2026 reporting

reported five identified app suspensions through a spokesperson

Reporting/update date; individual suspension dates unestablished.

WIRED publishes Google’s account that five identified apps were suspended. This is a company statement connected to the SF intervention, not independent availability measurement or proof of bank/payment action.

From the investigation

Methods and data boundaries

Document-version trap: search returned a cached June 23 variant of Discord's central page saying Google shares birthdate transiently with Discord and listing an Incode test. The live canonical August 10 page instead says age group + country and omits Incode. Use the live version for current claims; do not silently mix them or infer the engineering change/date from wording alone.

Read the research & sources ↗
Candidate relations and next decisive record

For integration, reuse the existing CCF, Columbia, Discord, OpenAI, Google, Roblox, Tech Coalition and other exact identities where they resolve. The meaningful new relationship types are incubation , advertised employer , named board/technical role , appoints , roadmap authority , merge/release authority , fundraising reported and collaboration/expertise reported . Avoid converting the entire roster into control edges. The Canadian edge remains a CCF award with an expected partnership purpose.

Read the research & sources ↗
Findings and locators

The sworn declaration supports a motion for alternative service on Sol Ecom, not a Briver compliance certification. Paragraphs18–23 report subpoenas and responsive contact records from Cloudflare, Namecheap and former registrar Name.com. Paragraph29 reports Google's June6,2025 production. Paragraphs24–30 describe subsequent notices and correspondence. These are counsel's sworn accounts; actual subpoena and production instruments are not attached in this read scope. They establish a reported disclosure route, not provider shutdown instructions.

Read the research & sources ↗
Integration decision

Retain these findings as a sourced intake pending the next atlas content revision. Highest-priority new node: ICMEC, with distinct financial-programme donor, legislative-sponsor and technical-proposal relationships. New infrastructure nodes include Windows age-signaling, k-ID, Veratad, Google Wallet and IDScan.net/VeriScan. Never connect IDScan to Discord without a separate source. Priority questions concern programme earmarks, drafting provenance, provider admission, credential refusal/correction, retention and deletion duties. No public release or automated restart occurred.

Read the research & sources ↗

Further reading

Discord age assurance: transcript verification

Steam transcript intake: age credentials, policy sponsorship, and data custody

Public officials ask payment networks to use private rules

Baseline evidence custody

ROOST: governance, operational home and funding

Provider disclosure and an attributed Australian lead

San Francisco notices: the original remains a specific gap

Partner access, contributions and downstream actions

Altitude: product governance and correction boundaries

TCAP: reported delivery from alerting to reusable infrastructure

Read the original sources 13

What the connections say

12 relationships
4

Googledocuments prior passport and face proofing for its ID-pass routeGoogle Wallet

Observed 2026-09-08

Reported by the cited source

A minimal downstream signal can depend on earlier identity proof; these are separate disclosures.

Read the original source 1
5

22 August 2025 NCII payment-platform letterrequests proactive NCII seller payment-authorization removalGoogle

Letter dated 22 August 2025; announcement 26 August. Actual dispatch/receipt and response not acquired.

Addressed to Google Pay legal representatives: asks present controls and further action enforcing existing terms/acceptable-use policies against sellers of deepfake NCII tools/content. Seller-level scope; no named bank instruction, adjudication, compulsory response deadline or confirmed receipt/implementation. Not a general pornography ban.

Read the original source 1
7

Googlereported five identified app suspensions through a spokespersonSF Apple/Google notices — July 2026 reporting

Reporting/update date; individual suspension dates unestablished.

Reported by the cited source

WIRED publishes Google’s account that five identified apps were suspended. This is a company statement connected to the SF intervention, not independent availability measurement or proof of bank/payment action.

Read the original source 1
9

Googlewas named as Jigsaw collaborator in Altitude developmentAltitude — inspected public implementation

2024-07-22 – 2024-07-22

Reported by the cited source

TAT announcement and reviews attribute co-development to Google Jigsaw and continuing advisory support. Existing Google identity reused with Jigsaw scope; no current unilateral repository veto, deployment or Canadian allocation inferred.

Read the original sources 3
11

Googleannounced an intended following-months rolloutStopNCII

2025-09-17 – 2025-09-17

Reported by the cited source

17September2025Googleannouncement describes planned hash use. No completion record in bounded follow-up; not proved implemented use.

Read the original source 1