Manus Splits From Meta: What Gets Deleted, and How to Back Up Before August 23

Manus announced on August 11, 2026 that it will "soon resume operating as an independent company" — unwinding the Meta acquisition that closed on December 29, 2025. The announcement is framed as good news, and for most users it is. But buried in the operational detail is a line that should stop any agent-platform user cold:

Data generated by affected users on or after December 29, 2025 will be deleted between 08:00 SGT on August 23 and August 24, 2026.

That date is not arbitrary. It is the acquisition date. Everything created while Manus was a Meta company has to go — for some users, in some jurisdictions — and the backup window to save it is already running.

This post covers who is affected, the exact deadlines converted to every timezone that matters, what the deletion boundary reveals about why this is happening, and the portability lesson that applies whether or not you have ever opened Manus.

TL;DR — what people are asking

The exact deadlines, converted

Manus publishes its deadlines in SGT (Singapore Time, UTC+8), which is itself a small signal about where the company's operational center sits. Here are both cutoffs in the timezones our readers actually work in — verified against the EDT and CEST figures Manus published:

Backup window closes

Restoration portal opens

Note the trap for Indian and European users. The backup deadline falls in the small hours of a Sunday morning local time. If you plan to "do it over the weekend," you have until Saturday night — not Sunday afternoon. In practical terms, treat Friday August 21 as your real deadline.

Who is affected, and how to find out

Manus is running notification through two channels, and the gap between them is where people will get burned:

• Email — sent to affected users only.
• In-app notification — sent to both affected and unaffected users. Unaffected users get an explicit "you aren't affected" message.

That second channel matters because of a detail Manus calls out directly: users who registered with an Apple ID or a Facebook account have no email address on file. Sign in with Apple's private relay and Facebook OAuth both mean Manus may never have had a deliverable address. If you used either, email silence tells you nothing — open the app.

The safe interpretation of an empty inbox is "unknown," not "safe." Manus's confirmation-for-everyone design means the absence of any notification, in either channel, is the one state you should chase down with support rather than assume your way out of.

What the December 29 boundary actually tells you

Most platform data migrations delete by storage tier, by inactivity, or by account age. This one deletes by transaction date.

Manus's FAQ is explicit about the reasoning: "On December 29, 2025, Meta acquired Manus. Data generated by some users on/after Meta's acquisition of Manus needs to be deleted to comply with regulatory requirements in specific jurisdictions."

Read that carefully. The category being erased is not "old data" or "unused data" — it is data that existed while a specific corporate parent controlled the company. That is the shape of a regulatory remedy for a transaction, not a housekeeping exercise. Something about the acquisition itself created a data-handling problem in at least one jurisdiction, and unwinding the deal apparently requires unwinding the data that accumulated under it.

Manus does not name the jurisdictions. Two things it does tell us are worth noting: user data is stored in the US and Singapore, and every deadline in the announcement is anchored to Singapore time.

explainx.ai flagged this exact scenario as a live possibility a month before it happened. In our July coverage of China's reported overseas AI model restrictions, we listed "Meta/Manus investigations and April NDRC unwind" among the concrete evidence that outbound-tech policing was actively underway rather than speculative. This announcement is what that policing looks like when it reaches end users — not a headline about export controls, but a backup deadline in your app.

To be precise about what is and is not confirmed: Manus has not attributed the requirement to any named regulator or country. The connection to previously reported acquisition scrutiny is an inference from public reporting and from the shape of the remedy, not a claim Manus has made. Treat it as strong context, not established fact.

What to do right now, in order

If you are an affected user, the sequence matters more than the individual steps:

1. Open the Manus app and check your notifications today. Do not wait for email. This is the only reliable way to learn your status if you signed up through Apple or Facebook.
2. Run the backup now, not near the deadline. Export tooling at scale fails under deadline load — this is the single most predictable failure mode of every migration window ever run. The first backup you complete is worth more than the perfect one you plan.
3. Verify what actually came out. Open the export. Check that it contains the task histories, artifacts, and generated files you care about — not just an account manifest. Do this while there is still time to file a support ticket.
4. Re-run the backup before the cutoff if you keep working. Manus explicitly supports multiple backups: "If you generate new task data after backing up, please back up again." Anything created after your last backup is deleted with everything else.
5. Copy anything business-critical out of the export format entirely. A vendor-specific archive that only restores into that vendor's portal is a hostage, not a backup. If a client deliverable lives in a Manus task, put a copy somewhere you control.
6. Plan for two days of no access. From the moment the backup window closes until the restore portal opens on August 25, affected users cannot reach their accounts at all. If you have deadlines in that window, move the work now.
7. Check your billing. Manus says affected users are not charged from August 11 to August 23 and that "welcome back bonuses" are coming. Verify against your actual statement rather than the announcement.

The honest unanswered questions

Derivative coverage that only restates the announcement is not much use. Here is what the announcement does not resolve:

• Which jurisdictions? Named nowhere. Users cannot self-assess their status from first principles, which is why the notification channel is the only signal.
• Why deletion rather than transfer? If the concern were data residency, migration to a compliant region would be the usual remedy. Deletion-then-user-initiated-restore is a heavier instrument, and Manus does not explain why it was required.
• What is in the export, exactly? Manus points to Help Center guides but the announcement itself does not enumerate whether full task histories, intermediate artifacts, browser-session outputs, and generated files all survive the round trip.
• What happens to team plans and API state? The announcement is written for individual users. Organizations with shared workspaces, seats, or API integrations have a materially harder version of this problem and no stated guidance.
• Does restore preserve timestamps and task ordering? For anyone using Manus output as a work record, a restore that flattens chronology is a different product than the one they backed up.
• What is the fallback if restore fails? No stated remedy, no stated SLA, and after August 24 the source data is gone.

None of these are gotchas — they are the questions a careful user has to route to support before the window closes, not after.

The real lesson: agent platforms have no export standard

One reply to Manus's announcement summarized the whole situation better than the announcement did: "Every agent needs a boring, reliable export path."

That is the durable takeaway here, and it applies whether or not you use Manus.

Agent platforms accumulate a genuinely new category of asset — not documents, but task histories: the prompts, the tool calls, the intermediate reasoning, the artifacts, the browser sessions, the accumulated context of how work actually got done. For a heavy user, that history is more valuable than any single output, and it is the thing least likely to be portable.

Compare the maturity gap. Files have had portable formats for decades. Email has IMAP. Even calendar data has iCal. Agent task history has nothing — no standard schema, no interchange format, no expectation that Platform A's history means anything to Platform B. MCP standardized how agents reach out to tools and data, which was the harder and more urgent problem, but it does not standardize the record an agent leaves behind.

The practical consequence is that your leverage over an agent platform is exactly as strong as its export button. That is worth weighing alongside capability when you choose one — the same evaluation discipline explainx.ai applies in the agent harness guide and in choosing open-weight versus closed models, where self-hosting eliminates this failure mode entirely because there is no portal to lock you out of.

It is also why the Gemini CLI deprecation and Antigravity migration is worth reading next to this one. Different company, different cause — a product sunset rather than a corporate unwind — but the identical user experience: a fixed date, a migration path someone else designed, and whatever you failed to export becoming unrecoverable on schedule.

Why this matters beyond Manus

There is a wider pattern forming, and it is not about any single product.

AI companies are now geopolitical objects. Acquisitions get reviewed, unwound, and conditioned on data handling in ways that reach individual user accounts. explainx.ai has been tracking the model-layer version of this — export controls and policy timelines, whether governments can ban AI models outright, and China's open-model playbook — but this announcement is the first mass-market case where that machinery lands as a consumer backup deadline.

One community reply captured the awkwardness precisely: the original acquisition's investors "already got paid out," and unwinding a deal after the money has moved "is a mess that 'please back up your data' doesn't come close to capturing." That is fair. Manus's users are absorbing the operational cost of a transaction they were not party to, and the company — to its credit — is at least saying so plainly and building tooling rather than posting a terms-of-service update and hoping nobody notices.

Manus's own framing looks past it: the company says it is "preparing a series of new features that will push the boundaries of what's possible for general AI agents once again." Independence may well be better for the product. But for the next twelve days, the only thing that matters to an affected user is whether they clicked export.

Related on explainx.ai

• China's reported overseas AI model restrictions — where we flagged the Meta/Manus investigations
• Gemini CLI deprecation and Antigravity migration guide
• Can governments ban AI models and tools?
• AI policy timeline 2026: export controls, distillation, open weights
• China's AI playbook: free models, cheap compute
• What is an agent harness? Complete guide
• What is MCP (Model Context Protocol)?
• How to choose open-weight vs closed AI models
• AI tool system prompts leaked — including Manus

Official source: Manus, A Note to Our Users (August 11, 2026), and the @ManusAI announcement on X.

Dates, deadlines, and quotations reflect Manus's official blog post and X announcement as published on August 11, 2026. Timezone conversions were computed from the SGT figures and cross-checked against the EDT and CEST times Manus published. Manus has not named the jurisdictions driving the requirement; any connection to previously reported acquisition scrutiny is inference from public reporting, not a company statement. Backup tooling, restore timing, and subscription handling may change — check Manus's Help Center and your in-app notifications for authoritative status before acting.