Bitget updates terms, cuts off users in Russia, Belarus, Kazakhstan
Regulation & Gov ·
The exchange's English Terms of Use, marked updated Oct. 16, list the three countries among prohibited jurisdictions, triggering account-specific service terminations.
Bitget has begun discontinuing services for certain users tied to Russia, Belarus and Kazakhstan after revising its English-language Terms of Use, with the document marked as updated Oct. 16 now naming the three countries among prohibited jurisdictions, according to a report citing The Defiant. Affected users are receiving account-specific deadlines and withdrawal instructions sent directly to them rather than a single public cutoff date.
Bitget has characterized the move as a one-off exercise and said user funds remain safe throughout the process. The exchange also said users who do not receive a notification can continue operating their accounts under the existing terms, suggesting the restriction is being applied selectively rather than as a blanket regional ban.
The exchange's official support account has corroborated the jurisdictional basis for the restrictions, citing the prohibited-jurisdiction list when responding to inquiries about limits placed on Russian users. That response aligns with the broader account-termination pattern described in the updated terms.
One affected user has reported an Oct. 21 deadline for action on their account, though this timeline has not been confirmed as universal. Bitget's main announcement did not specify a common deadline, did not disclose how many accounts are affected, and did not cite a specific regulatory basis for adding the three jurisdictions to its prohibited list.
The development is also being tracked as part of a wider pattern of exchange activity affecting the region, per ongoing coverage. What remains unresolved is the scale of the rollout — including the total number of accounts affected, whether the Oct. 21 date applies broadly or only to isolated cases, and what specific regulatory or compliance driver prompted the jurisdictional change. Further detail from Bitget on these points has not yet surfaced.