Private enforcement radar

Which competition decisions could lead to damages claims, and who could sue.

BINA reads everything the European Commission and the Autorité de la concurrence publish, sorts it by a level table your legal team fixes in advance, and writes the bulletin and case reports lawyers used to write by hand. Every line is cited.

Private workspace for the legal team. BINA supports counsel; it does not make legal decisions.

Bulletin · July 2026Sample
150reviewed
7important
8to note
0to review
Level 1DMA.100075

Google Play · Restrictions on steering users

European Commission · DMA Art. 5(4) · 23 Jul 2026

Fine
€430m
IP/26/1670
Fees
5–17%
decision
Appeal
To check
InfoCuria

Named in the decision

Third-party app stores

“…those stores lost traffic that would otherwise have reached them.”

Recital 87 · quote verified word for word

Added by BINA · hypothesis

Alternative Android app stores

Sample data. Recitals in the sample are paraphrases and are flagged as such.
Reads every publication fromEuropean Commission DG COMPAutorité de la concurrence Licence Ouverte 2.0

Product

Two outputs, both auditable.

01

The monthly bulletin

Every document both authorities published in the period, sorted by the level table. Level 1 and 2 cases get a card; level 3 gets one line; routine documents are counted. A type the table does not know is listed for review, never given a level.

02

The case report

For each important decision: the fine, since when, and the appeal status; a three-line summary with a recital behind each line; the parties that could claim, in two clearly separated categories; and similar decisions.

How it works

From publication to report, with the source attached.

  1. 01

    Read

    Every document the Commission and the Autorité de la concurrence publish is fetched, stored by hash and parsed into numbered recitals. Never truncated.

  2. 02

    Level

    A frozen table, fixed by the legal team before any case was run, places each document by its type alone. Unknown types go to review.

  3. 03

    Verify

    A model proposes parties and facts. Only a quote that appears word for word in its cited recital is kept. Anything else is refused.

  4. 04

    Report

    A monthly bulletin and a case report per important decision, where every figure, date and name points back to its source.

The quote gate

If it is not in the decision, it is not in the report.

A party named in a decision must quote its recital word for word. The comparison forgives line breaks and footnote numbers, never a changed word. A model can propose; only the decision's own text lets a proposal stay.

Try it in the tutorial

The level table

Fixed before the first case. One input: the document type.

Not the fine, not the parties, not the sector. The table is versioned, hashed and names its reviewers, and every bulletin repeats the hash of the table that sorted it.

Read the full table
  • 1Infringement finding with a sanctionCard + full report
  • 2Possible victims identified or a sanction announcedCard + short report
  • 3Notable, weak link with damages claimsOne table row
  • 0RoutineCounted only

Principles

Rules the code enforces, not guidelines.

Nothing invented

Every figure, date and name cites a recital, a press release or a URL. An invented quote is answered with a 422, not stored.

Estimates say “estimate”

Deadlines, exposure and population counts carry their legal basis and a caveat. A missing input is named, never guessed.

Hypotheses are labelled

Parties the decision does not name are shown as “Added by BINA”, under a heading that says they are hypotheses, not findings.

Client lists stay local

Watchlist matching runs on your machine. Client names and reviewer identities never enter a model prompt.

For developers

One process, one log, a plain HTTP API.

Run BINA locally against the sample inventory in five minutes, then explore every radar route.

$ npm install
$ npm run dev
$ curl 127.0.0.1:8787/v1/radar/levels