Your data, explained.
What Veyra stores, who can see it and the controls available in this preview.
Shared beta and private accounts
The early-access password opens a shared beta. Notes, tracked wallets, rules, paper activity and test results in that workspace can be seen or changed by other people with access. The password is not a personal account. Do not save private or identifying information there.
When private accounts are configured, account data is scoped to the signed-in user. Research collections can be shared with explicitly invited members.
Information used by the product
- Website access uses a signed session cookie. A separate browser-session identifier counts recent activity; it does not identify a person or trading bot.
- Private accounts use email and, where configured, Google sign-in. Password accounts store salted password hashes. Verification and recovery links are single-use and time-limited.
- Saved research includes public wallet addresses, notes, evidence, rules, paper activity and review history. Optional Telegram contact requires permission and is not a login or recovery method.
External services
Public market and wallet lookups contact the relevant data providers. Optional AI sends the evidence described by the consent control to a configured AI provider. Email requires a configured delivery provider. Availability and coverage can differ by service.
Veyra does not request seed phrases or private keys. Live order submission is disabled.
Export, contact preferences and deletion requests
Signed-in private users can export their account data and record or cancel a deletion request in Account data controls. A request records intent for review; it does not immediately delete data. Shared-beta users cannot delete the shared workspace through this control.
Research collections also offer their existing exports where access permits. Removing a Telegram handle removes the stored contact preference.
What is still pending
A full retention schedule, named privacy contact and commercial privacy notice have not been published. Host backups and provider logs may have separate retention. Veyra does not claim that a deletion request has removed those records.