orbleRequest access

Privacy

This website

orble.ai has no analytics, no cookies and no third-party scripts. Its fonts and images are served from this site.

If you ask for access, we keep three things: your email address, the answer you chose to “You'd use it for” if you chose one, and the time you asked. They are stored in Cloudflare Workers KV, under Orble's Cloudflare account, and used for one thing: writing to you about access to Orble. We don't keep your IP address or anything about your browser, and we don't share or sell the list.

To have your address removed, ask us from that address and we will delete it.

The app

What follows is the privacy page that ships with Orble itself, as written.

Updated 3 November 2026.

Orble has no account and no telemetry, keeps no crash reports unless you ask it to and never sends one itself, and sends nothing about you to its makers. Your screen stays in memory for about a minute, and the moments it changed for ten minutes, and is never saved to disk.

Normal mode

Orble talks to the services whose keys you entered, to GitHub for updates, and, when you attach a link, to that link's site:

Privacy Mode

With Private on (Settings), Orble uses only programs on your Mac: Ollama for answers; whisper.cpp, Apple's on-device recognition or VoiceStudio for listening; VoiceStudio, a speech server you run on this Mac (such as Kokoro-FastAPI) or the macOS voice for speaking. The local model can't draw on the board or search the web; what it points at is found by a model on your Mac too (the Pointing model in Settings → Local-first), or, with none set, by the names your apps give their buttons and menus.

Orble never sends requests to Ollama, VoiceStudio, a speech server or a local decision model through a web proxy, whatever your Mac's network settings say. Known gap: pasting a Claude or Gemini key in setup turns Privacy Mode off.

When you turn Privacy Mode off, nothing Orble saw or said under it goes to a cloud model. The screenshots it took then, the moments it kept of the screen and a /display still are dropped. What you asked and the local model answered stays on your Mac: Recent still shows it, and the local model has it again the next time Privacy Mode is on, but no later question carries it to Claude or Gemini, nor to the quick decision model or the note written at quit; the same goes for what Orble counted from the screen then (learner.json: an error's label, a button it pointed at). An answer of that time said again (Replay in Recent, "read the last answer again", "keep going") is spoken by the macOS voice or a voice on your Mac, never by ElevenLabs. Words you said while Privacy Mode was on stay on your Mac even when a model on your Mac finishes writing them down after you turned it off: no cloud model answers them. When you said them to Orble (with the wake word) and your chat model runs on your Mac (an Ollama model), the model on your Mac answers them as it would in Privacy Mode, and that answer is kept as Privacy Mode's; otherwise Orble does not answer them, and when you said them to Orble the island says to ask again. No later question carries them, nor does the count of questions you asked in an app then, and their words that appear as you speak (live captions) are never sent to a quick decision model off your Mac, which otherwise judges whether you were talking to Orble over its voice. Turning Privacy Mode on or off cancels a Scribe dictation, a Command Mode instruction and a held Talk key in flight: nothing of them is sent or typed. Attachments you chose yourself are yours to keep: a dropped file or folder, a pasted image and a clipboard chip stay attached, and go with your next question to the cloud model like any attachment, and a link that waited unread is read then. Remove a chip with its ✕ first if it should not go.

Updates

Once a day Orble asks GitHub, where its releases are published, whether there is a newer version: one request that carries nothing about you, though like any request GitHub sees your IP address. A new version downloads in the background and installs when you quit or click Restart now, never while Orble is answering or guiding you. It installs only if it carries Orble's signature. Turn the daily check off in Settings → Updates; Check now still works there. Privacy Mode makes no update check at all, and a copy of Orble you built yourself never checks.

Offline, hotel Wi-Fi and proxies

Orble follows your Mac's proxy settings (System Settings → Network → Proxies: the web proxies, the SOCKS proxy, automatic proxy configuration and its bypass list) for everything it sends to the internet, the connections that carry your voice to AssemblyAI and Orble's voice from ElevenLabs included. With automatic proxy configuration on, macOS fetches the configuration script from where those settings say (often a server on your organisation's network) and Orble asks it which proxy to use for each service, telling it only the service's address, never what you asked. If the script can't be reached or doesn't answer, Orble uses the other proxy settings, or connects directly. A proxy that is itself reached over https:// (set in the HTTPS_PROXY environment variable) can't carry those voice connections, so they don't start there rather than going around it. Requests to Orble's local helpers on your Mac never go through a proxy.

When a request cannot connect, Orble checks once whether you are offline or behind a Wi-Fi login page, by fetching http://captive.apple.com/hotspot-detect.html, the page Apple's own Wi-Fi sign-in check uses. It sends no key and nothing about you, though like any request Apple sees your IP address. It runs only after something failed, or when you ask while Orble thinks you are offline; never on a timer, and never in Privacy Mode. Only that check decides you are offline: a network that blocks one service (a work firewall, say) is not taken for no network. While you are offline or at a login page Orble says so once, stops trying the network instead of timing out, and picks up again when the connection returns.

When you step away

While your Mac is asleep, its screen is locked, or another user has switched in, Orble captures nothing (not even which windows are open), hears nothing, and sends nothing of yours: an answer in progress, a dictation and a guide stop, and the voice goes quiet. The daily update check above can still run then, and carries nothing about you either way. A screenshot that was being taken as you stepped away is thrown out. While only the displays are asleep, capture pauses too, though an answer already speaking finishes. Everything picks up again when you are back.

When Orble stops looking

Orble captures nothing, sends no screenshot and reads no screen text, while:

Each built-in app can be switched off in Settings → Pauses. The island says capture is paused and why. While paused for anything but a meeting app, Orble doesn't tell the model which app is in front either; for a meeting app it names the app but not its window, whose title can carry the meeting's name. Your question, recent conversation and memory still go with what you ask.

What Orble can't see coming: a password manager in a window behind the one you're using, a password manager's browser extension, banking in a browser tab (add your bank's site name in Settings → Pauses to cover it), and screen sharing or recording from any app not named above (a recording you start with ⌘⇧5, Slack, Webex, FaceTime, or someone viewing your Mac remotely). Such a window can be among the screenshots of the last ten minutes that a question about something earlier sends. Orble also takes up to three seconds to notice a share has started.

Meetings and calls

Capture pauses while a meeting app is in front, and resumes when you switch away, even mid-call. On a call Orble stays silent and answers only its wake word, the Talk key held while you speak, or typing, plus, while it is guiding you, the exact phrases "next", "continue" and "stop guide". Nothing it hears goes to AssemblyAI until the call ends: the wake word and what you say with the Talk key held are heard on your Mac (whisper.cpp, Apple dictation, or VoiceStudio on this Mac) when one is installed, and otherwise Orble says once that you can type instead. Other lines are not kept. Orble tells a call from another app using the mic (other than a recording app such as Logic Pro, Voice Memos or Audio Hijack), a Zoom or Google Meet call window, or the camera, and takes a second or two to notice one: speech in that moment can still go out. A recording app alone is not a call: while listening is on, what the mic hears as you record (a meeting in the room, an interview) goes to AssemblyAI as at any other time, unless Privacy Mode is on or you turn listening off.

With Stay quiet in a Focus on (Settings → General, off by default), Do Not Disturb or any Focus you share under System Settings → Focus → Focus status keeps Orble's voice and sounds quiet, and answers stay on screen. macOS asks you first, and tells Orble only that a Focus is on, never which one. Nothing about it leaves your Mac.

On your Mac

The explanation board, its animated diagrams, typeset equations and working, plotted curves, geometry constructions and chess positions included, and the short notes Orble writes on your page beside your own work are drawn on your Mac from the answer: nothing new leaves your Mac for them, and the model's words are never run as a program. An equation is read by Orble's own code from a fixed set of LaTeX commands, never by a renderer that runs what it is given; a curve's formula by Orble's own reader of a fixed set of functions, which computes every point itself; a construction by Orble's own geometry from a fixed set of steps. A note is never written beside a password field or while screen capture is paused for an app it hides, and it goes away with the rest of the drawing. For two minutes after a board's last sentence each question you ask also carries that board, and any notes still on your page, to your chat model so that you can ask for a change: what a chat model wrote earlier in the conversation, never written to disk, and dropped with the turn's other context by Forget this session, a workspace switch, Privacy Mode turned on or off, or choosing a chat model of another provider. If your chat model fails and Orble's automatic fallback answers, that model gets it too, as it gets the rest of the conversation.

In ~/Library/Application Support/orble/:

Outside that folder, Open at login (Settings, or the menu-bar menu; off until you turn it on) writes ~/Library/LaunchAgents/Orble.plist, which only tells macOS to start Orble when you log in. Turn it off and the file is removed.

On-device listening uses a temporary file per phrase, and several for a phrase while words show as you speak (with whisper.cpp, on by default), each normally deleted once transcribed. Quitting clears the conversation, screen history and attachments; Recent answers are the same in-memory conversation, never written to disk unless you keep them (recent.json above). Recent's Export writes the answers it shows to one Markdown file in Downloads, with anything that looks like a key or an e-mail address masked.

Settings → Your data shows all of this. You can see every file above and its size, edit or delete each note about you (or all of them), and Forget this session to clear the conversation, what the microphone heard, the screen history, a held mark and attached files at once. Export writes a new folder to Downloads with a README: your settings, notes, dictionary, saved feedback and the app notes you wrote, and the diagnostics log only if you tick it. It holds no API keys: they are never exported, not even hidden, and anything in your notes or feedback that looks like a key or an e-mail address is masked. Delete everything removes the whole folder above, your keys included, switches off Open at login, and restarts Orble as new. Export conversation (under Help & diagnostics) writes the conversation as a text file to Downloads. Files you export are copies on your disk, outside Orble's folder; Orble won't delete them.

Send feedback (Settings → Help & diagnostics, the menu-bar menu's Send Feedback…, or /feedback in the composer) drafts a report: your words, Orble's version and your macOS, the permissions and which keys are set (never a key), which engines it would listen and speak with and whether the network seemed up, the last 200 lines of the diagnostics log, and your settings without any key. You see every part in full and can edit or empty it first. Orble sends nothing itself: your mail app opens with the report, and it goes only if you press Send there. What does not fit in the mail is put on your clipboard for you to paste.

Permissions

Screen Recording lets Orble see your screen, Microphone hear you, and Accessibility find buttons, read an error's exact text, paste for Scribe and, with pointer tint on, nudge the pointer by a point. Speech Recognition is only for Apple's on-device dictation. Focus is asked for only when you turn on Stay quiet in a Focus, and Notifications only when you turn on Notify me when an answer is out of sight.

Orble never types or clicks for you. The one keystroke it sends is Scribe's paste of your dictation, only after you release or tap its key (with Command Mode on, the same paste carries the change you asked for to the text you selected, only after you release its key, and only if that text is still selected); a dictation longer than five minutes pauses and waits for the key, and the notch shows it waiting until you paste or discard it. It does not record at all when a field macOS marks as a password field has focus as you press the key, and does not type into one. It restores your clipboard after a paste; when it only copies, the dictation stays there. Both are marked so clipboard history apps that follow the common convention leave them out. With pointer tint on (off by default), Orble nudges the pointer by a point and back to refresh its colour.

Planned

A managed service will make keys optional. If you choose it, your AI requests, screenshots included, will pass through Orble's servers; this page will change first. Crash reports will stay off unless you turn them on.