Wallets and ownership
Flowlex uses a non-custodial wallet model: your available assets are held in your Safe smart account, and your liquidity-position NFTs belong to that account. Flowlex does not collect your wallet balance into a company custody account. Your connected wallet or Privy embedded wallet provides the signer that authorizes actions.
This distinction matters when you add funds, approve a transaction, or manage your account outside Flowlex.
Two roles, two addresses
| Component | Its role |
|---|---|
| Your signer | Authorizes actions. This is your connected external wallet or your embedded wallet provided through Privy. |
| Your Safe smart account | Holds available tokens and owns your liquidity-position NFTs. It executes authorized transactions on-chain. |
| Flowlex | Prepares transactions, displays estimates and activity, and provides the interface for managing positions. |
The signer and the Safe have separate addresses. The address shown for funding in Flowlex is your smart-account address. Sending assets to the signer address does not automatically put them into your Flowlex wallet balance. Follow the network, token, and address shown in Wallet → Add funds.
How your account is created
With an external wallet, you connect a wallet you already control. Flowlex derives a Safe account with that wallet as its owner and uses it to authorize transactions. Connecting the wallet does not make Flowlex an owner of the wallet.
With email, Google, or Apple, Privy handles authentication and provides an embedded wallet for an account that needs one. That embedded wallet becomes the signer for the associated Safe. You use a familiar login while transactions still operate through blockchain addresses.
A Safe address can be calculated before its contract is deployed. Deployment can happen with its first on-chain action. Deployment and balances are network-specific, so always use the funding options shown in the app.
What Privy does
Privy supplies authentication and embedded-wallet infrastructure. Its current architecture stores private-key material as encrypted shares across separate security boundaries and uses secure execution environments for authorized signing. An individual share cannot independently control the wallet. See Privy’s security architecture.
Privy’s client SDK creates embedded wallets with user owners by default. Its broader platform also supports separately authorized signers and policies; control depends on the wallet’s configuration. Flowlex’s ordinary position actions use the wallet signing client after you initiate the action. See Privy’s user-wallet model.
What Safe does
Safe is a smart contract account. It checks authorization and executes the requested calls. Flowlex uses account-abstraction infrastructure to batch related calls and support sponsored network fees. The standard Safe module checks the account owners’ signatures before executing an operation; submitting or sponsoring it does not make the service an owner. Safe explains this execution flow.
Token and NFT approvals give a particular contract permission to act on specified assets under its rules. They do not transfer ownership of the Safe itself. Review approvals and actions before confirming. The contract reference identifies the components used on Base.
Where your assets are held
In the ordinary Flowlex flow, available tokens stay in your Safe between transactions. Transfers and contract spending follow the account’s authorizations and any approvals you have granted. When you provide liquidity, the underlying tokens are deployed in Uniswap and your Safe owns the NFT representing the position. During execution, tokens can pass through Flowlex’s management contract for swaps and settlement. Resulting proceeds and unused tokens return to your Safe.
Read the transaction lifecycle for the complete path. The management contract’s administrator can pause its supported operations. This does not transfer position ownership, but it can affect actions through that contract. Ownership and risks explains the practical limits.
Keep access to your account
Protect the external wallet or login method associated with your signer. Where embedded-wallet export is available, it exports the signer’s key. Assets stay at the Safe’s address. To manage them independently, you need the signer, the existing Safe address, compatible tools, and network fees.
Export availability differs by app version. Never share private keys, recovery phrases, or verification codes with anyone, including support.