OBolo is live — free on the App Store and Google Play
For government & regulated sectors · a forward-looking vision

Citizens deserve official communication they can trust on sight.

A vision for verified, permission-based, auditable service communication — with one bright line, always: service communication on OBolo; statutory records on official systems.

Framing

What this page is — and is not.

A vision for dialogue. This page describes a forward-looking possibility (P2G — Person ↔ Government) in the OBolo roadmap. It is presented for discussion with government and regulated sectors, not as a deployed capability. Statutory records and legal identity remain on official systems throughout.
The challenge

When citizens can’t tell government from fraud.

Impersonation at scale

Fake “department” SMS, phishing links and spoofed caller IDs erode trust in every legitimate message.

One number for everything

Family calls, bank OTPs, marketing spam and official communication arrive indistinguishably on one personal number.

Fragmented outreach

Each department builds its own lists, apps and portals — duplicating cost while citizens juggle channels.

Weak accountability trails

Who was reached, on what basis, with what consent — often difficult to evidence across ad-hoc channels.

The core principle

Service communication is not statutory records.

Service communication

Could flow through OBolo Dynamic ID™
  • Announcements, advisories and service updates
  • Appointment, utility and civic reminders
  • Grievance acknowledgements and follow-ups
  • Community and ward-level participation
  • Delivered from verified, clearly identified official presences

Statutory identity & records

Remain exactly where they are today
  • Legal identity, registered numbers and official records continue on existing statutory systems
  • No replacement of any government ID, registry or KYC process
  • No financial, tax or benefits identity on OBolo
  • Where law requires official identifiers, official identifiers are used
Governed and accountable

Bounded authority. Distinguished classes. Auditable proofs.

Verified institutional presence

Departments operate from verified Spaces with role-based administration — citizens always know exactly who is speaking.

Authority stops at the role

Institutional administration governs institutional space only — it never absorbs a citizen’s personal identity or activity.

Distinguished message classes

Transactional, regulatory, advisory, community and emergency communication are architecturally distinct — and look it.

Integrity proofs, not surveillance

Consent receipts and authorisation records on tamper-evident datasets — with no personal content on any immutable ledger.

Lawful requests, lawful process

Valid legal requests are honoured under applicable law and published policy — through restricted, auditable channels.

Inclusion as a condition of trust

Understanding, accessibility and control across languages, abilities, devices and levels of digital familiarity.

The path

P2P → P2O → P2G. An evolution, not a leap.

PhaseWhat it proves
P2P — Person ↔ PersonThe identity and permission model, proven at human scale across families, friendships and work
P2O — Person ↔ OrganisationVerified institutional practice, as businesses and communities replace number-collection with permission
P2G — Person ↔ Government (future possibility)The same verified, auditable, permission-based channel applied to public service communication
Government participation would inherit an identity, permission and audit architecture already proven across millions of everyday relationships.

Begin the dialogue.

Requirements, safeguards and a scoped pilot concept for one service domain.