Privacy policy
Last updated: November 13, 2026
Edith is built local-first. The app has no accounts and collects no telemetry. Usage and ordinary app data stay on your device unless you enable iCloud backup. The optional Companion stores its memory on a Mac or SSH machine you choose and only calls an external model or connector when you configure one. The only thing Edith sends us is the license check described below, which carries no app data.
What the app stores, and where
- Usage analytics (tokens, costs, rate-limit history) are computed on your Mac from local files that your coding tools already write, and are stored in the app's local data folder.
- Clipboard history, shelf files, music, and settings are stored locally on your Mac.
- SSH machine definitions are stored in Edith's application data. Login passwords, passphrases, sudo passwords, and Companion deployment secrets use the macOS Keychain. Deploying Companion writes its required secrets into a permission-restricted
.envfile on the selected host. - None of the above is transmitted to us. The licensing server described below is the only Edith server, and it never receives app data.
Licensing
Edith needs a license, and each license covers a fixed number of Macs. To enforce that, the app talks to the licensing server at getedith.pro when you activate it and while it runs. This is what the server keeps:
- For each license: a keyed digest of the license key and its last four characters (never the full key), the email address it was issued to, the number of Macs it covers, and its status.
- For each activated Mac: a random device id, the public half of a device key that is created on the Mac and never leaves it (the Secure Enclave when the Mac has one), a hardware digest, the Mac's model identifier (such as Mac15,3), the Edith version, when it was first activated and last checked, and its status.
- The hardware digest is computed on your Mac as a one-way hash of the Mac's hardware UUID and serial number, then hashed again on the server with a secret key. The UUID and serial number themselves are never sent. The digest is how a seat stays tied to one Mac: the same Mac can reinstall and reactivate, and a different Mac cannot use a seat it does not hold.
- A log of license events (activations, refusals, device changes, disabling and enabling) with the license, device and time.
While Edith is open and online, it sends a signed license heartbeat about once a minute and when it launches, wakes or reconnects. A heartbeat holds the device id, the hardware value, the Edith version, what triggered it (such as launch or wake), a timestamp and a random nonce, signed by the device key. The server answers with a signed status. Update checks and extension downloads carry a short-lived token bound to the same device. None of these requests contain usage data, file names, clipboard contents or anything else you do in the app.
Your IP address is used only in short-lived counters that rate limit activation and download requests, and is never stored with a license or device. License and device records are kept while the license exists, and you can ask for a license and its devices to be deleted by emailing the address below. Deactivating a Mac in Settings deletes its credentials from that Mac. Its seat stays bound to that Mac's hardware.
Optional Companion
Companion is a self-hosted memory backend. Its PostgreSQL database, plain-file vault, models, recordings, and derived memory live in container volumes on the host you select. A remote deployment is reached through an SSH tunnel to localhost. Edith's iCloud backup does not copy the Companion database or vault.
Embedding, vision, and speech-to-text models run on that host. Reasoning can also run there, or you can configure an external provider. If you choose an external provider, the request and the context needed to answer it go directly from your Companion host to that provider under its privacy terms. GitHub and Notion sync likewise contact those services only after you provide a token and request a sync. Companion settings let you export the memory, erase derived data, or wipe the database and vault.
Remote machines
Machine monitoring, terminals, file operations, container control, power actions, and remote usage collection travel directly between your Mac and the SSH host you configured. We do not relay those connections. Actions you run can change files, services, power state, or thermal settings on that host, just as the equivalent SSH command would.
Rate-limit checks
To show live session and weekly limits, the app queries your AI provider's API directly from your Mac using credentials already on your machine. Those requests go from you to your provider. Edith never sees them.
Optional iCloud backup
If you enable iCloud backup, the app copies the categories you select, including settings, usage history, rate-limit history, music, and clipboard history, into your own iCloud Drive so it can merge across your Macs. That data is governed by your Apple account and Apple's privacy terms. Turn the toggle off and the app stops syncing. Companion memory and remote machine secrets are not included.
No accounts, no telemetry
- No sign-up, login, or account of any kind. A license key is all you need.
- No analytics SDKs, crash reporters, or tracking pixels inside the app.
- No advertising, and your data is never sold or shared, because it never reaches us.
Software updates
The macOS app checks for new versions and downloads extensions through getedith.pro, which checks the license token described above and then sends the app to the file in Edith's release repository on GitHub. That download goes from your Mac to GitHub and is subject to GitHub's privacy statement; like any web request it exposes your IP address to GitHub. The license token is the only identifier Edith attaches, and the update check can be turned off in Settings.
This website
getedith.pro is hosted on Vercel, and the licensing database runs on Neon (PostgreSQL). Vercel keeps standard, short-lived server logs (such as IP address and requested page) to operate the service. The site sets no cookies and includes no analytics or trackers.
Changes
If this policy changes, the new version will be posted here with an updated date. Material changes will be noted in the app's release notes.
Contact
Questions about privacy? Email me@pulkit.page.