Privacy
This draft describes the intended data flow but is not a substitute for a counsel-reviewed production notice.
Controller/provider: biccsdev
Effective date: [EFFECTIVE DATE REQUIRED]
Privacy/support contact: Discord support server
Data used by Revive
- A one-way, domain-separated hash of the cross-checked PSG1 bootloader serial. The raw serial remains on the local computer.
- Compatibility profile fields needed to decide support. Unknown-build and crash reports are redacted and submitted only through the stated product flow.
- Security audit events, coarse request metadata, and rate-limit state needed to operate and protect the service.
Data not used as the license key
Revive does not bind the license to an Android installation ID, wallet, hostname, computer ID, or Google account. It does not ask users to paste raw device serials or license tokens into this website.
Processors and public-chain data
Hosting providers process service data on our behalf. Optional Solana donations are public blockchain records outside Revive's control and are not linked to installer access by the product. A final notice must name production processors, regions, transfer safeguards, and user-rights procedures.
Retention
[RETENTION PERIODS FOR ORDERS, LICENSES, REPORTS, LOGS, AUDIT EVENTS, AND REFUNDS REQUIRED]
Your choices
Optional crash reporting can be disabled. The production notice must explain applicable access, correction, deletion, objection, and complaint rights, including information that cannot be deleted because it is required for security, accounting, or permanent device-license recovery.