The higher the permissions, the more concrete the risk of losing control. Step Terminal built a 'trustworthy, visible, controllable, reversible' security foundation in Step AOS: all data uploaded to the cloud is desensitized, and phone numbers, precise locations, and sensitive multimodal images will not be recklessly used without limits; all tool calls, permission requests, and execution chains are fully logged; at high-risk nodes such as deletion, payment, and cross-app operations, a pop-up must trigger the user's secondary confirmation, and authorization boundaries can be revoked with one click at any time; photos, files, notes, or contacts mistakenly deleted by the agent can be restored step by step or as a whole by the system. A separate 'Agent Security' module is listed in system settings, where A-Zai's permissions can be managed and visualized Tool Call records can be viewed.
Thresholds are also set on the ecosystem side: Step Terminal requires all publishers to complete real-name verification consistent with their phone number, all Skills and Agents must be under real-name registration, and it will block uploads of privacy files including .env, key files, databases, logs, or USER.md.
These mechanisms are currently all self-reported by Step Terminal or the author, lacking third-party verification. The actual effect of the 'trustworthy, visible, controllable, reversible' security foundation lacks independent evaluation support, and actual test data or vulnerability audit results for the security mechanisms have not been disclosed. In personal agent scenarios, users' willingness to entrust is a key variable for scaling, and this variable precisely depends on externally verifiable security evidence.