Meta Split Aftermath
Manus's Data Deletion Standoff
Restoration Has Begun, But It's Not Over
As part of unwinding its capital ties with Meta, AI agent maker Manus deleted data belonging to a subset of users. Restoration began rolling out from August 25 (SGT), but only for accounts in "certain jurisdictions" — meaning some users need to act now, and others don't. Here's what happened and what to do about it.
What Happened
The Price of
Independence
Manus became independent from Meta again this April, after Chinese regulators ordered Meta to unwind its roughly $2 billion-plus acquisition of the company. As part of that capital unwind, Manus announced in its official blog post "A Note to Our Users" that it would delete user data for a subset of accounts in certain jurisdictions.
The deletion covers data generated on or after December 29, 2025, and applies only to accounts subject to specific jurisdictional requirements — not the entire user base. The deletion itself ran August 23-24 (Singapore time), after users in affected regions were notified in-app and by email beforehand. The backup window closed at 7:59pm EDT on August 22 (7:59am SGT on August 23); according to regional press coverage, data not backed up before that cutoff was not recoverable.
The deletion window, by the numbers
Independence had a price —
and for some users, that price was their own history.
Why It Matters
This isn't just one company's problem
One of the first concrete cases of a state forcing an AI company's ownership structure to unwind under US-China tension.
What makes this episode significant isn't the corporate unwind itself, but that a government order forced the reversal of a Big Tech company's stake in an AI startup, with user data governance changing as a direct downstream effect. Meta had committed north of $2 billion to bring Manus under its umbrella; a single regulatory order from Chinese authorities unwound that relationship and, in the process, forced changes to how user data was handled. From a user's perspective, data governance shifted not because of a terms-of-service update, but because of geopolitical regulatory action entirely outside their control. As generative AI services increasingly operate across borders, this kind of "corporate-ownership risk" is unlikely to be a one-off.
Who It Affects
Who feels this, and how
Businesses running Manus workflows
If your automation outputs and logs lived entirely inside Manus, anything generated after Dec 29 in an affected jurisdiction may be gone. Confirm restoration completed, and start a secondary backup into your own systems now.
PMs and project leads
Lost task history breaks your audit trail of what a team actually did. Inventory which accounts were affected, and weigh whether to run a second tool in parallel going forward.
Individual users outside the affected jurisdictions
Per reporting, the deletion was limited to specific regions, so most individual users saw no impact. Still, given similar capital shake-ups could recur, it's worth checking the official notice rather than assuming it doesn't apply to you.
What to Do Next
If you're affected, do this now
Check whether your account was in scope
Look for an in-app notice or email. If you never received one, you likely weren't part of this deletion.
Verify restoration on your account
Restoration has been rolling out since Aug 25, but there's no guarantee everything returns instantly. Don't wait for a completion notice — try re-fetching critical data now.
Reduce single-vendor dependence
Given how a capital-structure change rippled into data preservation here, start mirroring important outputs to independent storage alongside any single AI vendor.
Risks & Open Questions
Reasons not to relax yet
Restoration starting is good news, but concerns remain. First, the boundary of "certain jurisdictions" isn't spelled out precisely in the official post, so affected users may not realize it unless they actively check. Second, users caught in the window effectively lost the ability to rely on Manus for business use for several days, and that disruption isn't being compensated. Third, this precedent — a government order forcing a capital unwind that cascades into user data deletion — could become a template other AI services face under future geopolitical pressure, which is exactly why keeping your own independent backups matters more than it used to.