Skip to content
flatbrowser

DSA Art. 16

Report illegal content or abuse

Anyone can file a notice — no account needed. You get a reference and a confirmation of receipt immediately.

draft 2026-10-04 · unreviewed

What this form is for

We are browser-automation infrastructure. Two different things can go wrong, and both belong here:

  • Illegal content stored on our systems — session artifacts (screenshots, PDFs, traces) a customer instructed us to keep. This is hosting under the DSA, so a notice creates actual knowledge and we must act.
  • Misuse of our infrastructure — traffic from our browsers that looks like credential attacks, scanning, spam or load generation against your systems. That breaches our Acceptable Use Policy and we enforce it.

Egress traffic itself is a mere conduit (Art. 4 DSA), so we cannot remove content that merely passed through us and lives on somebody else’s server — but we can, and do, act against the customer responsible for the traffic. Tell us either way; we will say which route applies.

What happens after you submit

  1. Immediately: an automated confirmation of receipt with a reference (Art. 16(4)).
  2. Review by a person — never by an automated decision alone.
  3. A decision within [PLACEHOLDER: internal decision deadline for abuse notices, e.g. 72 hours], sent to you with the reasons and the remedies available to you, including recourse to the courts (Art. 16(5)).
  4. Where the content is illegal we remove or disable it and issue the affected customer a statement of reasons (Art. 17).
  5. Where we become aware of a suspected criminal offence involving a threat to someone’s life or safety, we inform law enforcement immediately (Art. 18) — before, not after, hearing from the customer.

We handle every notice in a timely, diligent, non-arbitrary and objective manner (Art. 16(6)) and keep an audit trail of what we did and when.

Before you start

  • Child sexual abuse material: you may report it without giving your name or email. Do not use this form — write to [PLACEHOLDER: abuse email — DSA Art. 16 notices] or contact law enforcement directly, and we will act on the notice regardless.
  • Data-protection requests (access, erasure) are not abuse notices — see the privacy policy.
  • Account and billing questions go to our point of contact for users under Art. 12 DSA: [PLACEHOLDER: support email — DSA Art. 12 point of contact]
  • Authorities: use the Art. 11 point of contact, [PLACEHOLDER: email for authorities — DSA Art. 11 point of contact], and quote your file reference.
  • A knowingly false notice can make you liable for the damage it causes. We keep notices and their outcomes on record.

File a notice

Fields marked * are the elements Art. 16(2) requires. The form checks them before it sends, and we validate them again server-side.

Reporting traffic from one of our machines? Choose “Traffic from one of our IPs” and give the source IP, when you saw it and what it hit. Several customers can share one of our IP addresses, so the time window and the target are what let us identify the one responsible; we match them against our connection records (which customer used which of our IPs when, never page content).

Confirmation emails are limited per address and per day so that the form cannot be used to flood someone’s inbox. If no copy arrives, the on-screen receipt and its reference are your confirmation.

What are you reporting?
Exact URL(s) of the content *

One location per line, including https://. Art. 16(2)(b) needs the exact location — a homepage or a search result is not enough for us to act on.

you get a reference and a confirmation of receipt immediately · art. 16(4) dsa