Privacy for account access, account readiness, and future mining workflows.

This policy explains what FallenOne may collect during launch-ready controlled access, what participants is never expected to submit, and why payment, wallet, payout, and settlement data are not being collected yet.

Cookie Policy Contact Terms

Information We May Collect

Only what is needed for launch-ready controlled access review and site protection.

FallenOne may collect name, email address, organization, interest area, request type, message content, waitlist consent, security challenge results, and submission metadata.

Technical metadata may include timestamps, user-agent strings, IP-derived request information, request status, rate-limit events, challenge results, and access logs needed to operate and protect the site.

Information We Do Not Want

Public forms are for communication, not wallet or payment handling.

Do not submit private keys, seed phrases, payout wallet addresses, wallet credentials, card numbers, banking details, passwords, miner credentials, mining pool credentials, internal IPs, private hostnames, admin URLs, or confidential diagrams.

How We May Use Information

Information supports readiness, communication, and protection.

Submitted information may be used to record early interest, respond to inquiries, prepare future participant communication, evaluate demand, protect the site, detect abuse, preserve audit evidence, and support launch planning.

If account workflows are enabled later, additional privacy terms or notices may apply to orders, settlement records, payout settings, support records, and account activity.

No Payment Or Wallet Intake

Settlement and payout data are not being collected during launch-ready controlled access.

Hashrate checkout, card payments, BTC or crypto settlement, cash payments, invoices, deposits, payout wallet intake, payout automation, allocation automation, live miner control, telemetry ingest, and Stratum access remain locked until FallenOne clears its launch gate.

Retention And Security

Records may be retained for business, security, and audit needs.

FallenOne may retain waitlist, contact, security, audit, and operational records as needed for platform protection, dispute prevention, compliance review, launch-ready controlled access planning, and legitimate business purposes.