Skip to main content

Privacy Policy

Last updated: November 1, 2026

1. Introduction

SelvWallet is operated by Selv, Inc., a Delaware corporation (“Selv, Inc.,” “we,” “our,” or “us”), which is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our cryptocurrency wallet service through its Telegram Mini App, and when you visit this website.

By using SelvWallet, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Non-Custodial Nature

Your SelvWallet wallet is non-custodial: its signing keys are generated and used on your device, and our servers cannot sign for it. Telegram giveaways are the exception: their prizes are held in escrow by Selv, Inc., and our servers sign the escrow payouts and refunds (see Section 8 of the Terms of Service). Telegram Mini App users may explicitly opt into a cross-device backup containing an encrypted seed and password-wrapped key in Telegram CloudStorage. Telegram receives no plaintext seed, password, private key, or raw unwrapping key through that backup.

2.2 Information We Do Collect

  • Telegram User ID: We collect your Telegram user ID to link your wallet to your Telegram account.
  • Giveaway records: If you host or win a Telegram giveaway or draw, we keep the giveaway and claim records, including Telegram user IDs, the name shown in the group, payout and refund addresses, amounts, and transaction hashes.
  • Transaction Data: Blockchain transaction hashes and public wallet addresses for transaction history display.
  • Operational telemetry: Production routes may emit sampled error, log, trace, and performance diagnostics after the shared redaction boundary, except the dedicated recovery-export realm, which loads no Sentry or telemetry code and makes no network requests; during wallet creation it only records fixed step and failure codes and step durations on the device, which the app forwards as wallet-setup diagnostics. Default PII and session replay are disabled everywhere. Vercel Speed Insights is disabled on seed, backup, unlock, signing, send, swap, and vault flows.
  • Web request metadata: Our hosting and security providers receive the client IP address, User-Agent, requested path, and timing needed to serve and protect non-Telegram web requests.
  • Connected-app data: When you connect a site or app to the Mini App through TON Connect, the wallet processes the connected-site origin and request, the account addresses you approve, the chain, and transaction or message content submitted for approval.
  • Optional Telegram encrypted backup: If you opt in, Telegram CloudStorage stores the encrypted seed and password-wrapped data-encryption key for cross-device restore. Possession permits offline password guessing. Security settings let you retain or delete and verify removal of the backup.

3. How We Use Your Information

We use the collected information for the following purposes:

  • To provide and maintain our wallet service
  • To display your transaction history and wallet balances
  • To improve and optimize our service
  • To detect and prevent fraud or security threats
  • To communicate important updates about the service
  • To comply with legal obligations

4. Data Security

Security controls reduce risk but do not make wallet software risk-free:

  • TLS protects data sent between the client and HTTPS services.
  • AES-256-GCM encrypts supported local key-storage formats.
  • Automated gates check defined signer-isolation, secret-scanning, dependency, and documentation invariants. They are partial controls, not a formal third-party audit.
  • The server is not designed to store your wallet’s private keys or recovery phrase. Giveaway escrow keys are derived on the server from a key held in its secret store, not in the database.

5. Detailed Data-Flow Inventory

The entries below identify what each current product flow processes, why it is needed, who receives it, where it persists, how long it remains, how deletion works, and the relevant user or security controls. A provider may act under its own privacy policy and legal obligations.

Account, service, security, and diagnostics

Data
Account and public-wallet identifiers, including identifiers kept from account links to services we no longer offer; sessions; audit events; coarse network prefix and browser family; path and request timing on non-Telegram web requests; redacted error and device/browser diagnostics; wallet-setup step diagnostics (fixed step, outcome, and failure codes, step durations, a random per-attempt id that is not linked to the account, and a coarse device class: CPU core count, device memory class, Telegram client version and platform, OS family and major version, WebView major version, and a key-derivation time bucket). Production routes may emit sampled error, log, trace, and performance diagnostics after the shared redaction boundary, except the dedicated recovery-export realm, which loads no Sentry or telemetry code and makes no network requests; during wallet creation it only records fixed step and failure codes and step durations on the device, which the app forwards as wallet-setup diagnostics. Default PII and session replay are disabled everywhere.
Purpose
Authenticate users, operate the service, enforce rate limits and anti-replay controls, investigate abuse, and diagnose failures.
Recipients and boundaries
  • SelvWallet service database: Account, session, audit, notification, and operational records.
  • Vercel: Web hosting, routing, request logs, and DDoS protection. Privacy policy.
  • Upstash: Short-lived hashed rate-limit and anti-replay identifiers. Privacy policy.
  • Sentry: Sampled diagnostics from production routes after shared redaction, excluding the dedicated recovery-export realm; default PII and session replay are disabled. Privacy policy.
  • Firebase / Google Cloud: Legacy authentication identifiers, hosting metrics, and request logs when that path is used. Privacy policy.
Persistence
Account, session, notification, and audit records may be stored in the SelvWallet database. Hosting, security, and diagnostics providers may retain their own operational records.
Retention
Operational audit records expire after 90 days. Authentication and security audit records expire after 365 days unless a documented legal hold applies. Identifiers kept from account links to services we no longer offer stay on the account record until the account is deleted or we remove them. Upstash entries expire automatically. Provider retention follows the provider settings and policy.
Deletion
Request access, correction, export, or deletion at privacy@selvwallet.com. Account deletion removes audit records without a legal hold; held records remain until the hold is released.
Controls
Sensitive wallet flows may emit strictly redacted diagnostics, except the dedicated recovery-export realm, which loads no telemetry code and sends nothing over the network. Wallet-setup diagnostics are built only from fixed codes and numbers: never a password, recovery phrase, key, address, wallet id, or Telegram identity. Production routes may emit sampled error, log, trace, and performance diagnostics after the shared redaction boundary, except the dedicated recovery-export realm, which loads no Sentry or telemetry code and makes no network requests; during wallet creation it only records fixed step and failure codes and step durations on the device, which the app forwards as wallet-setup diagnostics. Default PII and session replay are disabled everywhere.

Telegram Mini App identity and notifications

Data
Telegram user ID, chat ID, username, first name, last name, language code when supplied, Mini App initData verification fields, link codes and expiry, and notification message/status metadata.
Purpose
Verify Telegram sessions, link the correct SelvWallet account, resolve wallet recipients, and deliver requested wallet notifications.
Recipients and boundaries
  • SelvWallet service database: Linked Telegram profile and notification records.
  • Telegram: Mini App authentication, CloudStorage when enabled, and bot message delivery. Privacy policy.
Persistence
Linked profile and notification records are stored in the SelvWallet database. Telegram stores its own account, bot, and Mini App records.
Retention
The link remains while the Telegram integration is active or until the account record is deleted, subject to legal or security retention. Verification codes expire.
Deletion
Disconnect supported linked services where available or request unlinking, export, or deletion at privacy@selvwallet.com. Telegram-controlled records follow Telegram controls.
Controls
Telegram initData is verified before account-linked actions; the server never receives the wallet recovery phrase or private signing key.

Telegram giveaways and escrow

Data
For the host: Telegram user ID and username, group chat ID, the giveaway settings (network, token, amount, number of winners, keyword), the escrow address, the host refund address, and the funding transaction and its sender address. For each winner: Telegram user ID, the name shown in the group, the payout address and amount. Telegram message IDs, and the payout, fee and refund transaction hashes.
Purpose
Hold the prize in escrow, pay each winner, take the escrow fee, refund the host, post the giveaway and its results in the group, and reconcile escrow balances against the blockchain.
Recipients and boundaries
  • SelvWallet service database: Giveaway, claim, escrow wallet and escrow ledger records.
  • Telegram: Group messages announcing the giveaway, each win, and the result. Privacy policy.
  • Public blockchains: Funding, payout, fee and refund transactions, including the escrow, winner and host addresses.
Persistence
Giveaway, claim, escrow and ledger records are stored in the SelvWallet database. Escrow transactions are permanently public on the blockchain.
Retention
Escrow wallet and ledger records are kept as the record of funds Selv, Inc. held and moved; the database blocks their deletion. Giveaway and claim records are kept with them.
Deletion
Escrow, ledger, giveaway and claim records cannot be deleted on request while they are the record of funds held and moved. Telegram messages follow Telegram controls. Other requests go to privacy@selvwallet.com.
Controls
Escrow keys are derived on the server from a seed held in the deployment secret store, never in the database; the database stores only each escrow wallet's derivation index and public address.

Wallet reads, transaction history, and blockchain broadcast

Data
Public wallet addresses, token accounts and balances, transaction hashes and payloads, signed transaction bytes, UTXOs, fee and nonce/sequence data, and RPC request metadata. Public networks permanently expose transaction effects.
Purpose
Read balances and history, estimate bounded network fees, verify transactions, and broadcast transactions the user signed locally.
Recipients and boundaries
  • Public blockchains: Solana, EVM networks, TON, and Bitcoin permanently record transactions.
  • Configured RPC operators: Helius, QuickNode, Solana Foundation, Alchemy, Infura, Ankr, LlamaRPC, PublicNode, dRPC, Cloudflare, Base, Polygon, Arbitrum, Optimism, Avalanche, Binance, Forno, Toncenter, Mempool.space, Blockstream, and environment-configured replacements process the public address, state, fee, simulation, or broadcast request for their network.
  • Blockchair: Bitcoin public-address and transaction-history requests.
  • TonAPI: TON account status and whether an account needs a memo, for a TON address typed into a /sen tip.
  • Chain explorers: Opening an explorer link discloses the viewed public address or transaction and normal web-request metadata.
Persistence
SelvWallet may store public addresses and transaction history records. RPCs and explorers may log requests. Signed transactions are permanently stored by public networks after broadcast.
Retention
SelvWallet transaction records remain while needed for wallet history or legal obligations. Public-chain data cannot expire; provider logs follow provider policies.
Deletion
SelvWallet-controlled history and account links can be requested for deletion. Public-chain records and provider-controlled logs cannot be deleted by us.
Controls
Private keys and recovery phrases remain client-side. Transaction verifiers bind reviewed effects before local signing; providers receive only public or signed transaction material needed for the request.

Token swap quotes and routing

Data
Public wallet address, chain, input and output token addresses, amount, slippage, route and quote parameters, and unsigned transaction templates.
Purpose
Obtain executable swap quotes and routes, then verify the returned transaction before local signing.
Recipients and boundaries
  • Jupiter: Solana swap quotes, route metadata, and transaction templates. Privacy policy.
  • 1inch: EVM swap quotes, token pairs, route metadata, and transaction calldata. Privacy policy.
Persistence
SelvWallet does not deliberately persist quote requests beyond operational records and transaction history; routing providers may log requests under their policies.
Retention
SelvWallet and provider retention follows the operational and provider policies described for the relevant request.
Deletion
Request deletion of SelvWallet-controlled account or transaction links at privacy@selvwallet.com; provider-controlled logs require the provider’s process.
Controls
Client verifiers bind route output, token pair, recipient, amount limits, calldata, and fees before signing. A quote is not authority to sign.

Local wallet storage and optional encrypted Telegram backup

Data
Encrypted wallet key material, encrypted seed backup, password-wrapped data-encryption key, public addresses, settings, and session state. TON Connect sessions also process connected-site origins, requested chains, accounts, transactions, and messages.
Purpose
Keep a self-custodial wallet usable on the device and, only when selected, support encrypted cross-device restore through Telegram CloudStorage.
Recipients and boundaries
  • User device storage: IndexedDB or platform secure storage, depending on client.
  • Telegram DeviceStorage: In the Telegram Mini App, a second copy of the already-encrypted wallet, plus which wallet this device shows, the ids of wallets deleted on it and its random device id, kept by the Telegram app on the same device so clearing the web view does not lose them. It does not leave the device. Privacy policy.
  • Telegram CloudStorage: Optional encrypted backup selected by a Telegram Mini App user. Privacy policy.
  • Connected websites: Receive only approved public accounts, chain context, and signatures or responses for requests the user approves.
Persistence
Encrypted wallet data remains on the device until erased. An opted-in encrypted backup remains in Telegram CloudStorage until replaced or deleted.
Retention
Device and optional cloud copies remain under the user’s storage choices; session secrets expire or are cleared by the client.
Deletion
Erase the wallet data locally. Telegram security settings can retain, delete, and verify removal of the optional cloud backup.
Controls
The server is not designed to receive plaintext recovery phrases or private keys. Cloud backup is opt-in and encrypted, but possession permits offline password guessing.

We do not sell personal data. We update this inventory when a product adds a user-linked persistence model or outbound recipient.

6. Data Retention and Deletion

Operational audit records expire after 90 days. Authentication and security audit records expire after 365 days. A daily deletion job removes expired records. A record may remain past its expiry only under a documented legal hold.

Audit records store a coarse network prefix and browser family instead of a full IP address or User-Agent version. Public blockchain transactions are permanent and cannot be deleted by us.

No self-service deletion or export workflow is currently implemented. To request access, correction, export, account deletion, or withdrawal of optional consent, email privacy@selvwallet.com. Account deletion removes audit records that are not under a legal hold. We will identify data that can be returned or deleted, held records that must be retained, and public-chain records outside our control.

7. Your Rights

Depending on your jurisdiction, you may ask to access, correct, export, or delete personal data, object to processing, or withdraw consent. These rights are not a promise that every requested record can be changed: public blockchain history cannot be erased, and legal retention duties may apply.

8. Children's Privacy

SelvWallet is not intended for users under the age of 18. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new policy on this page and updating the “Last updated” date. Continued use of the service after changes constitutes acceptance of the updated policy.

10. Contact Us

If you have any questions about this Privacy Policy, please contact us: