Skip to main content
Dutch Ministry of Justice pilots mintBlue for fraud signal exchangeRead the story

Share what is needed.
Know who is asking.

Selective disclosure shows each party only what it needs. Every request is signed and carries a mandate, and organisations can match cases without pooling data.

Share what is needed.
Know who is asking.

Trusted by government and industry

Belastingdienst
Ministry of Justice and Security
National Office for Identity Data
VISMA
Dockflow
NOWATCH
Sheltersuit

Most checks still move the whole record.

To answer one question, such as whether a person is known or a document is valid, departments and organisations often exchange complete records. A login shows who signed in, but not on whose behalf they acted or on which legal basis.

Here each field travels with its own key, and each request with its mandate.

Share the record

  • Whole records exchanged to answer one question
  • Copies kept by every party that asked
  • Logins show access, not authority
  • Mandates kept on paper and checked afterwards

Share what is needed

  • Each field encrypted with its own key
  • The other party opens only what it needs
  • Every request signed by its sender
  • Mandates checked before anything moves

Privacy-enhancing technologies (PET), in three layers.

The building blocks that decide who sees what, who may ask and what can be computed together. Each layer adds to the one below.

01

Selective disclosure

Share only what is needed. Each field has its own key, so the other party opens only the fact it needs. Every request is signed and checked against its mandate first.

  • Field-level encryption
  • Keys per recipient
  • Signed requests
  • Mandates

02

Auditing

Prove what happened. Every check lands in a tamper-evident audit trail, which auditors and supervisors can follow in real time without opening the data.

  • Signed events
  • Tamper-evident audit trail
  • Audit-only access
  • Real-time supervisor access

03

Multi-party computation (MPC)

Compute together without pooling data. Organisations learn whether they hold the same case, and a match only shows when enough of them hold it.

  • Blinded tokens (OPRF)
  • Threshold matching
  • MPC over new events, not whole datasets

How a check works

One question, answered without the file.

How a check between two organisations works, step by step.

View customer stories
  • 01

    A request with a mandate

    An employee asks another organisation a question on behalf of their own, for example whether a document number is known. The request is signed and carries the mandate it relies on.

  • 02

    Checked before anything moves

    The receiving side checks the signature and the mandate. If either is missing, expired or out of scope, the request is refused and nothing is shared.

  • 03

    Only the answer travels

    The answer comes back as a yes or a no, or as the one field the requester is entitled to. Every other field stays closed.

  • 04

    Recorded for the auditor

    Request, mandate and answer are recorded in the audit trail, so an auditor can later see who asked what and on which basis, without seeing the content.

Compared with logins and signatures

  • Proves who sent a request

    Logins (OAuth, SAML):
    Per session
    Signed documents (PKI):
    Per signed document
    mintBlue:
    Per request
  • Shows on whose behalf

    Logins (OAuth, SAML):
    Through roles inside one organisation
    Signed documents (PKI):
    The organisation in the certificate
    mintBlue:
    A mandate with every request
  • Shares only what is needed

    Logins (OAuth, SAML):
    Depends on each interface
    Signed documents (PKI):
    The whole document
    mintBlue:
    Each field has its own key
  • Checked before anything moves

    Logins (OAuth, SAML):
    At login
    Signed documents (PKI):
    When the document arrives
    mintBlue:
    On every request
  • Can be checked afterwards

    Logins (OAuth, SAML):
    In the provider's logs
    Signed documents (PKI):
    Through the signature
    mintBlue:
    In the audit trail

This complements your login system. People still sign in as they do today; mintBlue adds a signature and a mandate to each exchange between departments and organisations.

Frequently asked questions

Privacy

Technical

mintBlue platform illustration

Next step

Bring the question you have to answer.

Which question does another department or organisation need answered, and what may not leave yours? We work out which fields travel and which mandate each request needs.