{ "compartment_id": "section-16", "number": "Section 16", "title_local": "The Digital Services Act: put knowledge on the record", "title_english": "The Digital Services Act: put knowledge on the record", "source_url": "https://phishdestroy.io/steam_dossier/#dsa-accountability", "source_document": "index.html", "content": { "html": "
\n
\n
Part C — Legal frameworks · Section 16 · Notice, response, responsibility

The Digital Services Act: put knowledge on the record

\n
Context & source limits

Two elements of an Article 16 notice sit with the submitter rather than with this dossier: the submitter's own details and a statement of good faith that the information is accurate. Everything else the Article requires — the substantiated explanation and the exact electronic location — is set out in Section 3 and in the route register, with saved responses and hashes, so that any party can lodge it. Two further limits on the law itself: losing the hosting exemption does not by itself establish liability under any other law, and the 6% in Article 52(3) is a statutory ceiling, not an assessed penalty against Valve.

Under the DSA a hosting provider keeps its liability shield only until it has specific knowledge and fails to act. This dossier is that notice. It names the hosts, the dates, the saved responses and the hashes. From publication the question is no longer whether Valve knew — it is what Valve did next.

\n
01July 2016 / the dossier exhibit

A ten-day demand.

The notice reconstructed above is the historical starting point for the investigation's enforcement comparison.

0217 February 2024 / general application

The DSA time window.

Separate historical conduct from conduct during the period when the relevant DSA obligations apply.

03Ten years / original dossier snapshot

Duration needs a notice trail.

The elapsed time since July 2016 (see Section 11) is a dossier metric. It is not ten years of established DSA violations. Link each notice to a specific item, applicable law, delivery evidence and response.

\n
Articles 6, 8 & 16 / the legal test

For relevant hosting services, specific knowledge and failure to act expeditiously can remove the hosting exemption. A sufficiently precise notice can establish knowledge of the particular content. The DSA imposes no general monitoring duty; loss of the exemption does not itself establish liability under another law.

DSA: Articles 6, 8, 16, 52, 53, 93 and recital 17 ↗ archived 2026-09-20 ↗

\n
Review preserved complaints ↗Build the account timeline →Full legal & economic analysis →
\n
\n
" }, "original_content_sha256": "3c1664c9f6f9b780ec91779b89c54470b194a9a5af9240d28b58e377f45fbf1d", "author_pseudonym": "Agent John", "schema": "phishdestroy.macro-fact.v1", "language": "en", "aggregator": "PhishDestroy", "exports": { "pdf": "/steam_dossier/exports/agent-protocol/files/en/steam_dossier_section_16_agent_john.pdf", "json": "/steam_dossier/exports/agent-protocol/files/en/steam_dossier_section_16_agent_john.json", "signature": "/steam_dossier/exports/agent-protocol/files/en/steam_dossier_section_16_agent_john.json.asc" }, "integrity": { "signed_object": "steam_dossier_section_16_agent_john.json", "signature_file": "steam_dossier_section_16_agent_john.json.asc", "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01", "scope": "Exact JSON bytes, including macro-fact author and corresponding PDF SHA-256. PhishDestroy is the integrity signer; original evidence attribution is unchanged." }, "pdf": { "filename": "steam_dossier_section_16_agent_john.pdf", "sha256": "76ac5e5ea3d62f715bcad5a14e6749276db0dce9e4ea49a0179cb9b0bf03e72e", "pages": 4 } }