AddressKey, a consent layer for verified addresses

Address data is broken on both sides. People re-type the same address into every service and lose track of who still holds it; organisations sit on stale records they can't refresh without a mailout or a call. Nobody has a consent trail, so a change of address means dozens of disconnected updates and no way to prove who agreed to what.

Treat the address like a credential the person owns, not a field every company copies. AddressKey puts a consent layer between people and the organisations that need their address: verified profiles on one side, trust-credentialed organisations on the other, and an auditable permission grant in the middle. Data minimisation and rev-at-any-time are defaults, not settings, the same design discipline we bring to custody and payments infrastructure.

We built the MVP end to end: verified address profiles (home, mailing, business, and other), a consent engine for approve / deny / revoke, update orchestration so one address change fans out to every connected organisation with delivery status, and a trusted inbox for requests, notices, and verified messages. Organisations get trust credentials, verification badges, partner APIs, and signed webhooks; every action lands in an audit log the person can see. The whole exchange is consent-first and logged on both sides.

AddressKey is live as a working MVP and open for pilots with organisations that manage address updates, trusted messaging, supplier verification, property workflows, or civic delivery. It's the most infrastructure-grade product in the Lite Launch studio, the same security-first, audit-everything approach we apply to blockchain and payments work, pointed at digital trust.