Security overview
Security controls built around account and transaction records
GPT32 uses layered controls for authentication, payment verification, cycle accounting, withdrawal review, and administrator actions. This page explains what those controls do—and what members must still protect themselves.
Password and recovery protection
Passwords are stored as salted one-way hashes. Verification, session, and password-reset tokens are stored as hashes and expire. Members should use a unique password and never place credentials in a URL, support message, or shared screenshot.
Signed deposit confirmation
Deposit credit requires a valid payment callback signature. The callback is matched to a local deposit record and processed idempotently to reduce duplicate-credit risk.
Separated wallet accounting
Available Balance, Locked Balance, and Earnings are tracked separately. Starting a cycle creates a ledger entry and locks its principal; withdrawal requests reserve funds before admin review.
Audited administrator actions
Account status changes, wallet adjustments, cycle controls, support replies, and withdrawal decisions are restricted to approved admin accounts. Sensitive balance changes retain a reason and audit record.
Member security responsibilities
Always verify the domain before signing in, protect your email account, confirm the USDT network and destination address, and report unexpected activity through authenticated Support. Review our privacy notice for data-handling details.