Email and password via Supabase Auth. Consent timestamp. Destinations you declare. Jobs and check metadata (status code, bytes, duration). Device token hashes on the server, not the raw token after issue. No browsing history. No cookies from third-party sites. The extension fetches with credentials omitted.

The AFKMAXX Chrome extension stores on the device: whether checks are running, today’s byte usage, the web app origin you connected, a device token used to poll jobs, and a short local history of host plus status code. It does not read browsing history, does not inject into arbitrary sites except the connected AFKMAXX app origin and user-granted HTTPS check hosts, and does not sell data. Check response bodies are read only to count bytes, then discarded.

In return for premium features of AFKMAXX, you may choose to be a peer on the Bright Data network. By doing so, you agree to have read and accepted the Bright SDK EULA and Bright Data’s Privacy Policy.

You may opt out of the Bright Data network by turning off Web Indexing in the AFKMAXX desktop app (the Web Indexing switch in the Mac or Windows window, or in the Mac menu bar).

You get AFKMAXX desktop features in exchange for safely using some of your device’s resources, and only in a manner that will not substantially affect the device’s operation (see how Bright SDK works). You may turn this off from the desktop settings. See also the SDK Privacy Policy at https://brightdata.com/legal/sdk-privacy.

Check bodies are not stored on the server. Results stay unaudited until an admin reviews them. $AFK ledger rows are placeholders and are not withdrawable.

You can pause in the app, the extension popup, or the desktop app. A banned account cannot receive jobs. Ownership of a destination is declared, not proven, until a later challenge exists.