Security Architecture & Verification
Technical guarantees, hardware-backed cryptographic vaults, and privileged execution limits.
Windows beta status: the early Windows beta is unsigned and installed manually. A checksum verifies the downloaded bytes against the published hash; it is not a verified publisher identity or a guarantee that software is safe. Some Windows security policies block unsigned apps. Do not disable protection to use this beta. The mechanisms below do not imply independent security certification.
1. The Owner Trust Boundary
Zaya implements a strict privilege isolation boundary: External content is strictly DATA, NOT AUTHORITY. Incoming WhatsApp messages, scraped webpage text, OCR strings from screen perception, and tool stdout streams can never grant themselves permission to execute system commands, access files outside designated workspace roots, or alter security configurations.
2. ToolResult & The Full Access Confirmation Gate
Every action executed by Zaya passes through the ToolResult audit model:
Verified and completed with recorded proof-of-work
Process launched but state cannot be inspected
Irreversible action requires on-screen owner confirmation
Execution error; captured in local diagnostic log
When Full Access is toggled OFF (default), all shell commands and file deletions trigger a modal prompt. Enabling Full Access does not bypass Windows User Account Control (UAC).
3. Hardware-Backed DPAPI Secret Vault
All user credentials, including Gemini API keys, provider tokens, and mobile pairing hashes, are protected on disk using Windows DPAPI (Data Protection API). Keys are encrypted with the active user account's SID and Windows login credentials. Copying api_keys.json to another machine results in unreadable ciphertext.
4. Isolated Subprocess Workers
Optical hand tracking and screen OCR run inside an isolated subprocess (ZayaHandWorker.exe). Camera frames are processed strictly in RAM to infer 21 coordinate points and are immediately overwritten. Raw video never touches the application main thread or persistent disk.
5. Binary Integrity & SHA-256 Verification
Verify official releases before running by checking the SHA-256 hash in PowerShell:
Get-FileHash -Algorithm SHA256 .\ZayaSetup.exe6. Vulnerability Disclosure
To report security considerations responsibly, email ab4290025@gmail.com. Please do not post unpatched vulnerabilities in public GitHub issues.