HOREF LABSHoref Pulse 1.9 · Updated 1 November 2026
Privacy information
This page describes the Horef Pulse app for Mac. If the app starts handling data differently, this page will be updated first.
No data collection
Horef Pulse does not collect, store or share personal data. It has no account, no advertising and no analytics. It connects to the network only to check for updates and, if you turn on iPhone access, to reach your iPhone (below): once a day it reads its own version file on horef.app (you can turn this off in the App updates window), and while you have the App updates window open it asks Apple’s App Store about the App Store apps on your Mac by their bundle IDs and reads the update feeds your other apps name. When you install a Horef Pulse update, it downloads it from horef.app. Nothing about you or your Mac is sent beyond these ordinary web requests.
On your Mac
The app reads system load and the list of running processes on your Mac. It keeps the load of the last 10 minutes for the charts in memory only, and stores the latest snapshot, quit and cleanup proposals and a log of what was stopped, quit or cleaned in ~/Library/Application Support/HorefPulse. To show what can be cleaned it measures developer caches in your home folder (such as ~/Library/Caches and ~/.npm) and build folders in project folders such as ~/Developer, and only after you allow it looks in Downloads, Desktop and Documents for old installers and project build folders; it reads names, sizes and dates, not file contents. To uninstall an app it lists the apps in Applications and looks in ~/Library for files named after the app you pick. It removes only what you select in the Free up space and Uninstall windows; uninstalled apps and their files go to the Trash, or are deleted at once if you choose that. To show what takes the space it reads the names, sizes and dates of files on the disk you choose (never their contents), skipping folders macOS protects unless you allow them, and keeps folder sizes and free-space history for 30 days in the same folder, to tell what grew. For the desktop widgets it writes a short load summary into its own app-group folder; the network section reads the speed and signal of your connections, not the network name or any traffic content. When you click Connect, it changes the configuration of Claude Code (~/.claude/settings.json and its MCP server list) and of Claude Desktop, keeping a backup of each file. If you enable fan control, a helper that you allow in Login Items runs with system privileges; it only reads the fans and sets their speed, accepts requests only from Horef Pulse itself, and sends nothing anywhere. What it reports goes only to the AI tools you connected on this Mac; what those tools send to their providers is covered by their own privacy policies.
Terminal and iPhone access
The terminal’s sessions run in a server process on your Mac that only your user account can reach; what they show stays on your Mac unless you open a session from your paired iPhone. iPhone access is off until you turn it on. Then your Mac and the iPhones you pair talk over an end-to-end encrypted channel (the Noise protocol; keys are created on the devices and never leave them), on your local network, or, when the iPhone is elsewhere, through a relay on horef.app. Other Macs you pair the same way, to watch this Mac’s load in My Macs, use the same channel. While iPhone access is on, the Mac keeps a connection to that relay. The relay passes the encrypted messages between the two devices and cannot read them; it keeps no message content, only what it needs to route them: a random identifier of your Mac and a hash of its relay token. Pairing uses a one-time code shown on your Mac. The iPhone app stores the pairing and its own key on the iPhone, and keeps the Mac’s last status in its app group for its widgets. Revoking a device on the Mac or turning iPhone access off ends access at once. If you turn on notifications in the iPhone app, the iPhone gives your Mac, over the encrypted channel, its Apple push token and a key of its own; the Mac encrypts each notification’s text with that key and sends it through the relay to Apple’s push service, which delivers it to your iPhone. The relay and Apple see the push token, the time and that a notification was sent, not its text; the relay keeps nothing but a count of notifications per hour (at most 60) to prevent abuse. When you ask Horef Pulse to read or type into iTerm2 or Terminal sessions, it uses those apps’ AppleScript, after macOS asks you to allow it.
Support messages
Emailing support sends the content you choose to include through your email provider and our support mailbox. Contact support@horef.app for questions or deletion requests concerning support correspondence.