Login
Content

Privacy policy

Privacy policy

Last updated: 2026-09-01

What we collect

  • Account data: email address, username, and a salted password hash. We never store your password in plain text.
  • Technical data: IP address, user agent, and coarse IP-derived location for the most recent logins. This is required to detect multi-accounting and VPN abuse.
  • Transaction data: an append-only ledger of every balance change, withdrawal request and its status, and the FaucetPay destination you supply.
  • Offerwall data: transaction identifiers and amounts returned by third-party offerwall providers so we can credit you exactly once per completion.
  • Cookies: a session cookie and a CSRF token cookie. Both are strictly necessary; we use no advertising or third-party tracking cookies.

Why we collect it

To operate the faucet, to credit rewards, to pay you, to detect and prevent fraud and multi-accounting, and to comply with our own audit and reconciliation obligations.

What we do not do

  • We do not sell your personal data.
  • We do not run third-party advertising or analytics trackers on this site.
  • We do not accept deposits, so we never collect payment card or bank details.

Third parties

The only third party that receives your personal data is FaucetPay, which receives only the payout destination you provide, solely to complete a withdrawal you requested. Offerwall providers receive a transaction identifier and your IP address as part of fraud verification; they do not receive your email.

Retention

Account and ledger records are retained while your account is active. If you request deletion, we delete or anonymise personal identifiers but retain the ledger in aggregate form where required for financial reconciliation and fraud investigation.

Your rights

You may request a copy of your data, correction of inaccurate data, or deletion of your account, by opening a ticket from the Support tab in your dashboard.

Security

Passwords are stored as salted hashes. Offerwall gateway secrets are encrypted at rest with AES-256-GCM. All traffic is served over HTTPS in production. Financial records are written append-only and reconciled hourly so that unauthorised balance changes are detectable.