Consent, asked properly.

Nexus is the consent layer the studio puts on the sites it looks after. It asks a visitor before anything measures them, and it keeps what they answered.

What it is

Most sites carry a consent banner that was bolted on at the end and describes a site somebody else built. Nexus was built the other way round: it reads the site it is installed on, writes the policy from what it found, and refuses to let anything measure a visitor until that visitor has answered. It is our own software, and the reason our builds never need a third-party cookie widget.

Execution

What it does

Nexus is the consent layer the studio puts on the sites it looks after. It asks a visitor before anything measures them, and it keeps what they answered.

It asks first

Nothing that measures a visitor runs until they have chosen. The banner is the gate, not a notice posted after the fact.

It reads the real site

A scanner goes over the site and reports what it actually sets, so the list a visitor reads describes that site rather than a template. It re-scans on a schedule, because sites change.

It publishes the policy

The privacy and cookie pages are generated from what the scan found and served at their own address, which is what the banner links to. One source, so the page and the banner cannot drift apart.

It keeps the record

Every answer is recorded as it is given, so a choice can be shown later rather than assumed.

Who runs it

We do. Nexus is designed, built and operated in-house, and it is running in production on the sites we look after, this one included: the consent banner on this site is Nexus. It is not sold as a subscription.

The studio behind it

Built here, run here.

We build our own software for the same reason we build yours properly: because the thing that has to keep working after launch is the thing worth getting right.