Cruxi
Compliance research
A legal representative’s address is not a complete contact design. DSA Articles 11, 12 and 13 describe authority-facing contact, service-recipient contact and representation separately. Use a three-channel responsibility matrix to test the proposed service and public information before agreeing its scope.
Evidence retrieved 2026-10-06. Source versions and topic-specific limits are listed below.
Sourced criteria · EU
| Decision or task | What the source describes | What to prepare |
|---|---|---|
| Where do authority messages arrive? | Article 11 describes a single electronic point of contact for Member State authorities, the Commission and Board, public/current contact information and specified communication-language information. [1] | Identify the monitored authority channel, authorised recipients, languages and escalation owners. Test a received message and retain the public contact/version record. |
| Can a service user reach a person? | Article 12 describes direct, rapid, user-friendly electronic contact with a choice of communication means that does not solely rely on automated tools, with accessible current public information. [2] | Test the actual user journey, communication choices and escalation from an automated tool. Document the outcome and owner; no universal response-time SLA is invented. |
| What is the representative authorised to do? | Article 13 separately addresses the specified non-Union intermediary provider, written designation, location, powers/resources and notification/publication of representative contact details. [3] | Map the actual intermediary role and establishment first. Where appointment applies, document covered entity, mandate, powers, resources and coordinator/contact maintenance. |
| How are shared channels kept accountable? | The three articles specify different recipients and functions; recording one email address does not itself demonstrate that each function is fulfilled. [1] [2] [3] | Build a matrix with message type, public entry point, monitored owner, authority to act, backup and evidence of handoff. A shared channel may be assessed, but do not assume it satisfies every function merely because it exists. |
This workflow does not determine whether the buyer provides a regulated intermediary service or needs a representative. It describes Articles 11–13 of the acquired English original DSA act and a proposed operational matrix; subsequent amendments and applicability require review. It does not require three separate email addresses or establish a universal response deadline.
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Identify the monitored authority channel, authorised recipients, languages and escalation owners. Test a received message and retain the public contact/version record.
Useful evidence: Authority-channel details, language record, public information and receipt/escalation test.
Test the actual user journey, communication choices and escalation from an automated tool. Document the outcome and owner; no universal response-time SLA is invented.
Useful evidence: User-contact journey, available communication means, public details and an escalation demonstration.
Map the actual intermediary role and establishment first. Where appointment applies, document covered entity, mandate, powers, resources and coordinator/contact maintenance.
Useful evidence: Role/establishment assessment, mandate, powers/access commitments and contact-notification record.
Build a matrix with message type, public entry point, monitored owner, authority to act, backup and evidence of handoff. A shared channel may be assessed, but do not assume it satisfies every function merely because it exists.
Useful evidence: A three-function channel/responsibility matrix and end-to-end handoff tests.
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
32022R2065 · retrieved 2026-10-06
Source key D05 · snapshot 7fede5229786ffabdc8f7e55b93b5df49ed77ce445abf1cf51a23d53f82c94e2
Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.