About this archive

Why this archive exists

During the DeepSeek Persona Incident, a large amount of harassment and abuse circulated across platforms, group chats, and personal timelines. Posts get deleted, accounts get suspended, and screenshots lose their context. This archive preserves submitted evidence, reviewed and dated, in one place that everyone can search. It documents what people reported and when, so the record of the incident does not depend on any single platform, account, or memory.

The archive is a record, not a verdict. Everything here is published as submitted and reviewed against the rules below. A record appearing in this archive is not a finding of fact, and it is not a statement about any person's guilt or innocence.

How a submission becomes a record

1. Submit. A visitor uploads one file with an optional description, date, and source link.
2. Store privately. The file is held in a private review queue. Nothing is public at this stage.
3. Review. A moderator checks the file against the submission rules, verifies what can be verified, and censors any personal details that slipped through.
4. Publish. Approved records are published to the archive with their file hashes, and become searchable. Everything not approved is deleted after 30 days.

Submission rules

• Censor personal information

  Evidence must not expose private information about anyone: names, faces, handles, phone numbers, addresses, workplaces, or anything else that identifies a private person. Censor it before submitting. If a published record is found to expose personal information, it is corrected or removed. This protects people on both sides of the incident.

• No fabricated material

  Submit only material you believe is genuine. Fabricated evidence, edited screenshots presented as originals, and material submitted to frame someone are rejected. Verified reports of false records lead to removal.

• Lawful content only

  Pornographic, terrorist, and other illegal content is never accepted. Submissions must comply with applicable law, including the regulations that apply in mainland China.

• Right to submit

  Submit material you have the right to share. Do not upload private conversations you were not part of unless the public interest clearly outweighs the privacy of the people involved, and censor accordingly.

Privacy and data handling

The archive is built to collect as little personal data as possible while keeping evidence verifiable:

• Identifying image metadata (EXIF, such as camera and location data) is stripped from JPEG and PNG uploads before storage by default. Both the original and the stored file hashes are recorded for the review team. If operators disable stripping to keep evidence bit-exact, every published image is manually checked first.
• IP addresses are never stored. Abuse control uses salted one-way hashes only.
• Abuse control uses rate limits and salted one-way hashes. When human verification (Turnstile) is enabled, only the pass or fail result is recorded, never a token from your browser.
• Submissions sit in a private repository that only maintainers can read, before anything is published.
• Every publication action is a versioned commit, which acts as the audit log.
• Uploaded files are always treated as data. They are never executed, and they are malware-scanned before publication.

Integrity and verification

Every file in the archive is published together with its SHA-256 hash, in the public index and on each record page. Hashes let anyone confirm that a file they have matches the file the archive published, and that it has not changed since. To verify a download, run:

sha256sum <downloaded-file>

and compare the result with the hash shown on the record page. If they differ, the file was altered after download.

Reports, corrections and removal

Anyone can request the correction or removal of a record. Reports are reviewed by a moderator before any action, and a report that identifies a specific rule violation with evidence is handled fastest. Good reasons to report a record:

• It exposes uncensored personal information.
• It is fabricated, or was edited to mislead.
• It contains illegal material.
• You are the person shown in it, and you did not consent to its publication.

Reports are filed through the same review pipeline as submissions, in the report form. There is no email step, and reports are never published.

Verified problems are fixed by censoring the material or removing the record from the archive. Removal requests from the person a record is about are honored after review, including delete-and-forget requests by the original submitter. If a record is removed, the public copy is deleted; the private audit history of the archive captures that a removal took place.

Open the report form

To report a specific record, open that record and use its report button; the record ID is filled in for you.

Terms of use

Scope and neutrality

This archive preserves material submitted by the public, reviewed against one shared set of rules. It does not take sides in the incident, it does not certify that any record is true, and it does not name people as perpetrators or victims. Treat every record as a document: read the description, check the hash, open the source link, and draw your own conclusions.