The Steam DossierDispute a finding
Prove us wrong.
We will put it right.
Show the error and the evidence. We will acknowledge it, correct or withdraw the finding, and apologise for harm our error caused.
You do not need a lawyer, a lawsuit or the identity of a contributor to get an error corrected.
Make your case
What needs to change?
A specific passage. A reason.
The outcome you are asking for.
Our position
A law firm is not a court.
Valve and Taylor Wessing can challenge any finding here. Their claims are assessed on evidence and legal basis. Their demands do not become court decisions because of who sent them. An authenticated, applicable decision from a competent court or regulator is acted on within its lawful scope.
We do not require anyone to identify or pursue our contributors to get the record corrected. Show the error and we will answer for it. We stand behind supported reporting and we own our mistakes. Professional titles, pressure and the cost of a legal letter do not determine what is true.
Have a new case or evidence to add? Share material with the editors — a separate intake with no email field, a 14-day limit and an optional editor-only note.
From request to resolution
A clear path to action.
- 01
Received & notified
An eligible submission receives a private tracking key and timestamp. Its receipt and timeline remain private. An administrative notification is queued immediately; failed notification attempts are retried.
Evidence can be given directly in the form. A lawyer or digital signature is not required to report an error. - 02
Evidence & signature verified
For a factual challenge, we assess the source against the exact statement. For an official decision, we validate the signature using the issuing body’s official key, certificate or trusted certificate chain, confirming the issuer and integrity of the document.
We then confirm the decision’s powers, applicable scope and required action. Document checks are automated where supported; an authorised reviewer confirms the official source and execution scope. - 03
The remedy is applied
Once the decision and scope are confirmed, the approved action runs through the execution system. A removal can restrict the affected public copies first; a correction replaces the error and records the action privately. Any public correction notice is reviewed separately. We aim to act immediately.
Compliance is the default. If a review or appeal is pursued, we explain the reasons through your private receipt and attempt notice to the contact you supplied. - 04
Copies are updated
The action covers the identified website pages, translations, exports and managed mirrors. Mirror work is scheduled for the next 00:00 Europe/Berlin, or earlier when an administrator intervenes.
Technical problems remain pending for retry or manual handling. A case is not marked fully executed while an identified delivery step is unfinished.
72 hoursInitial official-decision verification target
14 daysWritten assessment of evidence of error
Action follows verification as promptly as possible. A shorter binding deadline takes priority over these review targets.
Private case access
Already sent a request?
Use the ID and private access key from your receipt. The key is shown once and cannot be recovered. Keep the receipt or its private bookmark.
The boundaries
Clear terms. An accountable record.
The signed policy contains the full procedure.
Jurisdiction and excluded official demands
We confirm the issuing body’s relevant powers, legal basis, territorial scope and the publications covered. This procedure does not amount to submission to every jurisdiction.
Official Russian and Belarusian state demands, including demands made through representatives, and prohibited dealings under applicable sanctions, including OFAC restrictions, are outside this intake. Identified excluded requests are rejected before a case is created; their text and files are not retained in the dispute database, vault, notifications or public log.
This concerns official capacity and prohibited dealings, not a private person’s nationality. Mandatory applicable obligations remain separate. Ordinary infrastructure security logs are separate from the case store. Policy §1.
Historical facts and the public record
An accurate account of an earlier event does not become false because it is old, unwelcome or later developments change the context. We distinguish facts, attributed allegations, opinion and later updates.
Each privacy or copyright request is assessed against the actual material and applicable law. A notice about a document does not automatically erase the underlying historical fact. Privacy procedure · Copyright procedure.
Contributors and reciprocal identity verification
You can challenge a finding without identifying an author or source. If identities or mandates are materially relevant, the involved representatives — including Valve’s representatives — may agree to reciprocal verification through independent counsel or another confidential channel.
Voluntary disclosure requires a lawful basis and any necessary consent. Mandatory lawful disclosure is assessed separately. This is not a request to expose unrelated people.
Website, IPFS and other published copies
We can correct or remove the public copies we control. Managed IPFS publication requires a new version, an updated publication reference and removal of our relevant old pins. Unconfirmed external updates remain pending.
Copies independently held by other parties and immutable archives cannot be erased by changing this website. We take the available steps concerning affected copies. A removal does not trigger a new archive copy or a public notice that reveals a restricted request or links to removed material. Policy §7.
Your submission stays private by default
No personal name is required. Optional email is used for case communication. Accepted text, documents and original signatures are held outside the public website with restricted access. Nothing is published automatically.
The receipt, identifier, dates, status, correspondence and file hashes stay private. There is no automatic public-log entry or web-archive submission. Any permitted release requires a separate review of privacy, third-party rights and publication restrictions.
Retention is reviewed for necessity under the applicable legal basis. The normal reference is the publication’s lifetime plus three years; shorter retention, erasure and lawful holds are assessed specifically. Rate records expire after two days and submission connection hashes after 30 days. Infrastructure and hCaptcha process technical connection information separately. Policy §9 · privacy@phishdestroy.io.
Local processing and approved automatic action
File checks and private tracking run on our infrastructure. Once an official decision, its issuer and exact scope are confirmed, the approved remedy is executed automatically, with failures kept pending for administrator attention.
Internal review may use local AI only where it is configured and authorised. It must stay local and advisory: it cannot authorise publication, decide jurisdiction or bypass verification of the official decision.
Replies and other ways to contact us
You may submit a reply without agreeing with our conclusions. We aim to publish a relevant reply or explain a concern within seven days. Material edits are identified; replies of up to 800 words ordinarily fit beside a finding.
You may also make a personal-data request. Where GDPR applies, the normal response period is one calendar month. Any lawful extension is explained within that period.
If you cannot use the form, write to legal@phishdestroy.io. The receiving team handles email; it is not automatically registered by this form.
Policy v3 · signed
Read Policy v3 Download its signature Terms of Service §9
Check the signature and policy record
- Key
- 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01
- SHA-256
- computing in your browser…
- Version record
- —
curl -sO https://phishdestroy.io/steam_dossier/dispute/policy-v3.txt{,.asc}
curl -s https://phishdestroy.io/.well-known/pgp-key.txt | gpg --import
gpg --verify policy-v3.txt.asc policy-v3.txt && sha256sum policy-v3.txt