To prevent session-hijacking and unauthorized account access from external machines, our system logs and stores a unique hardware signature (Device Token) in your browser’s localStorage. Accounts are strictly bound to authorized device fingerprints.
We collect staker credentials, blockchain wallet addresses, transaction ledger hashes, and referral connection networks. This information is strictly used for yield payouts, security checks, and ledger accounting.
User passwords are encrypted natively using BCRYPT hashes. Dynamic application states, session validation IDs, and database structures are locked behind strict firewall settings and prepared statement layers.
We utilize session cookies and local storage items solely to authenticate active staker access, maintain security headers, and validate CSRF verification tags.