1. Single point of contact
The public legal surface distinguishes between authority-facing and user-facing contact paths even where they currently resolve to the same operator mailbox or workflow.
Languages currently supported for these public channels are English and German unless a more specific notice is published later.
- Authorities / regulators (DSA Art. 11): use the published public legal contact lane and identify the request as authority-facing.
- Users / recipients of the service (DSA Art. 12): use the published notice path or legal contact lane and identify the request as user-facing.
2. How to submit a notice
The Services provide a structured reporting path for notices concerning allegedly illegal content, unlawful conduct, or serious policy violations.
The current technical notice endpoint is:
Public reporting contact details and any supplementary form or legal contact path should remain linked from the Services and the Imprint / Legal Notice page.
- POST /compliance/notices
3. What a notice should include
To the extent available and applicable, a notice should include:
- a sufficiently precise target location or identifier, such as a URL, listing ID, order ID, profile, transaction reference, or other target reference;
- an explanation of why the content or activity is alleged to be illegal or unlawful;
- supporting facts or evidence;
- your name and email address, unless the relevant channel lawfully allows otherwise;
- contact details if follow-up outside an authenticated session is wanted; and
- a statement that you submit the notice in good faith and believe the information provided is accurate and complete to the best of your knowledge.
4. What we may do after receiving a notice
We may:
- acknowledge receipt;
- review the notice manually or with technical triage support;
- request clarification or additional evidence;
- reject clearly unsupported, duplicative, abusive, or bad-faith notices;
- prioritize notices that indicate urgent safety, security, fraud, or legal risk;
- preserve evidence where reasonably necessary; and
- take action where warranted.
5. Possible outcomes
Depending on the circumstances, outcomes may include:
Platform decisions about visibility or access do not alter immutable public blockchain records.
- no action;
- delisting or removal from platform visibility;
- temporary restriction or workflow blocking;
- account suspension;
- escalation for legal review; or
- referral to competent authorities where required or appropriate under law.
6. Reasons and redress
Where required by applicable law, we provide reasons for qualifying moderation or restriction decisions and make available any relevant complaint, appeal, or redress path.
If you are directly affected by a qualifying restriction decision, the Services may provide a decision notice, statement of reasons, or separate appeal pathway as applicable.
7. Misuse of the notice system
Knowingly false, abusive, harassing, or bad-faith notices may themselves violate platform policy and may result in restricted access to reporting channels or the Services.
8. Recordkeeping
We may keep records of notices, decisions, statements of reasons, and appeals for legal, audit, safety, accountability, and claim-defense purposes, subject to our retention rules and applicable law.
9. Changelog
- 2026-04-20.1: Added the authority-facing and user-facing public contact split and introduced explicit version metadata.