> ## Documentation Index > Fetch the complete documentation index at: https://docs.privy.io/llms.txt > Use this file to discover all available pages before exploring further. # User wallets Privy enables you to embed non-custodial wallets for users directly in your product — no separate wallet client, like a browser extension or a mobile app, required. Users retain full custody of their wallets without needing to manage seed phrases or private keys directly. Neither Privy nor your application ever sees a user's private key. Read below to learn how Privy powers non-custodial embedded wallets for users across onchain social experiences, earning yield, trading, modern neobanking, cross-border remittances, and more. ## Key management Privy's [key management system](/security/wallet-infrastructure/architecture) uses distributed key sharding so that no single party, including Privy, ever holds a complete private key. Keys are only reconstituted in memory inside secure trusted execution environments (TEEs) at the moment a signature is required and only with the user's explicit authorization. This gives users full custody of their assets while eliminating the operational burden of key management themselves. ## Policies and controls Privy ties wallet usage directly to [user authentication](/authentication/overview). Given a valid user access token from your authentication service ([Privy](/authentication/user-authentication/privy-auth), [in-house](http://localhost:3000/authentication/user-authentication/jwt-based-auth/overview), or otherwise), Privy authenticates the user before their wallet is reconstituted in the TEE. This ensures that actions with wallets can only be taken with explicit authorization by the user. Embedded wallets can also be configured with [policies](/controls/policies/overview) to ensure guardrails for users. Your product may configure rules including allowed tokens and chains, allowed recipients, maximum transfer values, and more. ## Transactions Privy supports transactions across [all EVM chains, all SVM (Solana) chains, Tempo, Bitcoin, Spark, Tron, Stellar, and more](/wallets/overview/chains). Privy offers both low-level RPC and high-level wallet actions interfaces for executing transfers and swaps across these chains. With embedded wallets, users sign transactions directly from your product; not an external surface. You can choose to prompt users for transaction authorization using Privy's [default UIs](/wallets/using-wallets/ui-components#react) or [your own](/wallets/using-wallets/whitelabel#react). Once users authorize a transaction, Privy executes the signature and broadcasts the transaction onchain. Privy also offers native [gas management](/wallets/gas-and-asset-management/gas/overview) on EVM and Solana. Your product can sponsor gas for all users with, or you can have users pay gas in non-native tokens like USDC. ## Funding Privy offers several [funding integrations](/wallets/funding/overview) to enable users to smoothly onramp funds to their wallet, across various source currencies, destination currencies, and geographies. [Funding methods](/wallets/funding/configuration) include card payments, bank transfers, and crypto deposits with universal deposit addresses across EVM chains, Solana, and more. Privy uses a network of funding providers including [Stripe](https://stripe.com/), [Bridge](https://bridge.xyz/), [Meld](https://www.meld.io/), and [MoonPay](https://www.moonpay.com/) to over global support for account funding. ## Get started Provision a non-custodial wallet for a user Execute transfers, swaps, signatures, and more Enable actions with wallets when users are offline Enable wallet funding for users.