Orbit Logo
Orbit
← Back to home
Orbit Logo

Privacy Policy

Last updated: September 27, 2026 · Policy owner: Saadaan Hassan

Orbit captures activity on your Mac to build a searchable memory of your work. All capture stays local by default. AI features are entirely optional and only reach the cloud if you configure your own API key — this page explains exactly what happens in both cases, with no simplifications that stop being true once you look closely.

This page was drafted with AI assistance from Orbit's own source code, not from marketing copy. It is not legal advice, and has not yet had a professional legal review — treat it as an accurate technical description of current behavior, not a binding legal document.

1. What Orbit Captures

Nothing below is captured until you complete Orbit's first-launch consent screen, which asks about each category independently — there is no single “accept all” that turns on more than you chose. Orbit captures, only for categories you've enabled:

  • Active app and window title. Which application is in focus and what its window is titled, captured on a short poll interval.
  • On-screen text. The readable text visible in your active app's interface, accessed via macOS's built-in Accessibility API. This requires the Accessibility permission you grant during setup. Password fields are never read. They are identified and skipped before any text is accessed, at every level of the interface — unconditionally, this is not a setting.
  • Browser URL and page title. The URL and title of your active browser tab. Captured natively from Chrome, Safari, Arc, Brave, and Edge using macOS Automation, and optionally via the Orbit Chrome extension for richer context like article text, search queries, and link clicks.
  • Clipboard text. Text you copy. Recognizable secrets (API key formats, private keys, credit card and SSN patterns, crypto addresses) are detected and replaced with [REDACTED:type] before anything is written to disk — see Section 5 for the limits of this.
  • File activity. When files are created, modified, or removed in folders you choose to watch (Documents, Desktop, and Downloads by default; you can add or remove folders). Only the file path and the action are recorded. File contents are never read, by this feature or any other part of Orbit.
  • App launches and quits. Which applications you open and close, to help Orbit understand the shape of your work sessions.
  • System events. When your screen locks or unlocks, and when your Mac sleeps or wakes. Used to mark session boundaries — Orbit never starts a new “session” mid-lock.

Orbit does NOT capture, under any setting:

  • File contents (only file paths and the action taken)
  • Anything from apps excluded by default — 1Password, Bitwarden, Keychain Access, LastPass, Dashlane, System Preferences/Settings, and Orbit itself — or any app or website you add to your own exclusion list
  • Text typed into a password field or secure text input, in any application (skipped unconditionally by the Accessibility reader, before any text is read)
  • Keystrokes, key codes, or mouse coordinates — idle detection uses only a timer (seconds since last input), never what was typed or clicked
  • Screenshots or video of your screen, or audio/microphone input (none of this exists in the current app — these would be future, separately-announced features, not silent additions)
  • Network traffic, DNS queries, or HTTP request/response bodies

2. What Orbit Cannot See

For absolute clarity, Orbit cannot:

  • Read the contents of arbitrary files on your disk
  • Access your email or messaging accounts directly
  • Access saved passwords in your browser or keychain
  • Read messages from end-to-end encrypted services, unless their on-screen text happens to be visible in a window you have Orbit watching
  • Turn on your microphone or camera
  • Read text in apps that are not the currently focused, foreground application

3. Storage, Retention, and Encryption

All captured activity is stored locally on your Mac at ~/.orbit/ in a SQLite database, plus a local vector index if you've configured semantic search (Section 4). This data never leaves your device unless you configure your own AI provider key — see Section 4 for exactly what that sends and when. There is no cloud sync feature today.

Raw activity events are retained for 90 days on a rolling basis. AI-written session summaries are kept until you delete them or wipe your data — see Section 6 for what deleting a session does and does not remove.

Local data is not encrypted by Orbit itself beyond restrictive file permissions (readable only by your macOS user account). We recommend enabling FileVault, macOS's built-in full-disk encryption, for protection if your Mac is lost or stolen — Orbit does not do this for you and does not claim application-level encryption of its own.

4. Cloud AI Is Fully Optional

Orbit has no AI features funded by the maintainer. There is no shared key, no free tier, and no maintainer-run AI backend of any kind. Without your own key, Orbit is fully usable via local keyword search — no network request happens for AI purposes at all.

If you add your own key (Privacy tab in the app), two independent providers are involved, only for the feature each one powers:

  • Groq — chat-style recall, session summaries, and event classification. With your key configured, requests go directly from your Mac to Groq's API — never through any server the maintainer runs. Per Groq's own published policy, inference requests are not retained by default, and a temporary log kept only for abuse/reliability troubleshooting is deleted within 30 days; Groq offers a Zero Data Retention setting on your own account for an even stricter guarantee. Orbit does not control this — check Groq's own data policy directly.
  • Voyage AI — semantic (“search by meaning”) recall only. With your key configured, requests go directly from your Mac to Voyage's API — never through any server the maintainer runs, and no maintainer infrastructure of any kind sits in between. Unlike Groq, Voyage's default is to store and use your data for model training unless you opt out on your own Voyage account — see Voyage's FAQ for how to opt out. Orbit cannot change this setting on your behalf; it lives entirely on your Voyage account.

What either provider receives, only when its key is active: short AI-written session summaries, on-screen text/clipboard snippets already redacted per Section 1, your recall questions, and up to your last 4 conversation turns for context. Every field passes through the same redaction patterns as local storage a second time, immediately before the request leaves your device — this is defense in depth, not a replacement for capture-time redaction, and neither layer can guarantee no unusual secret format ever slips through.

Orbit never sends raw clipboard content, file contents, or the redacted secret values themselves — those don't exist past the capture-time redaction step.

5. Limits of Automatic Redaction

Secret detection is pattern-based and best-effort, not a guarantee. It recognizes common formats (API key prefixes, private key blocks, JWTs, card/SSN-shaped numbers, crypto addresses) but cannot catch every secret in every format, especially unusual internal formats. Treat this as a safety net, not a reason to freely copy or expose credentials while Orbit is running. You can exclude any app (password managers already are, by default) or any website from capture entirely.

6. Your Controls, and What Delete Actually Does

  • Pause all capture at any time from the menu bar
  • Change or withdraw your consent for any capture category independently, at any time — not just at first launch
  • Exclude specific apps or websites from being tracked
  • Turn off on-screen text capture or file activity monitoring independently
  • Choose which folders are watched for file activity
  • Remove your own AI provider key at any time; capture and local search keep working exactly as before
  • View everything Orbit has stored in the Memory Viewer
  • Delete individual events or sessions, or wipe everything at once

Deleting a raw event (a single clipboard entry, window title, browser visit, etc.) permanently removes that row — this is irreversible.

Deleting a session removes its AI-written summary and its semantic-search entry, but the individual raw events that fed into it are not deleted — they're only unlinked from that summary. Because unprocessed events are exactly what the next automatic summary cycle looks for, those same events may be summarized into a new session again later. If you want an activity permanently gone, delete the underlying events too, or use the full wipe below.

A full memory wipe (one click in the Privacy tab) deletes all events, sessions, the local search index, the semantic-search index, and paired browser-extension connections, and securely compacts the database file. This cannot be undone.

7. No Telemetry

Orbit sends no telemetry, analytics, or crash reports of any kind, to anyone, ever — not even anonymized, not even a count of app launches. No stable device identifier is created. This has been true since the app removed its analytics and crash reporting SDKs entirely, rather than disabling them by default — there is no setting that turns telemetry back on, because there is no code path left that could send it.

8. If You Capture Someone Else's Content

Orbit captures whatever is on your own screen — which may include an employer's, client's, or colleague's material if it appears in a window, document, or message you have open. You are responsible for getting any permission your workplace, contracts, or applicable law require before running Orbit in contexts involving other people's confidential or personal information. When in doubt, exclude the relevant app or pause capture for that work.

9. Updates to This Policy

If this policy changes, this page will be updated to keep matching actual behavior — there are no separate release notes to check; Orbit has no packaged release process, so the project's Git history is the record of what changed and when. The date at the top of this page reflects the most recent revision.

10. Contact

Questions about privacy, or to report a security issue? Email: saadaanedu@gmail.com. This project is not actively maintained, so there's no guarantee of a response — but privacy and security reports sent here are still the right way to reach the policy owner if one is possible.