Purple Wallet for Chrome and Safari

Get it

Coming to Chrome and Safari.

It's built and it works. It isn't in the stores yet — when it is, these buttons light up and installing takes one click.

Chrome Web Store Safari Extensions

Want to know when? team@purplewallet.app

Run it from source

For anyone who'd rather not wait. You'll need a checkout of the repository and Node 18 or later.

Chrome, Edge, Arc, Brave

Run ./purple ext. It tests, builds, and copies the folder path to your clipboard.
Open chrome://extensions and switch on Developer mode.
Load unpacked, and paste.
Sign in to American Express, open your offers page, then click the toolbar icon.

Safari

Safari won't load a folder — an extension has to be wrapped in a Mac app first. ./purple ext safari runs Apple's own tool for you and opens the Xcode project it writes.

./purple ext safari
Build and run the project that opens.
In Safari: Develop → Allow unsigned extensions, then enable it in Settings → Extensions.

Safari 18 or later. The unsigned-extensions switch resets when Safari restarts — that's Apple's design, not a fault here.

What it does, and doesn't

It reads one page. That's the whole job.

No bank login, ever. You sign in to your issuer yourself, in your own browser. The extension has no login screen and never will — there is nothing for it to store, so there is nothing for us to lose.
It asks for two websites. Storage, and your issuer's offers pages. Nothing else. Other extensions in this category request access to every site you visit, because they also inject themselves into shop checkouts. We don't do that, so we don't ask.
We can't read what it finds. Your offers are encrypted on your device before they are stored, with a key that never reaches us. We hold the ciphertext so your phone and your browser stay in step. The privacy page says exactly what we can still see.
It reads. It does not click. Activating offers on your behalf is a different thing with different risks, and it isn't in this version.
Amex first. More issuers follow. Some banks block extensions outright — where that happens we'll say so plainly rather than quietly returning less.

The part everyone else gets wrong

When it breaks, it goes quiet.

Every tool that reads bank sites has the same weakness: the bank changes something, the reader half-works, and the app starts showing offers that are stale or wrong — with nothing in the system aware anything happened. Three offers where there were twelve looks like a quiet month. Nobody investigates a quiet month.

So ours refuses to half-work. It checks that what came back is the shape it was written for, and if a single offer doesn’t read cleanly, it discards the whole batch and reports itself broken. You get nothing rather than something wrong, and we find out the same day.

It also doesn’t rummage through the page looking for text to match. It asks your issuer for the same list their own site is asking for, and reads the answer — which is why a visual redesign doesn’t touch it, and why it adds no work for your bank beyond what your own browser was already doing.

The same rule runs downstream: an offer the extension found never changes a recommendation on its own. It has to survive the check that it actually paid out first.