China’s ride-hailing giant is delisting from the New York Stock Exchange

China’s ride-hailing behemoth Didi has begun the procedure of delisting from the New York Stock Exchange and applying to list in Hong Kong instead, the company announced via a Weibo post on Friday morning.

The decision came days after Bloomberg reported the Chinese government had asked Didi to delist from the U.S. out of security fears. Didi could not be reached for comment by TechCrunch at the time.

The move is anything but surprising. The SoftBank-backed mobility powerhouse has faced immense regulatory pressure since it failed to assure Beijing its data practices were secure before its blockbuster IPO in July.

Over the past few months, China has rolled out a litany of new data regulations, including rules that would bolster user privacy protection and restrict cross-border data transfers. A Didi executive previously said it stored data in China and it was “absolutely not possible” that it passed data to the U.S., just like “many other U.S.-listed Chinese firms.”

Didi’s market cap currently stands at $37.6 billion. Its shares have plunged from over $15 apiece at debut to $7.8 as of Thursday.

More to come…

Credit belongs to : www.techcrunch.com

You May Also Like

Rocketplace raises $9M in seed funding to build the ‘Fidelity for crypto’

Rocketplace, a startup that aims to build a “next-generation asset management platform for crypto,” has raised $9 million in a seed funding round. A few things about this raise stood out. For one, the funding comes at an interesting time in the crypto world — during the so-called “crypto winter” and a period that has […]

YouTube Shorts will start adding watermarks to discourage cross-platform sharing

YouTube Shorts, the platform’s TikTok competitor, is rolling out a watermarking feature. That means that when creators make a short on YouTube, they won’t be able to download their video and cross-post it to other apps without a YouTube watermark. A YouTube community manager posted about the update yesterday on a support thread that chronicles […]
error: Content is protected !!