Hazely Notice-and-Action Procedure (EU Digital Services Act)

Effective 14 August 2026 | Version 2.0

This page explains how to tell us about content in Hazely that you consider illegal, and what we do with such a report. It is aligned with Article 16 of Regulation (EU) 2022/2065 (the Digital Services Act, "DSA").

About this version. Version 2.0 replaces version 1.1 in full. Version 1.1 promised machinery that did not exist: an automated acknowledgement, fixed decision windows, an internal complaint system with a second reviewer, an out-of-court dispute route, and an annual report at a page that was never created. Hazely is run by one person; most of that machinery was never owed by a service of this kind, and none of it was real. This version describes the procedure that actually operates. It is also the first version published as a web page — version 1.1 was readable only inside the Android app.

Language. This document is published in English only. No other language version of it exists, so none can prevail over this one. The only Hazely document currently published in Dutch is the Privacy Policy, at hazely.nl/privacybeleid. Reports and correspondence may be in Dutch or English.

1. What kind of service Hazely is under the DSA

Hazely is an information service operated by one person. Nearly everything in it — the map, the shop listings, opening hours, the guide pages — is compiled by us from public sources rather than posted by users, and users cannot post content that other users see, with one narrow exception: a strain-catalogue lookup that finds no match can create an AI-generated catalogue entry, served to all users, containing only a strain name and description (the Privacy Policy §3.3 describes this).

Our reading of the DSA, stated as our own position rather than a settled ruling: Hazely hosts almost no third-party content visible to others, is at most a small hosting / information service, and is not an online platform within Art. 3(i) DSA. As a micro-enterprise it is in any event exempt from the online-platform obligations of Chapter III, Section 3 — among them the internal complaint-handling system (Art. 20), the out-of-court dispute-settlement route (Art. 21) and the misuse-of-mechanism rules (Art. 23) — and from transparency reporting (Art. 15(2)). Version 1.1 promised parts of that machinery anyway; those promises were not real and are gone. What follows is what we actually operate. Where the DSA does not oblige us, it is described as our practice, not as an obligation.

2. How to report illegal content

Three routes:

Anyone may report — you do not need to be the victim, the rights-holder, or an authority. Reports without an email address are accepted; without one we cannot tell you the outcome or ask a follow-up question. Where a report concerns material that may relate to the offences in Articles 3 to 7 of Directive 2011/93/EU, you may stay anonymous.

3. What makes a report actionable

The more of Art. 16(2)'s elements a report contains, the faster we can act:

a) why the content is illegal — the law it violates if you know it, or a plain-language explanation;
b) exactly where it is — the hazely.nl URL, or the screen and item in the App;
c) your name and email address, if you are willing to give them;
d) your good-faith confirmation that the report is accurate and complete.

The form at hazely.nl/report collects exactly these. A report missing some of them is still read — it may just take longer to act on.

4. What happens to your report

5. What we keep

Reports are stored in our database (Firestore, EU region) and kept until the report is resolved, plus a reasonable period after that so we can show how it was handled. The Privacy Policy §7 states the retention position for reports honestly, including its limits, and §3.1 describes exactly what a report record contains.

6. Orders from authorities (Arts. 9–10 DSA)

We respond promptly to lawful orders to act against illegal content, or to provide information, from Dutch judicial or administrative authorities — including the Public Prosecution Service (Openbaar Ministerie) and the Police — and from any other EU Member-State authority issuing an order in compliance with Art. 9 or Art. 10 DSA.

Authorities should write to legal@hazely.nl. Hazely is operated by a natural person established in the Netherlands; there is no company registration and no published registered address. A postal address for formal service is supplied on request from legal@hazely.nl, as §1 of the Privacy Policy describes.

7. Point of contact (Arts. 11–12 DSA)

For authorities and users alike, the single point of contact for DSA matters is legal@hazely.nl. Communications may be in Dutch or English.

8. Contact

Changelog

Version 2.0 — 14 August 2026 (replaces version 1.1 of 21 May 2026)

1. Removed every promise of machinery that did not exist: the automated acknowledgement (no automated email exists anywhere in our system), the fixed decision windows for straightforward and complex cases, the claim that complaints are reviewed by a different person than the original decision-maker (there is one person), the internal complaint procedure and its response deadline, the out-of-court dispute-settlement section, the abusive-notifier suspension policy, and the annual report at a page that was never created. 2. Stated our DSA classification — at most a small hosting service, not an online platform, micro-enterprise — and reframed the document as the procedure we actually operate rather than obligations most of which never applied to us (§1). 3. Described the real intake routes: the web form with its actual fields and its on-screen reference number, the in-app routes exactly as they exist on each platform today, and email (§2). Version 1.1 called the /report address "a built-in form" at a time when it redirected to a pre-addressed email draft. 4. Published this procedure as a web page at hazely.nl/notice-and-action. Version 1.1 had no web page and was unreadable on iOS. 5. Removed the advertising-banner example from the content-location guidance — no advertising exists in the App. 6. Retention now defers to the Privacy Policy §7 instead of implying a schedule of its own (§5).