Development privacy notice

Accounts store email, password hashes, verification records, session metadata, policy acceptance, and an application profile. Financial records are kept separately in an immutable ledger. Email delivery requires a configured sender; there is no development email inbox. Optional product analytics remain off without configuration and consent.

Rewards and abuse prevention

The app records provider reward identifiers, offer starts, referral attribution, hashed device/IP signals and withdrawal details needed for review. Wallet destinations are masked in history. Staff can inspect account evidence; financial actions create immutable audit records. Survey answers are handled by the provider and are not stored here.

Support requests

In-app support stores your request subject, category, message, staff replies and resolution history. Authorized staff can inspect requests and account evidence. Messages and staff actions retain an audit trail; no email notifications are sent by this workflow. Do not include passwords, authenticator or recovery codes, private keys or wallet seed phrases. Production retention and user-rights handling remain to be finalized.

Operational monitoring

Financial health checks report aggregate issue counts. When configured, error monitoring receives operational codes and counts, with user, request and breadcrumb data removed. Financial health checks do not export wallet destinations or emails.

Production retention, user rights, provider disclosures, and operator contact details must be finalized before public launch. Use test accounts during development.