Data Privacy & Local Sovereignty

Exact disclosures regarding data storage, model transmission, and local network operations.

Optional product analytics

Disabled by default. If you opt in, Zaya sends a random installation UUID, platform and version once per UTC day in version 0.5.1 and later. Failed requests can retry; earlier versions report every two minutes. Packaged Windows releases may also send update stage and target version: update offered, download verified, installer process started, or failure. No error text, paths or download URLs are included. Update reports become daily aggregate counts; short-lived event receipts prevent duplicate counting and contain no installation identifier. Installer launch is not proof of completed installation. Daily active installations count each opted-in installation once per UTC day, not people. No Google API traffic or conversation content is used. Inactive installation records have a 90-day retention target. Bounded expiry cleanup runs on backend request traffic; deletion can be delayed when the service is idle or a cleanup backlog exists. Download clicks are aggregate counters, not proof of installation. Product analytics store no IP addresses. Abuse protection uses keyed identifiers that change each rate-limit window, with short expiry timestamps. Hosting providers may process network metadata for security.

No prompts, conversations, file names, screen contents, contacts, WhatsApp messages or API keys are collected. Turning analytics off stops future submissions. Website Google Analytics requires a separate opt-in when configured.

Optional website reports

Website analytics require permission. If allowed, the site counts public page views, 30-minute visits and platform download clicks, with broad device, browser, operating-system and traffic-source categories. Browser identifiers are random and rotate every 30 days; they are estimates of browsers, not people. No full referrer URLs, query strings, IP addresses, precise locations, fingerprints or private app content are stored in these reports. The backend keeps anonymous identifiers for a 90-day retention target and short-lived duplicate-event receipts for one day (anonymous download-browser deduplication receipts last up to 90 days). Bounded cleanup runs on request traffic and can be delayed during idle periods or backlogs. Anonymous aggregate counts remain for historical reports. Admin pages are excluded. Declining stops future submissions and removes the website identifiers from that browser. Do Not Track and Global Privacy Control are respected. Optional Google Analytics, when configured, uses the same explicit permission. Earlier visits cannot be reconstructed.

1. The Sovereign Local Principle

Your conversations, memory, tasks and configuration remain on your computer. Firebase stores release metadata and optional product/website analytics; it never receives your private Zaya history or provider keys.

2. Continuous Perception Privacy

Continuous screen perception runs entirely on-device via differential frame hashing (mss and OpenCV) and Windows native WinRT OCR streaming through standard memory buffers. No video feed of your desktop is ever streamed to cloud servers.

3. AI Provider Network Transmission

When you initiate a conversational voice turn or issue a desktop command:

  • Cloud Provider (e.g. Gemini / OpenAI): The active audio packet or text prompt is transmitted directly from your PC to the provider's API. No third-party proxy intercepts your traffic.
  • Modular Local Pipeline (Ollama / llama.cpp): Speech transcription, language modeling, and voice synthesis run completely offline on your local GPU/CPU. Zero bytes leave your machine.

4. Optical Tracking & Camera Frames

Your webcam is only accessed if you explicitly enable optical hand tracking. The camera remains completely OFF at normal startup. When active, frames are analyzed inside an isolated child worker strictly for 21 joint landmark coordinates; image frames are immediately discarded from memory without writing to disk.

5. WhatsApp & Android Companion Communication

WhatsApp auto-replies use only current session activity (e.g. listening to music or working on a project) and will never expose private conversation logs or files. The Android companion connects to your laptop over your local home Wi-Fi using encrypted WebSockets; keys are protected by the Android Hardware Keystore.