Compliance

A WAF your legal team will thank you for

GDPR is why people choose ONX. We sit down and write the DPA with you — hotel, municipality or shop.

Union

The console, the updates and the picture you need to run protection live in the Union.

Default

Less data, a clear purpose, retention you control. It all goes into the DPA you sign.

Oversight

Decisions happen on your server. You can show a colleague — or a regulator — why a request was stopped.

GDPR

GDPR is why you buy ONX

We aim as high as EU rules allow. Then we sit with you and agree the fields, the retention and the basis — for this hotel, this town, this shop.

Minimisation. The console receives what it needs to run the network — not a copy of every visitor request.
Purpose. That data keeps the site safe and improves protection for the same kind of business.
Retention. How long we keep it is agreed — and then it is purged.
Integrity. Updates are signed. Every action in the console leaves a trail.

Oversight

GDPR first. Decisions documented, so AI Act and NIS2 conversations have an answer. You get an architecture you can defend.

Transparency. Every blocked request includes a reason a person can read.
Human oversight. Your team reviews incidents and approves updates.
Local scoring. The decision is made on your server. The EU console is for operations.
Optional extra review. Off by default for municipalities. Used only when you ask for it.

Architecture

ONX decides on the request without calling an outside model.

Documents

Written with you for hotel, municipality or shop.

Uptime and response commitments for enterprise deployments.

EU hosting and only the processors named in your DPA.

Architecture, key management and hardening — on request.

We’ll walk through the DPA and how ONX fits your hotel, municipality or shop.

Start a conversation