Privacy

Your history stays on your computer.

Seggo runs only on your computer. There's no account, and it shows its pages fromhttp://127.0.0.1, in the Mac app's own window or your browser. Nothing is uploaded.

  • No accountNothing to sign up for.
  • No uploadHistory and handoffs stay on your computer.
  • Read-onlyYour tools' history is read, never changed.
  • Off by defaultThe only internet request is an update check you turn on.

Where your data lives

Seggo keeps everything in its own folders on your computer. You don't need administrator rights, and nothing is stored anywhere else.

macOSWindows
Data (history index, handoffs, project context)Mac app: ~/Library/Application Support/Seggo/
Terminal install: ~/.local/share/seggo/ (the app uses this too if it already exists)		%LOCALAPPDATA%\Seggo\
Settings (optional)~/.config/seggo/config.toml%APPDATA%\Seggo\config.toml
ProgramMac app: /Applications/Seggo.app
Terminal install: ~/.local/bin/seggo		%LOCALAPPDATA%\Programs\Seggo\seggo.exe
LogMac app: ~/Library/Logs/Seggo/
Terminal install: in the data folder above		In the data folder above
Start at login (only if you turn it on)~/Library/LaunchAgents/com.seggo.watch.plistA Seggo value under HKCU\Software\Microsoft\Windows\CurrentVersion\Run

seggo doctor prints these paths for your computer. When you uninstall, Seggo shows where its data folder is and asks before deleting it.

What Seggo reads and writes

Reads, never changes

  • Each tool's own history on your computer, for example ~/.claude/projects, ~/.codex/sessions and Cursor's chat database.
  • Files are opened read-only. Cursor's database is read in place and never copied.
  • Your original transcripts stay where they are. Seggo keeps a masked copy of their text in its own index.

Writes

  • Always: only its own data folder.
  • Only when you turn a tool on and confirm the preview: a seggo entry in that tool's settings, a marked Seggo section in a project's rules file (such as CLAUDE.md or AGENTS.md), and for Claude Code a session-end hook.
  • Nothing else. Every change is shown first, recorded, and undone by switching the tool off.

More detail for each tool is in Connect your tools.

What Seggo never does

  • Upload anything. There's no account and no server of ours. Your history and handoffs are never sent anywhere.
  • Listen beyond your computer. Seggo's pages are served only on 127.0.0.1. It refuses any other address, and its pages load nothing from the internet.
  • Change a tool's files without a preview. Every change to a tool's settings or a project's rules file is shown first and written only after you confirm.
  • Start tools on its own. Seggo opens a tool only when you click Open, after you've allowed it once, and shows exactly what will run first. That setting is off by default.
  • Download or install updates itself. Even with the update check on, you download and install new versions yourself.

Secret masking

Seggo masks secrets, such as API keys and tokens, before anything is saved to its index or exported. It's on by default.

Masking is best-effort, not perfect.

Seggo's tests prove that the secret patterns it knows about are caught. They can't prove that every secret a person might paste is caught. A secret in an unusual format may slip through.

  • File paths, commands and problem descriptions are kept, because they're what makes a handoff useful.
  • Git commit IDs and ordinary text aren't treated as secrets.
  • So treat Seggo's data folder as sensitive, the same way you'd treat your tools' own history.

The one internet request

Seggo can tell you when a newer version is out. This is the only request it ever makes to another computer, and it makes none unless you turn it on.

  • It's off until you switch on Check for new versions in Workspace settings > Updates.
  • When on, while Seggo is open it asks GitHub at most once a day which version is newest, and also when you press Check now.
  • It's a plain web request with a short timeout. It sends no cookies, no account, and nothing about you or your work.
  • If there's a newer version, Seggo shows a banner. It never downloads or installs anything itself.

Details are in Update Seggo.

What Seggo changed and Undo

Every change Seggo makes to your setup is listed in one place, each with Undo.

  • Turning a tool on, and letting Seggo open tools for you, are both recorded under What Seggo changed.
  • Seggo's additions sit inside a marked Seggo section, so they're easy to spot and remove.
  • Turning a tool off puts back any file you haven't touched since, exactly as it was. If you've changed a file since, your newer work stays and only Seggo's part is removed.
  • If any file can't be written, every file already changed is put back.

Send feedback

Send feedback builds a short report for bug reports. You read it first, then choose what to do with it. Nothing is uploaded or sent automatically.

Included

  • Your Seggo version.
  • Your operating system.
  • The same status check and paths as seggo doctor.
  • An optional quick tag and anything you type in the box, if you choose to.

Left out

  • Your threads, handoffs and project context.
  • Your prompts, files and project names.
  • Your home folder (shown as ~, or %USERPROFILE% on Windows) and your user name.
  • Copy report copies it, so you can paste it into an email or message you write yourself.
  • Save report… saves it as a text file you can attach. In the Mac app it goes to your Downloads folder.
  • Email feedback opens a draft to contact@bozomalabs.com in your own email app with the report prefilled, so you only send it if you choose to.

From a terminal, seggo feedback prints the same report. See Troubleshooting and feedback.

Your AI tools have their own privacy

Seggo stays on your computer, but the AI tools you connect it to are separate products. When a tool reads a handoff or project context through Seggo, that tool sends it to its own model, as it does with anything else in your session. Check each tool's own privacy terms for what happens there.