EU

DSA: Contact Points for Recipients and Legal Representatives

Rule: Hosting service providers must establish user-accessible contact mechanisms and, if not established in the EU, designate legal representatives to ensure accountability and enable recipient communication.

Note: These requirements are in addition to the general requirements in Articles 11-12 for all intermediary services.

Points of Contact for Recipients of Service [Article 18]

Article 18(1): User-Accessible Contact Point

Hosting service providers must provide user-accessible, easy-to-use system for:

  • Direct communication with provider
  • Electronic format
  • User-friendly interface

Different from Article 11:

Article 11Article 18
For authorities and CommissionFor end users (recipients of service)
Can be simple emailMust be user-friendly system
All intermediary servicesHosting services only

“User-friendly” means:

  • Easily accessible from user interface
  • Clear how to contact provider
  • Available in languages used in interface
  • Responds within reasonable time
  • No excessive barriers (no registration wall for contact)

Communication purposes:

PurposeExamples
NoticesReport illegal content (Art 16)
ComplaintsChallenge content moderation decisions (Art 20)
InquiriesQuestions about terms of service
RequestsExercise of rights

Article 18(2): Information to be Provided

Contact system must allow recipients to provide:

  • Electronic contact details
  • Clear explanation of issue
  • Relevant information supporting request/notice

Provider may request additional information if reasonably necessary to:

  • Identify or contact recipient
  • Process notice, complaint, or request

Balance required:

  • Enough information to handle request
  • Not excessive or deterring barriers
  • Proportionate to purpose

Example contact forms should include:

  • Name (may be optional for initial notice)
  • Email address
  • Description of issue
  • URL or identifier of content
  • Reason for contact
  • Attachments if needed

Article 18(3): Language Requirements

Contact system must be available in:

  • At least one official language of each Member State where provider offers services
  • And English

“Offers services” means:

  • Substantial number of recipients in Member State
  • Or directed at recipients in Member State

Practical approach:

  • Large platforms: all major EU languages
  • Smaller services: languages of primary markets + English
  • Machine translation may assist but not substitute

Article 18(4): Information About Contact Point

Providers must publish:

  • Information on how to access contact point
  • Clear, easily accessible location (e.g., footer, help section)
  • Visible on all pages or in main menu

Users should be able to find contact within:

  • Two clicks from any page
  • Clearly labeled (“Contact”, “Report”, “Help”)
  • No hidden locations

Legal Representatives for Non-EU Hosting Services [Article 19]

Article 19(1): Designation Requirement

Hosting service providers not established in EU must designate legal representative in one of Member States where provider offers services.

Triggers designation:

  • Provider not established in any Member State
  • Offers hosting services in Union
  • Regardless of provider size

Different from Article 12:

Article 12Article 19
All intermediary servicesHosting services specifically
General compliance mattersHosting-specific obligations
Broader mandateFocused on hosting duties

Can be same representative as designated under Article 12 (common approach)

Article 19(2): Selection of Member State

Provider designates representative in:

  • Member State where provider has substantial number of recipients
  • Or Member State with established presence

Factors to consider:

FactorConsideration
User baseWhere most EU users located
OperationsWhere provider has offices/staff
LanguageLanguages provider operates in
EnforcementDigital Services Coordinator capacity

Common choices:

  • Germany (largest EU market)
  • France (second largest)
  • Ireland (many tech companies present)
  • Netherlands (good infrastructure)

Article 19(3): Representative’s Powers and Resources

Representative must:

RequirementDetails
Written mandateFrom provider authorizing representative
Sufficient powersHandle all compliance matters
Adequate resourcesStaff, expertise, budget for obligations
Actual authorityNot just mailbox, must be empowered to act

Representative must be able to:

  • Receive and comply with orders (Arts 9-10)
  • Receive notices under Art 16
  • Handle complaints under Art 20
  • Cooperate with Digital Services Coordinator
  • Provide information to authorities
  • Be contacted in enforcement proceedings

Resources needed:

  • Legal expertise in DSA and EU law
  • Staff to monitor and respond
  • Communication systems
  • Escalation procedures to provider
  • Budget for compliance activities

Article 19(4): Representative Tasks

Representative mandated to:

TaskDescription
Receive communicationsFrom authorities, Commission, Board, users
Respond to requestsProvide information, explanations
Ensure complianceFacilitate provider’s DSA compliance
Cooperate with authoritiesEnable effective supervision

Specific obligations:

  • Respond without undue delay
  • Forward communications to provider
  • Ensure provider takes action
  • Maintain communication channels
  • Keep authorities informed

Article 19(5): Contact Information Publication

Provider must publish:

  • Name of legal representative
  • Postal address in Member State
  • Telephone number
  • Email address

Where to publish:

  • Provider’s terms and conditions
  • Provider’s website (easily accessible)
  • DSA transparency database
  • In response to authority requests

Must be:

  • Current and accurate
  • Publicly accessible
  • Updated within 30 days of changes

Article 19(6): Representative Not Personally Liable

Important protection:

  • Representative not personally liable for provider’s violations
  • Acts on provider’s behalf
  • Provider remains responsible for compliance
  • Representative facilitates enforcement, not substitute for provider

Practical effect:

  • Encourages professionals to serve as representatives
  • Provider cannot escape liability through representative
  • Representative protected if acting within mandate

Coordination Between Articles 11, 12, 18, 19

Multiple contact requirements:

ArticleScopeContact WithProviders
Art 11Point of contactAuthorities, CommissionAll intermediary services
Art 12Legal representativeAuthorities, CommissionNon-EU intermediary services
Art 18User contactRecipients of serviceHosting services
Art 19Legal representativeAuthorities, usersNon-EU hosting services

Can consolidate:

  • Articles 11 and 18: Same contact system (if accessible to both authorities and users)
  • Articles 12 and 19: Same legal representative (if properly mandated for both)

Best practice:

  • Use single user-facing contact system (Art 18)
  • Designate single legal representative (Arts 12+19)
  • Maintain authority contact channel (Art 11)
  • Document clearly who handles what

Practical Compliance

Implementing Article 18 Contact System

Checklist:

  1. ✅ Create contact form or system accessible to users
  2. ✅ Make form available in relevant languages
  3. ✅ Ensure form easily found (link in footer, help section)
  4. ✅ Allow users to describe issue clearly
  5. ✅ Enable file attachments if needed
  6. ✅ Confirm receipt to user
  7. ✅ Respond within reasonable timeframe
  8. ✅ Provide reference number for tracking
  9. ✅ Route to appropriate team (notices, complaints, general inquiries)
  10. ✅ Document all communications

Example implementations:

  • Social media platform: “Report” button on content + general contact form
  • Cloud hosting: Support ticket system accessible to all users
  • File sharing: “Contact Us” in footer + abuse reporting form

Selection criteria:

  1. ✅ Established in appropriate Member State
  2. ✅ Has legal/compliance expertise
  3. ✅ Adequate staffing and resources
  4. ✅ Responsive and reliable
  5. ✅ Understands provider’s services
  6. ✅ Can communicate in relevant languages

Mandate must include:

  1. ✅ Clear scope of authority
  2. ✅ Specific DSA obligations covered
  3. ✅ Communication and escalation procedures
  4. ✅ Budget and resources
  5. ✅ Duration and termination provisions
  6. ✅ Indemnification/liability terms
  7. ✅ Confidentiality obligations

Publication requirements:

  1. ✅ Post representative contact info on website
  2. ✅ Include in terms and conditions
  3. ✅ Provide to Digital Services Coordinator
  4. ✅ Submit to transparency database
  5. ✅ Update if representative changes

Ongoing Management

For providers:

  • Monitor response times to user contacts
  • Track common issues and improve processes
  • Ensure representative has current information
  • Regular communication with representative
  • Provide resources representative needs
  • Update contact information promptly

For representatives:

  • Maintain communication channel with provider
  • Monitor incoming communications
  • Escalate urgent matters immediately
  • Track compliance deadlines
  • Coordinate with authorities
  • Report regularly to provider
  • Maintain logs of all activities

Common Mistakes

Using same email for everything:

  • Art 11 (authorities) and Art 18 (users) can be different
  • Users need accessible, responsive system
  • Authority contact for rapid official communications

Hiding contact forms:

  • Must be “easily accessible”
  • Not buried in FAQ or terms
  • Clear labeling required

Representative without actual authority:

  • Representative must be able to act
  • Not just forwarding service
  • Needs resources and mandate

Not publishing representative info:

  • Must be easily accessible
  • Include in terms, on website
  • Keep current

Insufficient language support:

  • Art 18(3) requires languages of markets served
  • Plus English
  • Machine translation alone may not suffice

Non-EU providers ignoring requirement:

  • Art 19 applies to all non-EU hosting providers
  • No threshold or exemption
  • Enforcement increasingly active

Citation

Sources

Contains public sector information licensed under the Open Government Licence v3.0 where applicable. This is not legal advice. Always refer to official sources for authoritative text.

llms.txt