Skip to content
Registry · The foundation

Granite Registry

Identity, consent and data governance, enforced in the infrastructure.

All of Granite

The layer nobody sees that makes every other part trustworthy

Users never interact with the Registry directly. It holds verified identities, enforces data-access rules, and ensures that consent given by any person is technically honoured — not merely promised. It is the neutral identity and consent layer that makes interoperability possible in the first place.

Registry · consent gate
Enforced
OEG-UGA-2026-8F2C
Horizon Relief
scope: Identity, Contact
Allowed
OEG-UGA-2026-A91E
Coastline Aid
scope: Needs
Allowed
OEG-KEN-2026-3D7A
Open Aid Foundation
scope: Full record
Rejected
Audit · 14:02 · Horizon Relief read Contact under grant #4412 — visible to the person
Core characteristics

What makes Granite Registry different

  • Consent as a technical gateAn access request outside the scope of active consent is rejected automatically. No manual review, no exception pathway that depends on goodwill.
  • Data minimisation by designThe model holds only what is needed to establish identity, verify uniqueness and enforce consent. A request returns only the fields in scope, never the full record.
  • Permanent, portable identityEvery person receives a Personal ID that belongs to them and travels with them across organisations, responses and borders.
  • Neutral governanceOperated by Connectance as a neutral infrastructure provider. No single organisation controls it, no government holds the master database, no data buyer can reach it.
  • Auditability as a rightEvery access is logged immutably — who, what, when, under which consent — and surfaced to the person in their app.
The rest of the platform

Granite is one platform, six parts

Want to see Granite in the field?

We are consulting organisations, funders, and refugee-led groups on what shared infrastructure should do. Tell us where you fit.

Get in touch