Privacy notice
Updated 30 October 2026 · Pre-launch disclosures
What stays in your browser, what reaches our services, and what becomes public.
Wallet and transaction data
Connecting a wallet exposes its public address and network to the app, not its private keys. The API and RPC providers process addresses, balances, allowances and transaction details to quote, simulate and track trades. Wallet-balance caches last 30 seconds. Public addresses and transaction hashes can identify or be linked to a person; public blockchain data is not necessarily anonymous.
x402 purchase checkout records
When you use the x402 purchase relay, the server stores checkout records that include wallet addresses, signed transactions and transaction hashes. Live checkout records expire 24 hours after creation. Backups may retain copies longer, and public blockchain records do not expire. These records are separate from purchase telemetry and browser storage.
Stored in this browser
Local storage keeps your selected network, named saved portfolios, one editable allocation per network and a transaction journal containing wallet addresses, transaction hashes, expected calls and receipt information. Wallet software may also store connection preferences or sessions. These support draft restoration and transaction recovery, rather than advertising. Session storage also carries a selected allocation and deposit amount from My portfolio to the purchase editor. Clear site data in your browser to remove local records; doing so also removes recovery information and does not delete server records or blockchain transactions.
Transaction receipts are recent browser records, not a complete account history. Imported activity archives stay in local storage and remain unverified. Downloaded backups contain wallet addresses and trading information; protect those files and delete them separately from site data. Files selected for restore are read locally, not uploaded to our API. Calendar reminders are optional downloads containing your saved target’s name; importing one shares that information with your calendar provider. Manage or cancel the reminder in that calendar. Neither import grants wallet access.
Independent price context
When enabled, our server requests security prices and market hours from Financial Modeling Prep and USDC/USD references from CoinGecko. These requests identify the asset, not your wallet, holdings or purchase amount. Reference data may be delayed or unavailable and does not determine whether a transaction is safe or legally eligible.
AI search and suggestions
Search and allocation prompts, together with public asset identifiers, are sent to TypeSafe AI to generate results. The app does not include wallet addresses or credentials in those requests. Do not put personal, confidential or financial-account information in a prompt. The app server does not persist prompts or results; an allocation can be saved as a local draft without its prompt. Provider processing and retention are separate from the app’s storage.
Purchase telemetry
When enabled, first-party telemetry measures prepared reviews and verified purchases to understand usage. It retains asset identities, allocations, quantities, issuer choices and optional bundle IDs for up to 90 days, subject to a record limit. Events include a pseudonymous buyer ID: a 16-character SHA-256 hash of the purchase wallet address that groups repeat purchases from one wallet and can be recomputed by anyone who knows that address. These event records omit raw wallet addresses, transaction hashes, prompts, IP addresses and browser IDs, but may still be linkable to public activity. Temporary transaction hashes and transaction fingerprints used for verification expire after 24 hours. This is not a complete account history.
First-party browser funnel telemetry separately collects only an allowlisted interaction stage, supported network when applicable, optional elapsed duration capped at five minutes and an optional reason of cancelled, unavailable or failed. It stores daily aggregate counts and duration totals/counts for up to 30 days, not individual browser events. These aggregates contain no prompts, wallet addresses, amounts, asset IDs, arbitrary error messages, IP addresses or browser/session identifiers. They are unverified usage signals, not unique people or proof of purchase. Collection sends no cookies or referrer and uses no browser tracking storage. Do Not Track and Global Privacy Control suppress this browser collection, but not the separate server-verified purchase records described above.
What you publish is public
Shared bundle titles, networks, allocations, issuer choices and any creator fee and recipient address are public. Published bundles are stored without an automatic expiry; unpublished drafts expire after ten minutes. Links and preview images can be copied or indexed by third parties. Do not include personal information in a title. Removing browser data does not unpublish a bundle or remove third-party copies.
Other services and network requests
Hosting and network providers receive connection information such as your IP address. The API uses a hashed caller IP for rate limiting, with counters expiring after 70 seconds. RPC and routing services process requests needed to display balances and execute trades. The site loads Google Fonts and some token images from external hosts, which receive browser requests. When WalletConnect is configured and chosen, its relay and wallet services process app metadata and session information. Following issuer, explorer or social links takes you to separately operated services. Their privacy practices and retention periods also apply.
Your rights and publication details
Depending on applicable law, you may have rights to access, correct, erase or obtain a copy of personal data, restrict or object to processing, withdraw consent where processing relies on it, and complain to a data protection authority. Blockchain records and independent third-party copies cannot simply be erased by this app.
This pre-launch notice describes the current implementation. Before public launch, the operator must publish its identity and privacy contact, the applicable legal bases, provider/log retention, international-transfer safeguards and a working rights-request process. These details have not yet been finalized; this notice is not a claim of GDPR compliance.