Contact and security reports
YSeed's most important support rule is simple: never send a real seed phrase to anyone, including someone claiming to represent YSeed.
No phrase APInothing posts your wordsMemory-only phrase statetheme is the only saved settingNarrow by designno keys, xpubs, addresses, or balances
Direct answer
YSeed has not published a direct support inbox yet. Until one is added, use the public security model and methodology pages for verification, and do not send wallet secrets through any channel.
Never send these
- Real seed phrases or recovery phrases.
- Private keys, xprv values, xpub values, or keystore files.
- Wallet screenshots that reveal balances, addresses, or recovery details.
- Clipboard history, cloud notes, or backup photos.
Useful report details
A safe security report should describe the affected page, browser, operating system, reproduction steps, expected behavior, observed behavior, and whether the issue affects phrase generation, validation, storage, service worker caching, or external requests.
Do not include a real wallet phrase as proof. Use a known public BIP39 test phrase or a phrase generated only for the report.