Fiadyn Privacy Policy
If you use Telegram, we store your raw Telegram user ID and, when Telegram provides them, username and language metadata to operate your account. A BTCPay browser purchase may create a provider-neutral Fiadyn account without a Telegram ID or email. Fiadyn sends BTCPay only a random internal order reference and product code, not your Telegram identity or Fiadyn identity ID. Bitcoin on-chain transactions are public and must not be described as anonymous; Lightning and wallet/provider usage may also expose metadata outside Fiadyn. We store BTCPay invoice/event identifiers, entitlement records and a keyed hash of the private claim capability needed to bind a settled purchase. If you pay by card, we store the Stripe identifiers needed for settlement and lifecycle handling. We store device labels and one-way hashes of device identifiers, keyed hashes of browser/session/subscription tokens, entitlement records, traffic accounting and security/audit records. We do not store raw Happ device IDs, raw session tokens, raw refresh tokens, or raw subscription tokens.