Operational Risks Associated with Unilateral Account Suspensions

I would like to raise an important concern regarding the process of account and application suspensions on Base44.

I understand that the platform must maintain usage policies, security standards, and compliance requirements, and I recognize that violations may require firm actions. However, when we are dealing with complete systems built on Base44’s infrastructure, a unilateral suspension — without prior notice, without minimum transparency, and without an adequate mitigation process — can generate serious consequences not only for the creator of the application, but also for all end users who rely on that system in their daily operations.

My concern is that a suspended account may effectively result in the immediate interruption of real-world operations, impacting customers, teams, data, internal workflows, and the trust of an entire ecosystem already in operation.

For this reason, I would like to suggest that the suspension process be redesigned with greater care, transparency, and proportionality, including whenever possible:

• prior notice in non-critical cases;

• clear communication regarding the reason for the action;

• a remediation or compliance adjustment window;

• a human review mechanism;

• the possibility of secure data export or recovery;

• consideration of the impact on the end users of the affected application.

Platforms that enable the construction of complete systems also carry a responsibility proportional to the impact that a suspension may cause. Therefore, I believe Base44 should adopt a more careful process, especially when such measures may unilaterally terminate entire operations already running in production.

I make this statement respectfully and with the intention of contributing to a more mature, predictable, and secure policy for everyone building real businesses on the platform.