
This page walks through how JB.COM collects, uses, and protects personal data tied to its players, India-based players included. It covers every part of the platform where personal information gets touched – registration, payments, and any interaction with support.
A few broad categories of information get collected as part of regular platform use. That includes contact details handed over at registration, documents submitted for identity verification, and general data that builds up just from using the platform, like login activity and saved preferences. Nothing here is collected without a reason – each category ties back to something specific about keeping the account running.
Whatever gets collected through JB.COM goes toward a handful of core jobs: confirming who a user actually is, processing deposits and withdrawals, keeping the account secure, and meeting whatever requirements come attached to the platform’s operating license. None of this is about marketing or promotion – it’s strictly functional, aimed at keeping the account working properly and safely.

There are situations where personal data ends up shared with outside parties who play a role in running the platform. That can mean payment providers processing deposits and withdrawals, game providers supplying the titles on offer, or regulators where sharing is required as part of licensing obligations. Whatever gets shared stays limited to exactly what that specific purpose calls for, nothing more.
Personal data belonging to players in India gets the same technical protection as everyone else’s. That includes encrypting data as it moves between a device and the platform, keeping internal access to personal information limited to relevant staff only, and controlling how long different types of data actually get kept. Put together, these measures are there to keep exposure of personal information down to just what running the account actually requires.
Players hold certain rights over their own data – requesting to see what’s on file, asking for corrections if something’s wrong, or requesting deletion where that applies. These requests generally go through JB Casino support, and each one gets looked at individually rather than processed automatically.
Account data generally stays tied to the platform rather than a specific location, so a change in country doesn’t typically require a separate data transfer request, though updating account details for the new location is still worth doing.
Usage data may be used to shape what’s shown or suggested on the platform, and where such personalization exists, it’s generally covered under the platform’s broader data use terms.
Depending on what’s requested and current platform capabilities, data access requests submitted through support may be provided in a reviewable format, though this can vary by request type.
Data sharing generally follows the categories and purposes already outlined in the policy, so a change significant enough to alter those terms would typically come with a policy update rather than an individual notice per provider.
Contacting JB Casino support immediately is the right first step, since prompt reporting allows the platform to investigate and take any necessary protective action on the account.