Privacy

This policy covers the flockr iPhone app. flockr is free and open source: github.com/flockr-sh/flockr.

The short version

• No account.
• No analytics.
• No crash reporting.
• No tracking.
• No flockr servers. There is nothing on our side to send your data to.

Where the app connects

The app talks only to the flockr server on your own computer. You pair the two by scanning a QR code, and the connection is end-to-end encrypted (Noise).

Push alerts

Push alerts are the one thing that leaves your network. Your flockr server sends each alert through Expo's push service and Apple's push service. An alert carries:

• the agent's name and status
• the workspace, tab, and machine name it runs on
• IDs the app uses to open that agent
• for a blocked agent asking a plain Yes / No question 1.2.0: the question and the command or file it wants to act on (for example "Do you want to proceed? · npm test"), the labels of its answer options, and a state number the app uses to check the prompt before it answers

To keep all prompt text on your computer, set alert_prompt_text = false in the [mobile.push] section of your server config. No question, command, or option label leaves your computer. Alerts then carry only the agent's name and status, where it runs, IDs, and a fingerprint (a hash) of the prompt. The answer buttons still work: the app re-reads the screen and answers only if the fingerprint matches.

Expo keeps alert contents only as long as it needs to deliver them, in memory and queues, not in a database (Expo push notifications FAQ). Expo's privacy policy says it may store the device push token (expo.dev/privacy).

To stop push alerts entirely, turn off notifications for flockr in iOS Settings, or set enabled = false in [mobile.push] on your server.

Data on your phone

The app stores your paired servers and device tokens in the iOS keychain. Removing a server in the app, or deleting the app, removes them.

Contact

Questions about privacy: open an issue at github.com/flockr-sh/flockr.