Security and trust
Layered controls protect accounts and authorized operations
GPixel combines role-based account access, server-side availability and pricing checks, installation controls, protected processing, and append-only financial records. No security control removes the customer’s duty to use the service lawfully.
Last reviewed
Why service teams trust GPixel
- Live compatibilityModel and software checked before work begins
- Clear credit pricingCurrent cost confirmed before authorization
- Authorized serviceFor devices you own or are permitted to manage
- Recorded outcomesCustomer-safe status and credit history
Account and session protection
- Server-side customer, reseller, and administrator role enforcement
- HTTP-only session cookies, CSRF protection, and session rotation
- Login throttling, temporary lockouts, and optional two-factor authentication
- Administrative session, token, installation, and security reset controls
Operation controls
- Device- and job-bound authorization
- Service availability checked before processing
- Internal implementation data excluded from public pages
- Safe customer milestones separated from protected technical logs
Credits and auditability
Credits are reserved, captured, released, or refunded through recorded ledger actions. Historical financial and operation records are preserved instead of silently rewritten.
Responsible disclosure
If you believe you found a vulnerability, use the contact channel below and include a concise impact description, affected URL or version, and safe reproduction steps. Do not access other users’ data, disrupt the service, or publish secrets or personal information.
Safe report scope
Test only accounts, installations, and devices you own or are expressly authorized to assess. Stop if you encounter another customer’s data. Reports should use minimal proof and must not include passwords, tokens, private service files, or full device logs.
Download integrity
Install GPixel Pro only from the published download page. Verify the displayed version, build number, and SHA-256 value when a browser, security product, or transfer process raises a warning.