TLDR: Bitget will discontinue services for selected customers, sending each affected account its own deadlines, next steps and withdrawal arrangements. English terms marked as updated October
TLDR:
Bitget will stop serving a selected group of customers, with each affected account receiving its own deadline and withdrawal instructions. The exchange publicly announced the measure on October 17 and said operations would continue for other users.
Its English Terms of Use, marked as updated October 16, list Russia, Belarus and Kazakhstan among prohibited jurisdictions. One customer reported an October 21 cutoff, but the main announcement gave no shared deadline.
The company described the action as a one-time exercise and said customer funds remained safe. It did not disclose the number of affected accounts or identify a specific regulatory order.
Bitget said affected customers would receive emails, in-app messages and/or push notifications. These messages will set out the steps needed before service ends, including arrangements for taking assets off the platform.
Bitget support will assist with outstanding orders and account questions during the process. The exchange did not publish a single withdrawal procedure applicable to every affected account.
A user posting as FrontMan said on October 16 that he had received one of the notices. His notification reportedly set October 21 as the end of service for his account. Customers who receive no official notification can continue using their accounts under the existing terms and conditions. The company did not describe the exercise as an exchange-wide shutdown or announce the suspension of all trading.
The announcement also directed users toward official channels for updates and assistance. It named the website, app, Support Center and verified social accounts, while warning about phishing links and impersonation.
Bitget lists Russia, Belarus and Kazakhstan within a broader group of locations excluded from its services. The English agreement labels that group as prohibited countries and allows the exchange to designate additional locations.
Under the document, restricted persons include individuals residing in those places and entities established or operating there. Its eligibility section says restricted persons cannot register for accounts or use the services. The wording connects access to residence and operations, rather than nationality alone.
Bitget support also addressed a question about restrictions on users in Russia. It cited the country list and compliance with national regulations. The reply did not name a specific law, regulator or enforcement action, according to The Defiant.
Bitget terms also cover know-your-customer and anti-money laundering procedures, commonly grouped as KYC/AML requirements. Users must provide accurate information and update it when circumstances change. The agreement allows requests for further documents and enhanced due diligence.
The agreement also allows the platform to restrict access or close accounts when users no longer meet eligibility conditions. It permits the closure of outstanding positions, depending on the circumstances, and leaves some risk assessment criteria confidential. This authority also covers legal or regulatory restrictions, concerns, requests and other requirements.
Those standing KYC/AML provisions do not identify the reason for the latest service withdrawals. The main notice did not say that every customer in a named jurisdiction had received an identical timetable.
Bitget issued the service notice more than three weeks after a September 24 wallet breach. Its September 25 security update put transfers to attacker-controlled addresses at approximately 387.5 million dollars. The exchange did not connect the account terminations to that attack.
The revised loss exceeded an initial estimate of 351.6 million dollars. The company said the difference reflected a fuller classification of transfers, including assets on Zcash and TRON. It said the revision did not represent further unauthorized transfers.
That security update said investigators had identified and repaired the vulnerability. External specialists Mandiant and SlowMist were assisting the investigation, alongside internal security and technical teams.
The post Bitget to End Services for Some Users Amid Russia Restrictions appeared first on Blockonomi.
