Security & privacy
Pushary is built on data minimization. The decision path needs the question and tool name, nothing more. Pushary-launched transcripts sync only after local redaction and encryption for the owner's phone and documented compliance recovery. Here is exactly what that means.
A lightweight hook runs in your agent (Claude Code, Codex, Cursor, Hermes, or any MCP client) when a tool call needs a decision. The agent and your code stay on your machine.
Pushary forwards the question and tool name to its API, applies your per-tool policy, and sends a push when a human decision is needed. Synced transcripts use a separate path that redacts and encrypts content on the agent machine for the owner's phone and documented compliance recovery.
You approve, deny, or answer from your lock screen. The decision page links are HMAC-signed so they cannot be forged.
Your answer returns to the hook and the agent keeps working. The question, tool, and your decision are written to an audit trail, never your code.
Pushary has two data paths. The decision path is always on and deliberately minimized: it carries the question and tool name, preserving a server-side, queryable audit trail. Pushary-launched transcript sync is on by default, but redaction and encryption happen on your machine first. The session key is wrapped independently for the owner's phone and Pushary's compliance recovery key; authorized admins can recover one exact session for a documented legal obligation. You can disable sync on the agent machine. Traffic is over HTTPS, decision links are HMAC-signed, and pending questions expire from cache on a short timer.
Not on routine product paths. The decision path sends the question text, tool name, and minimal notification metadata. Pushary-launched transcripts sync after local redaction and encryption. The owner's phone can decrypt them, and authorized Pushary compliance admins can recover an exact session for a documented legal obligation.
No. Pushary uses provider-managed encryption for synced transcripts, not end-to-end or zero-knowledge encryption. Redaction and encryption happen on the agent machine first. The session key is wrapped independently for the owner's phone and Pushary's compliance recovery key, so authorized admins can recover an exact session for a documented legal obligation. The decision path remains minimized and queryable for the audit trail. You can disable transcript sync on the agent machine. Traffic is over HTTPS.
Pending questions are held briefly in Redis with a short time-to-live and then expire. The audit trail records each question, the tool involved, and the human decision (who decided, when, and under which policy), so you and your team have a record. It does not store your code.
No. Decisions are scoped to your account and site, and the decision page URLs are signed with an HMAC secret, so a link cannot be forged or replayed by someone else.
Approve from your phone, set guardrails once, and keep an exportable audit trail. Works with Claude Code, Codex, Cursor, Hermes, and any MCP client. 3-day free trial.
