“Embedded wallet” is a funny marketing term. It borrows legitimacy from embedded systems, which suggests that the wallet is part and parcel of the application

In reality, it’s a “hosted” wallet - the host (aka the SaaS provider) can revoke access to the wallet as soon as their customer (the app) stops paying

Oh interesting — i hadn’t thought about embedded systems, for us was about the relationship to the product experience, trying to make onchain actions a natural part of user interactions. 

We actually wrote a bit about it at the time (https://www.privy.io/blog/embedded-wallet-launch) but iirc term was from @gaby

FID 83. Investor at TCG Crypto. Farcaster power user. nf.td/gaby

friendly neighborhood anon // crypto angel + advisor + shitposter

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

There are really cool ways providers can ensure users can always access wallets, outage or not, payment or not (in our case this is why we have a lot operating client side)