COULDINJECT · TRANSPARENCY UPDATE
We want every user to understand what we have done, what has been affected, and what remains to be done.
The closure concerns the Support workflow phase associated with the first rights notice.
In this statement, SLA means CouldInject Support's response and handling time framework. Completion of an SLA phase or closure of the original case does not end the relevant rights matters, does not mean content review is complete, and does not mean NetEase or any other relevant rights holder has approved, authorized or confirmed the current version.
If we receive new specific pages, content locations, rights explanations or other verifiable information, we will open a new handling phase and link it to the earlier records for continued review.
According to CouldInject's version description, September 19 refers to software fixes, not an intelligence-data update of equivalent scope on that date. The September 28 rollback restored this earlier data and software state.
The following account is compiled from Support correspondence and event records, with all UTC timestamps converted to Beijing Time.
We publish key handling events, including assignment, investigation, supplemental materials, category and priority changes, technical rollback, focused review and phase closure. We do not publish full private correspondence, contact email addresses, ownership-document links, access credentials or other information unnecessary for public disclosure. Repetitive system notifications have been consolidated into the corresponding handling actions.
This timeline explains the measures CouldInject took during this phase. It does not make a final determination on behalf of any party about infringement, trade secrets, ownership or any other legal characterization.
The rights notice entered the Support workflow.
The team requested specific content locations and verification materials that could actually be accessed.
Urgent handling began, with temporary access restrictions and further review arrangements communicated.
The newer version was taken off the public site, an earlier version was restored, and the notifying party was updated.
The first Support / SLA handling phase was completed and archived; new specific information can still enter subsequent handling.
Support created a case after receiving a rights notice concerning ANANTA-related content.
The contact email completed system verification. Email verification is not a final assessment of the rights claim or ownership documents.
The support team accepted ownership of the case and began follow-up.
Content review began, focusing on non-public information, NDAs or confidentiality obligations, and other third-party rights risks. Temporary measures were expressly distinguished from a final legal determination.
The team requested specific page URLs, content locations, and the scope of requested removal, takedown, or access restrictions.
The case category was changed to Copyright / Rights Notice, with high priority.
The team explained that attachments could not then be accessed normally through Support and requested a read-only online link to the materials.
The notifying party replied that ownership materials had been sent. Support recorded the supplemental message and continued follow-up.
The team reiterated that being unable to read the attachment did not mean the other party had failed to send it, and requested read-only links, relevant text in the message body, and specific page locations.
The team asked for only the materials necessary for verification, avoiding unrelated personal or sensitive information.
Support recorded another response from the notifying party submitting ownership materials.
The team explained that the attachment was still not available in the review workflow, shared feedback on what had been received, and again requested accessible materials and specific content scope.
The team described its renewed review of sources, the distinction between public information and independent analysis, and possible temporary hiding, access restrictions, or presentation changes.
The team received an online materials link from the notifying party. Receipt of a link does not mean all claims in it have been accepted.
The matter was referred to technical and content-review personnel. The target communicated at that time was to finish the principal review and adjustments for that round before October 1, Beijing Time; this was not a promise to restore every withdrawn item.
The case was transferred to technical personnel for follow-up.
The category remained Copyright / Rights Notice, and the priority was changed to urgent.
The team stated that initial restrictions on the relevant pages were expected within 24 hours of receipt of the notice, while verification and communication about the specific disputed content and appropriate handling continued.
The case category was changed to Content Review / Takedown Request, with urgent priority retained.
Support recorded that the earliest backup was being restored.
The team informed the notifying party that an earlier data version had been restored, while the September 26–28 version remained under review. The response distinguished public facts, analytical deductions, speculation, and information with unverified sources.
The category was changed to NDA / Non-public Information Risk, and the workflow priority was changed to normal. This is a workflow record, not confirmation that all content had passed review.
The case was transferred back to the support team to continue handling any supplemental information.
The first Support / SLA handling phase was completed, and the original case entered the archive.
Setting the case status to closed means only that the current support workflow has completed this phase's response, technical handling and feedback steps. It does not mean that further investigation, internal analysis or content review has stopped.
New specific information, page URLs, content locations or other rights claims can still enter subsequent handling and be linked to the earlier case records.
By the close of the first Support workflow, we had received ownership-supporting materials and related supplemental explanations from the notifying party.
At the point covered by this phase's records, however, we had not received a complete set of page URLs, specific content locations and a handling list covering all disputed content item by item. This round of handling was therefore not a mechanical deletion exercise against an itemized infringement list. After receiving the overall rights notice, CouldInject proactively adopted risk-control measures including rollback, broader review, source verification and temporary takedowns.
If new information accurately identifying specific pages or content is received, we will continue handling it item by item.
There were 10 primary business sections before the rollback; 8 remain. Paginated search snapshots, 404 pages and shared resource directories are not counted as separate business sections.
Scroll horizontally to see the complete table. Page files include HTML and the route data used for in-site navigation.
| Section | Handling | Page files Before → After | Replaced at the same path | Page paths taken offline | Referenced assets taken offline May be shared between sections | Confirmed impact in this row Pages + referenced assets |
|---|---|---|---|---|---|---|
| Relationship board | Retained; rolled back | 7 → 7 | 7 | 0 | 255 | 262 |
| Characters & NPCs | Retained; rolled back | 8 → 8 | 8 | 0 | 4,816 | 4,824 |
| Factions & companies | Retained; rolled back | 8 → 8 | 8 | 0 | 19 | 27 |
| Scene analysis | Retained; rolled back | 8 → 8 | 8 | 0 | 12 | 20 |
| Timeline | Retained; rolled back | 8 → 8 | 8 | 0 | — (separate scope) | 8 page files |
| World maps | Retained; rolled back | 8 → 8 | 8 | 0 | 9 | 17 |
| Systems matrix | Retained; rolled back | 8 → 8 | 8 | 0 | 0 | 8 |
| Hypotheses | Retained; rolled back | 8 → 8 | 8 | 0 | 0 | 8 |
| Progression & daily life | Temporarily withdrawn | 8 → 0 | 0 | 8 | 0 | 8 |
| Story archive | Temporarily withdrawn | 8 → 0 | 0 | 8 | — (separate scope) | 8 page files |
The asset column is derived from references in the eight public presentation datasets used before the rollback, deduplicated within each section. 203 resource paths were shared by multiple datasets. The same image or path can appear in several sections, and a reference does not mean that every user saw that image on a page.
“—” means that this public-dataset reference method does not apply to that section; its supporting files are listed separately below. “0” means that no matching asset paths were found in that dataset, not that the section had no content. The deduplicated site-wide retirement total is given in the asset table.
An earlier release package was restored; not every old path from before the rollback was retained unchanged.
Before rollback: 4,985 + 74 + 14 = 5,073. After rollback: 74 + 14 + 181 = 269.
Paths unique to the restored package reflect the file organization of the earlier version. They must not be interpreted as the same number of newly added intelligence entries. Nor do 269 files mean that 269 content items have passed review.
| Archive category | Files taken offline |
|---|---|
| Relationship-board pages | 6 |
| Relationship-record pages | 6 |
| Character-name index pages | 32 |
| Featured characters | 1 |
| Factions & companies | 1 |
| World-geography pages | 7 |
| Scene analysis | 1 |
| Gameplay systems | 1 |
| Progression guides | 1 |
| Gameplay loops | 1 |
| General hypotheses | 1 |
| Spatial hypotheses | 1 |
| Archive entry and snapshot homepage | 2 |
| Archive stylesheet and sitemap | 2 |
| Total | 63 |
These files supported functionality through a protected server-side service. They were not 1,152 directly downloadable public files. The count includes pages, indexes and service configuration; it is not a count of characters, events or dialogue lines.
| Supporting-file category | Files |
|---|---|
| Character-name lookup files, including pages and indexes | 320 |
| Event lookup files, including pages and indexes | 266 |
| Dialogue lookup files, including pages and indexes | 554 |
| Story, timeline and revision catalogs | 3 |
| Service deployment support | 1 |
| Public presentation datasets | 8 |
| Total | 1,152 |
Older content has been removed from the public deployment directories, and the relevant old endpoints, search archives and resource entry points no longer serve it. No alternative public backup entry point was provided. Records necessary for verification remain in restricted internal storage. This page therefore says “taken offline / temporarily withdrawn” and does not claim that the files have been permanently destroyed.
We respect the legitimate rights and interests of NetEase and other relevant rights holders and will continue communicating about specific rights claims concerning ANANTA-related content.
The review covers both historical versions temporarily taken offline and the earlier version currently online.
We will continue checking sources, the nature of the content, relevant rights and presentation, distinguishing wherever practicable:
To provide an independent historical reference for this phase's handling record after subsequent page updates, we submitted the then-public v3 statement to the Internet Archive. The links below capture v3, not the initial v1.
Third-party web archives provide only an independent historical reference for a particular moment. They do not mean that the Internet Archive has reviewed, approved or endorsed this page's facts, legal characterizations, statistics or any party's claims.
CouldInject may correct, supplement or update this page in light of new review findings. Significant changes will be recorded by version; historical snapshots distinguish the information published at different times.
CouldInject is an independent, unofficial community project. It does not claim ownership of the relevant rights in ANANTA's original works or official materials, and does not represent authorization, approval or endorsement by NetEase, NetEase Games or Naked Rain.
Completion of the first Support / SLA phase does not mean all review processes have ended, that the parties have agreed on all disputed matters, or that any particular content has been authorized, found infringing or subject to any other final legal determination.
CouldInject will continue retaining necessary handling records and conducting further review based on new verifiable information.
Thank you for your understanding and patience.
CouldInject Team · September 30, 2026
Current statement version: v4. Key-event timestamps, rollback scope and asset totals are unchanged.