A useful evidence file should let a reviewer reconstruct the Article 40 path without asking product, security, or legal teams to recreate the decision from memory. The file should show the request, the research purpose, the DSC route, the dataset decision, the security review, and the final access state.
Keep public-data access separate from vetted researcher access. Article 40 also requires access without undue delay to publicly accessible interface data, including real-time data where technically possible, for researchers who meet specified independence, funding, security, proportionality, and research-purpose conditions.
Can a VLOP or VLOSE reject a vetted researcher data request because the platform prefers not to share the data?
No. Article 40 provides a specific amendment route, not a broad preference-based refusal. Within 15 days, the provider may ask the DSC of establishment to amend the request if it does not have access to the data or if access would create significant service-security or confidentiality vulnerabilities, and it must propose alternative means or sufficient alternative data.
Does DSA researcher data access require a platform to publish a general-purpose research API?
No. Article 40 refers to access through appropriate interfaces specified in the request, including online databases or APIs. The evidence record should show which interface was specified or approved, which data it exposes, and why the access method fits the DSC request and security constraints.
Who decides whether a researcher is vetted for Article 40 access?
The Digital Services Coordinator of establishment grants vetted researcher status for the specific research and issues the reasoned request to the VLOP or VLOSE. If the researcher applies through the DSC in the Member State of their research organisation, that DSC conducts an initial assessment, but the DSC of establishment makes the final decision.