Introducing AddressKey: a consent layer for verified addresses

We build our own products in the same studio we build client work in. AddressKey is the newest, and the most infrastructure-grade thing we've shipped: a consent layer for verified addresses. It's live as an MVP and open for pilots. Here's what it is and why we built it.

The problem: address data is broken on both sides

Your address is one of the most-shared pieces of data you own, and nobody handles it well. You re-type it into every checkout, every account, every form, then lose track of who still has it. On the other side, organisations sit on records that quietly go stale, with no clean way to refresh them and no proof of who agreed to what. A single change of address turns into dozens of disconnected updates.

The missing piece isn't another address form. It's consent, a way for the person to own the record and decide, per organisation, who gets it and for how long.

What AddressKey is

AddressKey sits between people and the organisations that need their address, and makes every exchange explicit and auditable.

For individuals

• Verified address profiles, home, mailing, business, and other.
• Grant, deny, or revoke access to any organisation, at any time.
• One update that fans out to every connected organisation, with delivery status.
• A trusted inbox for requests, notices, and verified messages.
• An audit log of who accessed what, and when.

For organisations

• Request consented address data instead of buying or guessing it.
• Trust credentials and verification badges so people know who's asking.
• Partner APIs and signed webhooks to wire consent into existing systems.
• A clean audit trail on both sides of every exchange.

Why we built it the way we did

The same discipline we bring to custody and payments infrastructure applies here: assume the data is sensitive, minimise what you collect, and log everything. Consent and revocation are defaults, not buried settings. Data minimisation is the design, not a policy page. Every access leaves a signed trail the person can see. If that sounds like how we talk about blockchain and payments work, that's the point, this is the same security-first approach pointed at digital trust.

It's also built in Canada, for privacy-first workflows, which matters for the organisations we're piloting with, government, financial institutions, property managers, and brands that need consented address data rather than stale lists.

Where it's at, and who we're looking for

AddressKey is a working MVP, not a live-at-scale product yet, and we'd rather say that plainly than dress it up. We're opening pilots now with organisations that manage any of the following:

• Address updates and change-of-address workflows.
• Trusted messaging, notices, offers, surveys, that need verified recipients.
• Supplier or business verification.
• Property and tenancy workflows.
• Civic delivery and government correspondence.

The bigger picture for the studio

Most of the products in our studio are consumer apps. AddressKey is different, it's infrastructure other organisations build on, which is where a lot of our recent work has been heading. It shares a lot with the fintech and blockchain systems we ship: verified identity, consent, signed audit trails, and integration APIs that have to be right the first time.

If you want the fuller build story, read the AddressKey case study.

And if your organisation handles address data and any of the pilot workflows above sound familiar, request a pilot at addresskey.ca, or talk to us directly.