Privacy
What stays on your computer, what leaves it, and the boundary of each promise, stated plainly. This page describes the build as it is. Nothing here changes without this page changing first.
Where your photos are
Your photos stay in your folders. Borago reads them there, never moves, copies, renames or edits one, and never uploads one.
Indexing, search, voice, places, face grouping and Studio all run on your computer. There is no server that sees a photo, a thumbnail, a file name or a folder. You need no account, and there is nothing to sign in to today. Borago is fully usable with no network connection at all.
What leaves the device
An update check, and what you ask for. Nothing else.
| What | When | Who sees what |
|---|---|---|
| An update check | In a packaged build, 30 seconds after the window opens and every six hours while it stays open. An AppImage that finds a newer version downloads it from the same place | Borago Soft's update server sees your address and which platform's version file was asked for. Nothing about you or your library |
| Model downloads | Only for an installation missing its models. Every package carries them. The offer names where they come from and their size | Borago Soft, Hugging Face and GitHub, the hosts, see your address and which file was fetched. Nothing about you or your library |
| A web image you allow | When an image dropped or pasted into the window arrives as a web address. Borago asks first, naming the site, each time or always | That site sees your address and the request, as a browser's would. Nothing from Borago |
That is the whole list. No crash report, no usage statistics, no search ever leaves the computer. Studio's window is refused every request that is not for its own files. A check script runs the window and the agent through indexing and a search and fails on any connection off the machine. It is run after any change to a dependency or a model, and it has caught two defaults that broke this rule before they shipped: a browser engine fetching a spellcheck dictionary, and an inference runtime reporting usage to its maker. Both are closed.
Faces
Face data never leaves the device under any circumstance. Not under a paid plan, not by opt-in, not by any setting that exists or will be offered.
Borago can find the faces in your photos and group the same face together, on your computer, from the photo's own thumbnail. It never names anyone itself. You can name a group, and search by that name. What it stores is a representation of each face, its box, its group and the name you gave it, inside the encrypted index. Nothing from those tables is sent anywhere: not the representations, not the boxes, not group names, not the fact that a photo has a face.
The face models come with the application, but the face pass runs only once you turn on Find faces in Settings, Faces, which is off by default and not part of the first run. Biometric identifiers are separately regulated in several places, and sending a face template to any third party is out of scope for this product permanently, not merely unbuilt.
Voice
Speech is understood on your computer. While listening for a wake phrase, no audio is recorded, written to disk or sent.
Always-on listening is off until you turn it on. While it is on, the microphone is read into memory in small frames, each frame is checked for the phrase, and each is dropped once checked. The only thing the listener ever reports is which phrase it heard. A spoken search is held in memory for the length of the search and is gone when it ends. The listening state is visible in the tray from outside the window, and saying stop listening turns it off from anywhere.
The index and the thumbnails
The index and the thumbnail cache are encrypted with a key kept in your system keychain. That keeps your library from other accounts on the machine, from backups and from anyone with the disk.
It does not keep it from a program running as you, which can ask the keychain for the key as Borago does. The privacy screen in Settings says exactly this, rather than describing the encryption as stronger than it is. The logs are encrypted with a key of their own, kept the same way, and never record what was searched for, only how many words. Where there is no keychain, Borago says so in Settings.
A screen that says what is kept
The last section of Settings lists what Borago stores, where, and what leaves the computer, in plain words, with a Show button that opens each place in your file manager. It names the update check and the download hosts above, and lets you turn an Always allow for web images back into a question.
Deleting everything
Delete all data, at the end of Settings, removes everything Borago keeps: the index, thumbnails, settings, logs and Studio's storage. It asks twice, the second time by typing delete. Models go too unless you keep them for whoever uses Borago next. Photos in Borago's own folder go only if you choose that, after a warning that some may be the only copy. Photos in your own folders are never touched. Borago then starts again from setup.
No account, no telemetry
There is no analytics and no telemetry, and there is nothing to opt into. Every feature works with no account. Settings has an Account section for Borago's cloud, which is not running in this alpha. It says the service is not reachable, there is nothing to sign in to, and nothing is sent.
This website
This site sets no cookies and runs no analytics. The theme switch remembers your choice in your browser and nothing about it is sent. The website notice has the rest.
Related: Privacy and data in the features, FAQ, Report a vulnerability.