Privacy Policy
This policy explains what YSeed intentionally does not collect, and the limited technical data that can still exist when any public website is loaded.
Direct answer
YSeed does not ask for an account, email, payment, wallet connection, or seed phrase upload. Seed phrases are generated and validated in the browser and are not intentionally sent to YSeed servers.
Data YSeed is designed not to collect
- Seed phrases, recovery phrases, private keys, xpubs, addresses, or wallet balances.
- Account details, payment details, or customer profiles.
- Form submissions containing wallet secrets.
- Analytics events that include generated phrase text.
Browser storage
YSeed may save one local preference: the visual theme. The storage key is yseed-theme. Generated seed phrases are not intentionally written to localStorage, sessionStorage, cookies, or URL parameters.
The site also registers a service worker to support an offline-ready workflow. The service worker caches public site files such as pages, scripts, styles, and the manifest. It does not cache generated seed phrase text.
Technical request data
Like most public websites, YSeed is served through hosting and security infrastructure that may process basic request data, such as IP address, user agent, requested URL, timestamp, and security events. This can happen at the web server, reverse proxy, CDN, firewall, or hosting layer.
YSeed's product design does not require that request data to include a seed phrase. Do not put a seed phrase in a URL, support message, or any field on any public website.
Clipboard and screenshots
If you copy a phrase, your browser, operating system, clipboard manager, or device ecosystem may retain or sync clipboard content. Screenshots, cloud notes, printers, and screen sharing can also leak secrets. Copy only for tests or controlled offline workflows.
Contact and updates
YSeed is currently published as a static educational tool. A dedicated legal operator and support inbox have not been published on this page. This policy should be reviewed again before adding accounts, analytics, forms, payments, or commercial support flows.
Effective date: May 26, 2026.