9 September 2026. Root acquisition CLOSED. StopNCII exposes several distinct gates: admission and payment, reference contributions and feedback, withdrawal processing, and platform action. Published terms are not an executed partner-specific agreement. All observations below concern public administrative records; no live case or operational API was used.
The [join page](http[local research file] offers Approved Participant and Programme Partner routes. Its comparison table assigns both every listed network/support/development benefit. Yet the [Approved Participant page](http[local research file] expressly denies wider programme/network involvement. This is a real description conflict, not evidence of an undisclosed voting arrangement. The [Programme Partner page](http[local research file] advertises active engagement, working groups and opportunities to influence tools/policies; it grants no stated vote or veto.
All four embedded fee/onboarding diagrams were acquired and visually read. Both routes show registration, verification, a data-sharing agreement, payment and integration. The full programme adds meeting the team and announcement. Published annual GBP fees, in the same revenue bands, are:
| Revenue band | Approved Participant | Programme Partner |
|---|---|---|
| New business | 1,000 | 1,000 |
| Below 10 million | 4,000 | 10,000 |
| 10–249 million | 8,000 | 20,000 |
| 250–499 million | 12,000 | 30,000 |
| 500–999 million | 16,000 | 40,000 |
| Over 1 billion | 20,000 | 50,000 |
These are undated published schedules, not invoices, revenue received or proof every earlier partner paid. The wording leaves exact intervening band boundaries unclarified. The user-facing service being free does not establish free organizational access.
[Partner Terms](http[local research file] cover manual and automated admission. They incorporate the unacquired data-sharing agreement and registration form. Sections3–10/schedule specify the lower fee schedule, eligibility/reverification, discretionary refusal, credential controls, security assessment, local caching and access suspension. Redistribution is prohibited; model training has a purpose-limited exception. Permitted purpose depends on the separate agreement. Termination requires cessation/deletion and written certification; annual summaries are due within60days of the access anniversary.
The posting contains conflicting company/charity identifiers, an empty hash-value definition, inconsistent defined-purpose terminology, bracketed implementation/amendment/certification periods and an explicit unfinished implementation note. Do not present those brackets as settled deadlines. Key-compromise notice is24hours; the schedule's general incident notice is48hours—retain their distinct scopes. The five-day certification placeholder concerns partner termination, not each user withdrawal. No signed data-sharing agreement, precedence clause resolving these inconsistencies, executed admission/refusal or payment was acquired. No displayed effective date was established.
[SWGfL privacy](http[local research file] Working with Partners, names Deloitte LLP for business verification and Neterium for sanctions/PEP/watchlist/adverse-media screening. This concerns applicant businesses and connected officials, not identification of people submitting intimate-image cases. The notice describes human consideration of adverse results and rejects solely automated refusals. It promises notice where screening influenced an adverse decision, an uninvolved reviewer on request, correction/annotation and relevant corrections passed to vendors. Acknowledgment is2workingdays and substantive response30workingdays. Applicant records are retained during the relationship plus3years, or3years for unsuccessful applications.
Those are specific process commitments. The partner terms' general sole-discretion/no-reasons clause remains broader; no acquired priority rule resolves every refusal category. This is not a proved exercise of arbitrary denial or an observed successful appeal. The retained HTML references vendor privacy notices without supplying actual links. Root read the complete partner section; other SWGfL processing purposes are outside this lane.
The [API guide](http[local research file] cover date08/10/2025, describes SWGfL-issued provider credentials, CSP hash submissions, NGO-reviewed Active entries, public-user Received entries and independent provider feedback. It documents change timestamps and asks recipients to record status changes. These are interface descriptions, not proof each function or input category is deployed.
Printed6–10 and14–15 distinguish multiple associated cases, provider contributions, feedback replacement/removal and withdrawal of an organization's own submissions. Deletion markers have limited availability; pagination guidance warns that delayed retrieval can miss deleted records. Printed6's Withdrawn→Deleted timing and printed15's minimum24-hour withdrawal description should not become one exact tested retention guarantee. A batch-management feature is expressly unimplemented. Text/URL type labels and the political-free-speech example are schema/example content, not observed censorship records. Neither generic status feedback nor database withdrawal proves restoration of content/accounts. Ordinary PDF retrieval timed out; the complete16-page reader text was read, without executing examples or obtaining operational data.
[SWGfL, 13March2024](http[local research file] announced updated PhotoDNA integration allowing on-device hashing and access by more already-equipped platforms. It also announced Niantic joining. Microsoft provided an attributed supporting statement. This predates the Coalition's January2025 expanded-sublicensing announcement; that later announcement is not the first use of PhotoDNA for adult NCII.
[Microsoft, 5September2024](http[local research file] reports donating the capability that March and piloting StopNCII in Bing, with action on268,899 images by the end of August. This is an operator-reported aggregate for image-search results, not an independent audit, unique victims or removal from source websites. Its separate direct-report process describes review against Microsoft's policy and global search delisting. Full substantive reader body read; original GET403 closed.
[Google, 17September2025](http[local research file] announced planned hash use over the following months. It is not itself proof of completed implementation. No later completion record was located in the single focused Google follow-up query.
The [eSafety August2025 report, updated February2026](http[local research file] records Snap using StopNCII on Spotlight/Discover/Stories, excluding Withdrawn/Deleted entries, with daily updates. Its Chat row does not list StopNCII. Printed7/11/18 establish the15June–15December2024 reporting period and that this summarizes provider responses, not comprehensive regulator testing. That supplies a dated, legally requested recipient account of withdrawal filtering, not a paired individual deletion/restoration trace or current2026 operating guarantee. Ordinary GET timed out and table screenshot failed; reader table/text scopes were read. No original PDF is claimed.
[Free Speech Coalition, 26February2026](http[local research file] urges adoption by adult platforms and explicitly links the case to legal/reputational risk and credibility with banks/payment processors. This is an industry association's recommendation, not a bank mandate or a payment-disconnection record. Its named adopters and volume claims were not independently corroborated here. The full body was read; retained Article metadata dates publication26February2026 and modification27February2026.
The documented architecture permits institutional contributions and differentiated access while preserving platform policy judgments. It includes a described withdrawal channel and a named recipient account of honoring withdrawal states. There is no basis here for claiming all withdrawal requests fail, all recipients obey an automatic command, or banks require this particular product. The most useful missing record remains a current signed data-sharing agreement with its permitted-purpose and correction provisions, followed by a public implementation/audit trace. Wider operator resources and governance are in the sibling finance lane.
Custody: partners-captures.json records eight successful HTML originals, four original administrative JPGs, one403 error and two PDF timeouts. HTML text derivatives are separate. Complete substantive reads: join/programme/approved, all partner terms/schedule, PhotoDNA2024, Google2025 and FSC2026; scoped SWGfL partner privacy; all four diagrams visually. Reader-only: full Microsoft2024 body; full16-page API text; eSafety cover/date, report-period/limitations passages and Table3 Snap row. Other eSafety pages/search snippets are not a whole-report reading. The one malformed discovery query is excluded; eight other focused queries were used. A direct agreement query located no separate executed document within this finite search. Sources retain their own dates and claims. No registration form, case-status service, API, private dataset, outreach or paid action was used. Acquisition stopped for review and forest.