Your data, your server
Privacy
HiBoss connects to a server you choose. This policy explains what the iPhone and Mac apps, the CLI and the MCP plugin handle, and where that information goes.
How HiBoss connects
The apps have no default hosted account. You connect to a HiBoss server by pairing with a one-time code, or by entering a server URL and Boss Token. The apps send authentication requests to that server. The iPhone app stores the server URL in device settings and the connection token in the iOS Keychain. Pairing can also create a signing key in the device's Secure Enclave.
The server you choose may be operated by you or someone else. Its operator controls the storage, access, retention and deletion of data sent to it. Installing the apps alone does not send your messages to the app developer.
Information sent to your server
To show and act on your work, the apps exchange messages, replies, decisions, session content, progress posts, panels and questionnaire answers, Box items, preferences and related media with your selected server. Connecting or pairing can send a device label and a connection or device token. These are used to authenticate and identify the client to that server.
If you allow notifications on iPhone, the app sends the selected server what it needs to address notifications to this installation: an Apple Push Notification service (APNs) device token, or, when the server uses the push relay, a relay handle and a notification key.
Notifications and camera
iPhone notifications pass through Apple APNs. A server reaches APNs in one of two ways. A server with its own APNs key for this app's Apple signing team pushes directly; depending on the server's settings, such a notification may include message text. A server without one sends through the HiBoss push relay, described below, and its notifications reach Apple only as a generic alert and ciphertext that the app decrypts on your iPhone. The private notification option uses a generic alert and retrieves the message from your server after you open the app. If the server's operator turns the relay off and sets no APNs key, the app does not push.
The camera is used to scan a pairing code. The iPhone app processes the code on your device and does not upload camera video for the scan.
The push relay
The push relay at push.hiboss.org is operated by the app developer. It holds the APNs key of the App Store app and forwards notifications for servers that do not have one. When your server uses the relay, the iPhone app registers with the relay and sends it the APNs device token and its environment. Before storing the token, the relay checks it with Apple by sending one silent background notification to the device; a token Apple rejects is not stored. The relay returns a random handle, which the app gives to your server, and a device secret, which stays in the app's Keychain. The app also creates a notification key on your iPhone and gives it to your server; it is never sent to the relay.
For each notification, your server sends the relay the handle, the kind of notification (decision, message or system), the content encrypted with the notification key, an optional grouping identifier and its urgency: priority, interruption level and whether to play a sound. The relay turns this into a generic alert with the ciphertext attached. Only your server and your iPhone hold the key to decrypt it.
The relay stores the APNs device token and environment, digests of the handle and device secret, when the registration was created and last used, and counters for its usage limits. Like any web service, it receives the source IP address of each request, and for a server hosted on Cloudflare Workers the domain of that Worker; it uses them only to limit request rates and does not store them. It never receives message titles, bodies, answer options, sender names or account information, and it writes no logs of handles, secrets, device tokens or ciphertext. It can observe which handles a server pushes to and when.
A registration that receives no notification and no token update for 30 days is deleted automatically. A registration is also deleted when Apple reports its device token as no longer valid. Your server's operator can turn the relay off or use their own APNs key, in which case your server does not contact the relay.
The Mac app
The Mac app connects to your server the same way, by pairing with a code, signing in with your iPhone, or entering a server URL and Boss Token. It stores the connection token in the macOS Keychain. It shows notifications locally from messages it receives from your server; they do not pass through APNs.
Release builds of the Mac app check for updates with Sparkle. By default they check once a day against the update feed at hiboss.org, not your HiBoss server, and download updates from the project's GitHub Releases. The request carries the standard information of an update check, such as the app version, and no system profile. Updates are verified with an EdDSA signature before they install. You can turn off automatic checks in Settings → About. A build without an update feed never checks.
The CLI and MCP plugin
The hiboss CLI and the MCP plugin talk only to the HiBoss server you configure. The one exception is guided Telegram or Discord setup, which calls those services' APIs with the bot token you provide. The CLI stores its server address and agent keys in a local configuration file readable only by your user account.
Analytics and tracking
The iPhone and Mac apps contain no advertising or third-party analytics SDK. They do not use app data for cross-app advertising tracking. A server you choose may use its own service providers; ask that server's operator about their practices. This website sets no cookies and loads no third-party scripts.
Retention and your choices
Signing out disconnects the iPhone app and asks iOS to remove the saved connection token and signing key. If Keychain removal fails, those credentials may remain on the device. The previously entered server URL remains in device settings. Signing out or removing an app does not delete content stored on the server.
Signing out does not remove the APNs device registration from your server. To stop alerts on this device, turn off HiBoss notifications in iOS Settings. Contact the server's operator to remove its device registration or to access or delete server-side data.
You can deny or change notification and camera permissions in iOS Settings. Without camera access, you can still enter a server URL and Boss Token manually.
Questions
For questions about the apps or this policy, email [email protected]. For a server you do not operate, direct requests about its stored content to that server's operator.