Manus Returns to Independence, but Some Users Face a Data Reset

Manus said on August 11 that it will resume operating as an independent company, but that reversal carries an immediate cost for some users. Data generated on or after December 29, 2025, by affected accounts will be deleted during a scheduled transition beginning August 23.

The company is giving those users a narrow window to download a backup. They must complete it before 7:59 a.m. Singapore time on August 23. Manus says they can begin restoring the exported data at 8:00 a.m. Singapore time on August 25.

This is more than a routine service migration. December 29 was also the date Meta announced its agreement to acquire Manus. China later prohibited the transaction and ordered the parties to unwind it, turning an AI acquisition into a test of regulatory control over technology, talent, and data.

What Manus Users Need to Do Before August 23

Affected users should treat the backup deadline as a hard operational cutoff, not a general recommendation.

According to the August 11 notice summarized in the original user notice, the deletion applies only to certain users. Manus says those users will receive instructions through its interface and can start backing up their information immediately.

The relevant cutoff is based on when the data was generated. Content created on or after December 29, 2025, falls within the announced scope for affected accounts. Older content is not described as part of the reset.

The company plans to delete the covered data between August 23 and August 24, using Singapore time for the published schedule. Affected users can restore their exported information beginning August 25.

The practical sequence is straightforward:

• Confirm whether Manus has marked the account as affected.

• Export the available account and task data before 7:59 a.m. Singapore time on August 23.

• Keep the downloaded archive in a separate, accessible location.

• Avoid assuming that data created shortly before the deadline will remain available.

• Return after 8:00 a.m. Singapore time on August 25 and follow the restoration process.

Users outside Singapore should convert the deadlines carefully. The backup window closes at 7:59 p.m. Eastern Daylight Time on August 22 and 4:59 p.m. Pacific Daylight Time that day.

The restoration window begins at 8:00 p.m. Eastern Daylight Time on August 24 and 5:00 p.m. Pacific Daylight Time. Those conversions matter because the official dates can appear one day earlier in North America.

Manus says unaffected users can continue using the service normally. They do not need to export or restore their data solely because of the corporate transition.

That distinction should prevent unnecessary panic, but it also creates a verification problem. Users must rely on Manus to identify affected accounts correctly and communicate the required action clearly.

Anyone who uses Manus for client research, generated applications, reports, files, or recurring workflows should review the account directly. Waiting for a second reminder introduces avoidable risk.

A backup also needs verification. Users should confirm that the archive downloaded successfully, opens as expected, and contains the projects they cannot recreate easily.

The transition highlights a weakness in cloud-based agent workflows. An AI agent can generate a report, browse sources, write code, and assemble files, yet the resulting work still depends on the platform’s account and storage policies.

Teams should therefore retain important outputs in systems they control. That can include a local repository, approved document storage, or a searchable personal knowledge base.

That practice does not eliminate platform risk. It does reduce the chance that a corporate or regulatory event becomes a business-continuity failure for the user.

The Independence Announcement Reverses Meta’s Plan

Manus is moving from planned integration with Meta back to independent operation because regulators rejected the transaction behind that integration.

Meta announced its agreement to acquire Manus on December 29, 2025. The public terms were not disclosed, although a person familiar with the transaction told Reuters that the company was valued between $2 billion and $3 billion.

At the time, Meta said it would operate and sell the Manus service. It also planned to integrate the agent technology into consumer and business products, including Meta AI, according to the acquisition coverage.

An AI agent is software that can plan and complete multiple steps toward a goal with limited user intervention. That differs from a standard chatbot, which primarily responds to individual prompts.

Manus attracted attention by presenting its service as a general-purpose agent. The company said it could research topics, analyze information, create documents, and execute digital tasks through one delegated workflow.

Those capabilities made Manus relevant to Meta’s broader push into personal and business agents. Meta already controls distribution through Facebook, Instagram, Messenger, and WhatsApp, but distribution alone does not produce reliable task execution.

The acquisition offered a direct route to an established agent product and its engineering team. It also promised to shorten the distance between Meta AI conversations and completed work.

That strategy encountered a regulatory barrier. On April 27, China’s National Development and Reform Commission prohibited the foreign acquisition of the Manus project and required the parties to withdraw the transaction.

The decision was unusually direct. Legal analysts described it as the first publicly announced, transaction-specific prohibition under China’s current foreign investment security review framework.

Manus had moved its headquarters to Singapore before the Meta agreement. Its products were not available in mainland China when the deal was announced, and Meta maintained that the transaction complied with applicable law.

Chinese regulators nevertheless focused on the company’s deeper connections to China. Manus was founded by a Chinese team, and its predecessor business and technical development had substantial roots there.

This is the central reversal. A corporate relocation that appeared to position Manus for a global sale did not put the company beyond Chinese regulatory reach.

The August independence announcement is therefore not a fresh strategic choice in the usual startup sense. It is an operational consequence of a transaction that authorities ordered the parties to unwind.

The deletion and restoration process provides the first visible evidence of how that unwinding affects ordinary users. Corporate separation is no longer confined to legal documents, employee assignments, or ownership records.

It now reaches into account-level data.

Why Regulators Looked Through the Singapore Structure

The case suggests that an offshore headquarters cannot erase the jurisdictional importance of where technology, talent, and data originated.

China’s foreign investment security review system examines whether foreign control of a business affects national security. It can address direct acquisitions and less obvious arrangements that transfer actual control.

That makes corporate form only one part of the analysis. Regulators can also examine intellectual property, personnel, contractual control, development history, data access, and the practical location of business operations.

The regulatory decision analysis from DaHui Lawyers argues that the Manus ruling rejects the idea that relocation alone can remove a China-connected technology business from Chinese review.

The firm identified several overlapping regulatory areas. These include foreign investment review, technology export controls, cross-border data rules, merger control, and overseas transaction requirements.

Manus sits at the intersection of those concerns. Its value does not depend solely on a legal entity or consumer brand. It also rests on agent architecture, engineering expertise, operational data, and the ability to coordinate models and external tools.

That combination complicates any attempt to unwind an acquisition. Shares and contracts can be reassigned, but knowledge and technical collaboration cannot be separated with equal precision.

Reporting in April indicated that Manus personnel had already moved into Meta’s Singapore offices. The founders had also taken roles within Meta’s organization, according to deal reporting.

Those reported changes illustrate why the regulator’s order raised difficult implementation questions. A completed or partly completed technology deal can mix teams and know-how long before authorities issue a final decision.

The data reset now appears to be one part of creating a legally distinct operating environment. Manus has not publicly provided enough technical detail to establish exactly which systems, databases, or jurisdictions require separation.

The company’s phrase “specific regulatory requirements” leaves important questions unanswered. It does not identify which categories of data create the compliance problem or why the December 29 cutoff captures the necessary scope.

It also does not explain whether affected information was stored within Meta-controlled systems, copied between environments, or governed by agreements made during the acquisition period.

Readers should not infer more than the announcement establishes. The timing strongly connects the reset to the acquisition and its unwinding, but the precise technical mechanism remains undisclosed.

That verification gap matters because “data deletion” can describe several different operations. It can mean removing active database records, revoking access, deleting replicated copies, or placing information beyond recovery through key destruction.

Each method carries different consequences for restoration, auditability, and retained backups. Manus has not publicly described its method at that level.

Its existing deletion policy says the company can retain some personal information for legal, accounting, reporting, fraud prevention, or legal-claim purposes.

That policy concerns account deletion initiated by a user, not the August transition. Still, it shows why the word “deleted” does not necessarily mean every related record disappears simultaneously.

The regulatory lesson extends beyond Manus. A company cannot assume that moving its headquarters, contracts, or holding company will settle questions about strategically sensitive technology.

For AI startups with development roots in one country and buyers in another, the real asset map includes source code, training methods, operational data, employee knowledge, and control rights.

Regulators can evaluate that entire map.

The Real Conflict Is Corporate Independence Versus Data Continuity

Manus can restore its independent legal position without guaranteeing a frictionless continuation of every user’s account history.

That tradeoff is the heart of the story. Independence sounds like a reversal at the company level, while deletion sounds like a failure of continuity at the user level.

Both can be true. Separating Manus from Meta may require changes to data custody, system access, contractual responsibility, or infrastructure. Those changes can protect regulatory boundaries while disrupting user access.

The dates make that relationship visible. The affected data period begins on December 29, the day the Meta agreement was announced. The deletion occurs while Manus prepares to resume independent operation.

The user experience resembles a controlled export and import rather than an invisible backend migration. Affected users must take possession of their information, wait through the reset, and then return it to Manus.

That process shifts some execution risk from the company to the customer. If a user misses the deadline, loses the archive, or cannot restore it, independence offers little practical comfort.

The process also introduces integrity questions. Users will want to know whether restored projects retain their original structure, attachments, conversation context, task histories, and links between generated assets.

An exported folder of final files is not always equivalent to a restored agent workspace. Agent products depend on context, permissions, tool connections, and intermediate state that may not survive a simple file transfer.

This difference matters for professional use. A marketing report can often be downloaded as a document. A recurring agent that monitors sources, calls integrations, and revises a shared artifact may depend on hidden configuration.

Manus has not publicly explained which of those elements its backup captures. Until restoration begins, users cannot independently confirm that exported accounts will return to the same operational state.

The company also needs to prevent cross-account errors during the restore. A system that accepts uploaded archives must reliably verify ownership and avoid exposing files, credentials, or task history to the wrong account.

Security controls can make restoration slower. Weak controls can make it dangerous.

Enterprise customers face additional questions about administrators and ownership. Manus’s general help materials say that team administrators can influence retention policies for team accounts.

The transition notice needs equally clear guidance about who must perform the backup for shared workspaces. Individual members should not assume another administrator has completed it.

The uncertainty creates pressure on Manus, not just on users. The company must complete a legally sensitive separation while preserving confidence in a product built around delegated responsibility.

AI agents ask users to hand over more than isolated prompts. They can receive research materials, customer data, draft code, internal plans, and access to connected services.

That makes continuity and provenance central product qualities. Provenance means retaining a clear record of where information came from, how it changed, and which system controlled it.

A reliable agent must do more than produce a good result. It must give users enough control to preserve, audit, transfer, and delete that result under changing conditions.

The Manus reset turns those abstract requirements into a deadline. It also gives customers a practical reason to assess exit procedures before committing critical work to any agent platform.

Questions worth asking include:

• Can the platform export complete projects in a documented format?

• Does an export include attachments, prompts, task history, and generated files?

• Can another system read the exported information?

• Who controls connected-service credentials?

• Can administrators verify that every shared project was included?

• What evidence confirms that restoration completed successfully?

These are not arguments against cloud agents. They are basic procurement questions for software that acts on behalf of its users.

The same logic applies to personal workflows. A researcher who asks an agent to gather sources should retain the source list and resulting notes somewhere independent of the execution service.

A developer should keep generated code in version control. A product manager should retain specifications and decisions in a durable workspace, not only inside a temporary agent session.

A system designed for work memory can help preserve the evidence surrounding a task. It should complement, not replace, verified exports from the original platform.

The Manus transition shows why portability is not a secondary feature. It is part of whether an AI service can be trusted with long-running work.

Meta and Manus Still Face an Unfinished Separation

A public return to independence settles the intended destination, but it does not reveal how completely the companies can reverse months of integration.

China’s April order reportedly required the parties to unwind the acquisition. In legal terms, unwinding aims to restore the position that existed before the transaction.

Technology companies rarely return cleanly to an earlier state. Employees learn from new colleagues, systems exchange information, and product road maps change once integration begins.

Meta’s original rationale also remains relevant. The company wanted agent technology that could extend Meta AI from conversation into multistep action.

Manus offered a ready product and an experienced team. Losing the acquisition removes one path toward that goal, but it does not remove Meta’s strategic need for capable agents.

Meta can continue building internally, license outside technology, or pursue partnerships. It can also apply knowledge gained during the transaction where contracts and regulatory restrictions permit.

What it cannot safely do is behave as though the prohibition changed nothing. Regulators will likely examine whether the parties restored genuine independence rather than merely changing ownership paperwork.

The separation therefore pressures both companies.

Manus must rebuild confidence as a standalone provider. It needs to show that its service, team, infrastructure, and financial position can function without relying on the anticipated Meta integration.

Meta must demonstrate compliance while maintaining its broader agent strategy. It also faces uncertainty over which people, code, and operational knowledge remain available after the unwind.

The International Bar Association’s cross-border assessment describes the decision as a warning for AI transactions involving sensitive technology, data, and technical talent.

That interpretation matters for future deals. Buyers may need to complete national-security and technology-transfer reviews before teams begin working together.

They may also need stronger separation plans. Those plans could limit early data sharing, preserve standalone infrastructure, and define what happens if a regulator rejects the transaction after signing.

Such precautions slow integration. They can also reduce the damage if a deal collapses.

For founders, the Manus case weakens a familiar assumption that redomiciling a company creates a clean route to Western capital or acquisition. A Singapore entity can still carry regulatory exposure from technology developed elsewhere.

For investors, the case expands diligence beyond ownership records. They must ask where important code was created, which employees hold critical knowledge, and whether data moved across borders.

For enterprise buyers, the immediate concern is simpler. They need to know who operates the service, which entity holds their data, and whether existing contracts remain valid after independence.

Manus’s public notice does not answer all those questions. It explains the user action required for the transition, not the final corporate structure or long-term commercial arrangements.

The lack of detail should not be mistaken for evidence of failure. Complex separations often unfold in stages, and some information may remain confidential.

Still, the burden now sits with Manus. Independent operation becomes credible through observable continuity, clear ownership, stable service, and accurate handling of affected accounts.

A successful restoration would support the company’s account. Missing files, unclear eligibility, or repeated schedule changes would weaken it.

The first meaningful test begins before the deletion window, when users attempt to export their work.

What the Manus Data Reset Still Does Not Explain

The biggest uncertainty is not whether a reset was announced, but whether users can verify its scope and recover everything that matters.

The August 11 notice provides dates and a broad eligibility rule. It does not provide a complete technical specification for the backup and restoration process.

That leaves several unresolved questions.

First, Manus has not publicly defined every data category included in the export. Users need clarity on conversations, tasks, uploaded files, generated websites, code, connectors, preferences, and shared workspaces.

Second, the notice does not explain whether restoration recreates the same internal relationships among those objects. A complete archive can still produce an incomplete workspace if links and permissions disappear.

Third, the company has not publicly detailed how it will validate restored archives. Users need protection against corrupted files, partial uploads, duplicate projects, and account mismatches.

Fourth, the jurisdictional scope remains unclear. Manus says only certain users are affected because of requirements in particular jurisdictions, but the public summary does not identify them.

That may be deliberate. Eligibility could depend on account history, infrastructure, contract status, or data location rather than a user’s current country.

A geographical list might therefore be misleading. Even so, users need a direct and prominent account-level determination.

Fifth, there is no independently verified account of the deletion mechanism. The company says covered data will be deleted, but outsiders cannot confirm which systems hold copies or how long backup retention lasts.

This is where cautious reporting matters. The timing supports a connection to the Meta unwind, but it does not prove a specific database architecture or data-transfer history.

The report also does not establish that all affected data was controlled by Meta. It would be inaccurate to present that conclusion without a direct statement or technical evidence.

Likewise, the deletion should not automatically be described as a breach. A breach involves unauthorized access or disclosure. Manus has announced a planned compliance operation, which is a different event.

The more credible concern is operational reliability. Can the company complete a large, time-bound migration without losing context or confusing users?

The answer will emerge through the restoration results.

Users should document the process. Screenshots of the eligibility message, export confirmation, file size, project list, and restoration status can help resolve disputes.

Teams should also assign one owner to verify completion. Shared responsibility often becomes no responsibility when deadlines approach.

If the interface appears inconsistent with the notice, users should contact Manus support before the cutoff. They should avoid relying only on community posts, screenshots from other accounts, or assumptions based on location.

The narrow transition window deserves scrutiny, but it also offers a defined test. Manus has published when backup access closes and when restoration should open.

That creates measurable expectations. The company should be judged against them.

What to Watch After Manus Becomes Independent

Three signals will show whether this transition produced a viable independent company or merely a temporary legal separation.

The first signal is restoration accuracy after August 25. Users should be able to recover covered projects without missing files, broken permissions, or unexplained changes.

Successful restoration would strengthen Manus’s claim that the reset is a controlled compliance step. Widespread failures would turn a regulatory problem into a product-trust problem.

Manus should publish clear troubleshooting guidance and acknowledge known limitations. Silence would force users to piece together the outcome through social posts and support conversations.

The second signal is the final operating boundary between Manus and Meta. Users and regulators will look for evidence that ownership, personnel, infrastructure, and product control have been separated as required.

A distinct corporate entity alone will not settle the question. The April decision focused attention on practical control over technology, talent, and data.

Future corporate disclosures, employment changes, or regulatory statements could clarify that boundary. They could also reveal continuing disputes over how far the unwind must go.

The third signal is Manus’s independent product cadence. A standalone company needs to maintain service, release improvements, support customers, and finance ongoing development.

Regular releases would indicate that Manus retained enough technical and organizational capacity to compete. A prolonged slowdown would suggest that the Meta period disrupted the company more deeply.

Competition will not pause during that adjustment. OpenAI, Google, Anthropic, and several specialized agent developers continue to pursue systems that browse, code, research, and operate software.

Manus must therefore solve two problems at once. It must complete a difficult separation and convince customers that its product remains worth building workflows around.

The broader market should watch the regulatory precedent as closely as the product. The foreign investment ruling signals that AI agents can be treated as strategic assets, not ordinary software subscriptions.

That affects acquisition planning across the sector. Startups with engineers, intellectual property, or operational data spanning multiple jurisdictions now carry a larger compliance burden.

Buyers may respond by structuring deals more cautiously. Some will prefer licenses, minority investments, or commercial partnerships over full acquisitions.

Regulators can still examine those arrangements if they transfer practical control. Labels will not determine the outcome when the underlying substance points elsewhere.

For users, the lesson is immediate and less abstract. Open Manus now, determine whether the account is affected, and create a verified backup before the Singapore-time deadline.

Then keep watching after August 25. The quality of the restoration, the clarity of the separation, and the pace of independent releases will reveal whether Manus has truly regained operational independence.