Privacy

What the phone app keeps

• The sign-in credentials for each computer you pair, in the iPhone Keychain or the Android Keystore. They stay on this phone: they are not synced or included in backups, and they are wiped when you unpair or when the computer revokes the phone.
• The list of paired computers (their names and addresses) and the app's settings.
• No analytics, advertising or crash-reporting code.

What leaves the phone

• Everything you do in the app goes to your own computer, and nowhere else.
• Images you share into an agent's queue go to your computer with their location and other metadata removed first.
• If you allow notifications, the phone's notification token and its name go to the aasc.work backend, so your computer can send you notifications.

Notifications

Your computer decides when to notify you; the backend passes the notification to Apple (APNs) or Google (FCM), which deliver it. A notification says what kind of event it is (approval needed, waiting for your input, finished, interrupted), the session's title (AASC may have made it from your first prompt) and, when an agent is waiting, the name of the tool it wants to use. Never the command, prompts, terminal output or file contents. The backend can be set to send only “A session needs you” instead. On Android the text is hidden on the lock screen; on an iPhone it follows your Show Previews setting.

What the aasc.work backend stores

• Your devices: names, platform, permissions, and hashed (never plain) tokens and pairing codes.
• Notification tokens for the phones that allowed notifications.
• Delivery counts, kept 30 days, with a one-way hash of each notification to avoid sending it twice. The notification text itself is not kept after sending. Used pairing codes are deleted after 7 days.
• If you turn on notes sync on your computer: the favourites, tags and short names you gave your agents' skills, not the skills themselves.

It never stores session content, prompts, terminal output, file paths or Git credentials.

Removing your data

• Revoking a phone on your computer (devices panel → Revoke) cuts it off at once and deletes its notification token from the backend.
• Unpairing in the app does the same from the phone, and wipes its credentials.
• The backend's owner can export or delete everything stored for an account.

Questions

Open an issue on GitHub, or read how pairing works in the documentation.