Website data
The website does not set advertising cookies or collect wallet addresses, balances, signatures, API credentials, or trading identifiers. It contains privacy-safe event hooks for aggregate actions such as an access click; no analytics service is active unless the site is later configured with one. Like most hosting services, infrastructure providers may temporarily process IP address, user agent, requested path, and timing data to deliver and protect the site.
App data by function
Hosted sign-in and embedded wallets
If you use hosted sign-in, Privy processes the identity information needed for the selected method, such as email or identity-provider account information, and provides embedded-wallet services. Amethyst receives the user and wallet identifiers necessary to maintain the session.
Connected wallets
If you connect an external wallet, Reown/WalletConnect and the wallet provider process pairing and session messages. Amethyst receives the public address, selected chain, and approvals needed for the requested action.
PERPL trading
Amethyst sends public wallet addresses, enrolled API-key public material, signed API requests, orders, account queries, and transaction-related data to PERPL. The Ed25519 private key stays in the iOS Keychain. PERPL returns market, order, position, fill, and account state used by the app.
Monad and public blockchain data
Wallet addresses, contract calls, token approvals, deposits, withdrawals, transaction hashes, and balances can be publicly visible on Monad. Amethyst and RPC providers read and submit blockchain data. Public blockchain records generally cannot be deleted.
Diagnostics and support
Amethyst does not silently upload the private-beta diagnostic snapshot. You choose whether to copy and send it to support. It can include app/build version, environment, connection health, and redacted state needed to diagnose a failure. Do not send secrets or unredacted credentials.
Why data is processed
Data is processed to authenticate the selected wallet path, enroll and use the limited trading key, display market and account state, submit user-requested activity, reconcile transactions, prevent abuse, diagnose failures, meet legal obligations, and support the private beta.
Sharing and providers
Data is shared only as needed with the service involved in the path you select, including hosting infrastructure, Privy, Reown/WalletConnect, wallet providers, PERPL, Monad RPC providers, and support tools. Amethyst does not sell personal information or use wallet/account data for behavioral advertising.
Retention and security
Local credentials and app state remain on the device until revoked, signed out, cleared, or the app is deleted, subject to iOS backup and Keychain behavior. Providers retain information under their own policies and legal obligations. Amethyst uses platform protections and limited authority boundaries, but no software, network, wallet, protocol, or storage system can be guaranteed secure.
Deletion and account choices
The dedicated account and data deletion page is the direct starting point. It explains identity verification, the beta support target, and the separate hosted-account and connected-wallet-only paths.
Connected-wallet-only users can review or revoke server-side keys in PERPL's key manager, then disconnect or sign out and delete the app to remove Amethyst's local relationship. Clearing the credential inside Amethyst affects only that device. These steps do not delete the external wallet or public blockchain history. Hosted-account deletion separately requests removal of the Privy identity and Amethyst-controlled support data; Privy documents that it disassociates and archives the embedded-wallet record instead of deleting the on-chain wallet. PERPL and other providers apply their own retention rules.
Eligibility and children
Amethyst is not intended for anyone under 18. Do not use the beta if you are not legally eligible where you live.
Contact
Privacy questions: use support. To delete an account or local relationship, start at account and data deletion.