Better ASIC Portal
Privacy
How the Better ASIC Portal handles account, device, request, and security data.
Draft for staging - 13 July 2026Data we process
We process the identity supplied by Google or Telegram, linked-provider records, encrypted miner serial numbers or MAC addresses, request status history, and limited security and audit metadata. Normal portal screens and logs show device identifiers only in masked form.
Why we use it
We use this data to authenticate accounts, detect duplicate device claims, review compatibility, prepare per-device firmware requests, protect the service, and maintain an audit history of sensitive actions.
Storage and access
Application data is stored in Cloudflare D1 and future firmware artifacts remain in private Cloudflare R2 storage. Access is limited by role and record ownership. OAuth credentials, encryption keys, and build-service credentials are stored as Cloudflare secrets, not in the repository.
Retention and questions
The self-service deletion policy is not final during staging. Do not submit production customer data to the staging portal. For privacy questions or staged-data removal, contact the Better ASIC team through Telegram.