What you need to know
- TikTok has slammed an Executive Order which could ban the app in the U.S.
- It said it was "shocked" and that the order was issued without any due process.
- It said the order risked undermining the trust of businesses globally in the United States' commitment to the rule of law.
TikTok has issued a statement fervently criticizing a recent Executive Order that could see its App banned in the United States.
TikTok said that there has been no due process or adherence to law on the matter and that the text of the order "makes it plain" that there has been a reliance on "unnamed 'reports' with no citations." TikTok reiterated it had never shared user data with the Chinese government or censored content at its request. It also pointed to its Transparency Center, "a level of accountability no peer company has committed too."
Clearly, TikTok is eyeing up all recourse including legal action against President Trump's administration to fight the order. TikTok is, of course, currently in the process of trying to strike an acquisition deal between Microsoft and parent-company ByteDance. The ban will take effect in 45 days.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple. Follow him on Twitter @stephenwarwick9
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.