Current prototype posture

Privacy & security

Agent Maxer is an active developer preview. This page explains the controls implemented in the current codebase and the remaining gates before broad public distribution. It is a product overview, not a final App Store privacy policy.

The short version

Agent Maxer is designed to reveal only the ambient state needed by your Apple surfaces. Agent credentials, prompts, repositories, source code, local paths, and command output stay on the Mac and are not sent to the hosted bridge.

What leaves your Mac

DataBridge accessRetention

Chat ID, short title, state, timestampReadableLatest tenant state

Optional final response for speechEncrypted onlyUp to 24 hours

Pairing keyRequest authentication; not stored rawDevice Keychain

ActivityKit and WidgetKit push tokensEncrypted at restUntil replaced or removed

Controls implemented today

Each Mac generates a random 256-bit pairing key and keeps device copies in Keychain.
The bridge derives tenant identity with SHA-256 and does not persist the raw pairing key.
Push tokens are encrypted at rest with AES-256-GCM.
Optional speech content is encrypted on the Mac and decrypted only on the paired iPhone.
Requests, stored state, acknowledgements, tokens, and speech envelopes are tenant-scoped.
The bridge runs in an isolated cloud project with a dedicated runtime identity.

Known public-launch gaps

The current prototype does not yet include installation attestation, abuse quotas, pairing-key rotation, per-device revocation, account recovery, a remote deletion workflow, or a finalized App Store privacy policy. These are release gates, not hidden claims of completion.

Pairing responsibility

Pairing is possession-based. Treat the QR code and pairing link like a password: anyone who captures it can act as that tenant until rotation and revocation ship.