Ajar Privacy Policy

Effective September 27, 2026. Ajar is developed by Robert Torres.

Your terminal and credentials

SSH connections run directly between your device and the computer you choose. Ajar’s notification service does not receive your SSH keys, passphrases, commands, terminal output, host names, or IP addresses of saved connections. Saved SSH keys use Apple Keychain on your device and do not sync through Ajar or iCloud.

Optional completion alerts

If you enable alerts, our service processes an opaque installation identifier, an Apple push notification token, random session, event, and journal identifiers, event sequence and creation time, event type, optional elapsed time, an optional fixed agent identifier (Claude or Codex), success/failure/input-needed status, and optional opaque tmux window identifiers and numeric window indices. A helper on your computer sends generic events when a task finishes or needs your input. Computer, session, and window names and terminal content stay outside this service. Network providers necessarily receive the source IP address of requests to deliver and protect the service.

Pro subscriptions

Apple processes purchases and payment information. Ajar receives signed purchase information, product and transaction identifiers, subscription status, expiration, and an opaque purchase account token. We verify these with Apple and link them to your alert installations to provide access, restore purchases, and respond to renewal, expiration, or refund. We do not receive your card details.

App integrity

Apple App Attest helps verify that service requests come from a genuine copy of Ajar. We retain the verified public key, its identifier, environment, and a request counter for your installation. Short-lived challenge identifiers prevent replay. We verify and discard attestation objects and receipts; these are not included in operational logs. App Attest does not send us your Face ID data, private device key, SSH credentials, or terminal contents.

Service providers and retention

Cloudflare hosts the alert service; Apple verifies purchases and delivers notifications. We use this data to operate and secure Ajar, not for advertising or cross-app tracking. We do not sell your data. Alert registration records are kept while needed to deliver or disable alerts. Event identifiers are retained temporarily to prevent duplicate delivery. Subscription records may remain to enforce expiration and refunds and support restoration. Operational logs contain aggregate-friendly request operation, status, error category, latency bucket and duplicate indicator; they exclude private keys, purchase proofs, push tokens, host names, App Attest objects, and terminal content. Deleting service data removes the installation’s push token, pairings, and retained event records. Minimal opaque ownership and disabled-installation records, App Attest replay protection, and subscription/refund history remain to prevent deleted credentials or old purchase proofs from restoring access.

Your choices

You can disable alerts per session, view or remove devices linked to your Pro subscription, and delete this installation’s alert-service data in Ajar. You can also revoke notification permission in iOS Settings, delete saved keys in Ajar Settings, and manage or cancel Pro through Apple’s subscription settings. Cancelling Pro pauses new alerts after your access ends; SSH and tmux remain available. Deleting the app does not cancel an Apple subscription.

Contact

For privacy requests and support, visit Ajar support. Do not include keys, passwords, payment information, or terminal contents in a support request.