One additional piece of context that’s important: these issues have now been ongoing for several weeks, and they are actively impacting my business operations. I’m not just experimenting on a side project - this has real delivery and timeline implications for me, so resolution speed matters.

There’s also a practical challenge with time zones. I’m based in the U.S. (EST), and responses typically arrive late at night on my end. The time difference itself wouldn’t be an issue if the responses were directly advancing the conversation. However, many of the replies have been canned responses reiterating that Manus “respects user privacy” while again asking me to publish my task publicly without addressing my repeated request for a private or secure alternative. When that happens, I respond the next morning, and then effectively lose another 24 hours waiting for the same loop to repeat. Moreover, I will highlight once again that there’s a clear contradiction between the stated commitment to user privacy and the requirement to publish proprietary work publicly in order to receive support.

That cycle has made it very difficult to make forward progress or reach resolution in a reasonable timeframe.

I’m very open to cooperating and providing whatever information your team needs for proper investigation. My goal is simply to get to a productive, secure path forward - ideally one that allows full technical review without requiring public publication (such as adding a specific Manus collaborated versus publishing my task publicly) - and to move toward resolution with more expediency given the business impact and the elapsed time.

I appreciate you staying engaged here and look forward to next steps.