OBolo is live — free on the App Store and Google Play
The platform

Trust, as architecture.

Most platforms begin with a permanent identifier and treat every connection the same. OBolo begins with the person, the context of each relationship, and continuing permission.

The organising idea

Every layer answers one question.

Every future flow, screen and policy in OBolo inherits this stack — so trust behaves the same everywhere.

LayerControlling questionWhat it provides
Registration IdentityCan the platform trust this account?Mobile + OTP, device biometrics, recovery and fraud controls
Identity IsolationWhere does exposure stop?A permanent boundary between credentials and relationship identity
Dynamic ID™How do I connect without exposing credentials?A readable identity, Dynamic QR, Dynamic Link, contextual attributes
Identity ExchangeHow do relationships begin?Declared purpose, displayed permissions, informed acceptance
RelationshipWhy are we connected?Purpose, consent and a governed lifecycle
LifeSpace™What trust context applies?Eight approved Trust Zones
Identity Permission Engine™What may occur, right now?Runtime decisions from relationship, context, role and policy
Privacy Hedge Layer™What may be seen or disclosed?Tokenisation, shielding, minimisation, anti-abuse controls
Seven O ExperiencesWhat can we do together?Chat, calls, meetings, moments, tasks, files and channels
Data TrustHow is everything protected and proven?Encryption, keys, audit and integrity datasets
The model

Not a contact list. A relationship system.

Every accepted connection on OBolo carries a declared purpose, a LifeSpace™, a visible permission model and a governed lifecycle.

Declared purpose

Why are we connecting? Stated up-front, before anything is shared.

A LifeSpace™

The trust context that sets sensible defaults for the relationship.

A permission model

Exactly what each side may see and do — visible and adjustable.

A lifecycle

Relationships evolve, pause, restrict or close — cleanly and completely.

Relationships define intent. The Identity Permission Engine™ enforces intent.
Honest positioning

What OBolo is not.

Not merely a messaging app

Messaging is one of seven expressions of a deeper relationship architecture.

Not a network built on exposure

No engagement traps, no public-by-default identity, no attention economics.

Not a financial identity wallet

Deliberately non-financial: no banking, payment, statutory, KYC or credit identity — ever.

Not an advertising system on hidden profiling

Commercial reach exists only through permissions people granted — and can withdraw.

Start with the layer that changes everything.

The Dynamic ID™ is where separation begins — and where trust becomes portable.