Saeta is in development and has no public release yet. This page describes the current development build and our plans.

Security & privacy

Know where your data goes.

Approval details are local, and remote payloads are sealed for your devices. Routing an encrypted message still reveals routing metadata.

Local decisions

The local daemon, inbox, trust list and activity history run on your computer. An account is optional for local approvals. Local history can contain sensitive action details; protect your operating-system account.

End-to-end encrypted relay

The desktop seals a separate copy for each paired phone using X25519 and XSalsa20-Poly1305 sealed boxes. The phone's decision is sealed to the desktop and signed inside the payload. The gateway routes ciphertext and does not hold the private keys used to decrypt approval details.

What the gateway can see

Account email, subscription state, public identity keys, pairing relationships, push tokens, request identifiers, timing, aggregate relay counts and network metadata are visible to the service. Browser labels for devices are also stored there. Local commands, file paths and request summaries are not included in the aggregate dashboard.

Push without the request text

Firebase push carries a request identifier. The phone fetches the ciphertext and decrypts it. Lock-screen presentation and device authentication still need real-phone acceptance before launch.

Pairing needs a trusted check

The verification code is checked on the desktop and phone. Pairing always starts on the desktop; the account dashboard can list, rename and revoke paired phones, but cannot start a pairing or replace that trusted confirmation.

The boundary

Saeta is a guardrail against mistakes, not a sandbox for a hostile agent. A process that can change your integration configuration or run commands independently can bypass the intended approval path. Advisory MCP also depends on model cooperation.

Web sessions

Browser sign-in links are single-use, short-lived and bound to the browser that requested them. Session cookies are HttpOnly, Secure and SameSite=Lax. Changing account API calls require a same-origin custom header; the gateway grants no CORS access.