1. Data we collect
If you join the waitlist, we store your email, optional name, consent version, signup source, timestamps, and a hashed version of your one-time deletion code. If you sign in, the platform supplies a stable user identifier so UnionFolio can store your strategy draft and application activity. Your account email and display name are shown in the workspace but are not copied into UnionFolio’s strategy tables. We also keep daily aggregate counts for page views, wallet connections, and waitlist signups.
2. Data kept on your device
A connected wallet address and mainnet ETH balance are read directly in your browser. Guest strategy drafts are stored in local browser storage. Signed-in drafts are also synced to UnionFolio’s database under the platform-supplied user identifier.
3. Data we do not add to analytics
UnionFolio’s application analytics do not store wallet addresses, balances, IP addresses, browser fingerprints, user agents, referral URLs, or individual browsing histories. Wallet addresses and balances are not added to cloud strategy records.
4. Why we use the data
Waitlist data is used to understand beta interest and, once a verified contact channel exists, to communicate about access. Signed-in strategy and activity records provide workspace sync. Aggregate counts help us measure broad product usage without building trading profiles.
5. Service providers
The site and database are hosted by infrastructure providers that may process ordinary technical logs for security, reliability, and delivery. Robinhood market APIs, TradingView widgets, wallets, RPC endpoints, and explorers are separate third-party services with their own privacy practices.
6. Retention and deletion
Waitlist records are kept while the preview remains relevant or until removed. Keep the deletion code shown after signup; it is the self-service proof used to delete the matching record. Guest dashboard drafts remain until you reset them or clear browser storage. Resetting while signed in also deletes the cloud strategy profile; the reset event remains in the application activity ledger. Aggregate counts cannot identify you and are retained for product measurement.
7. Security and sharing
Deletion codes are stored only as one-way hashes and are unrelated to wallet private keys. We do not sell personal data. No system is perfectly secure, and this prototype should not receive sensitive financial information, seed phrases, private keys, identity documents, or account balances.
8. Final policy
A production policy will add the operating entity, contact details, applicable privacy rights, international transfer terms, and jurisdiction-specific notices after those facts are established.
Remove your waitlist record
Enter the same email and the one-time deletion code issued after signup. If both match, the record is deleted immediately.