Legal
Privacy Policy
Effective
SweepLoom runs on your computer and sends nothing to us. This website has no analytics, sets no cookies and loads nothing from third parties.
The short version
- No account, no telemetry. SweepLoom does not collect analytics, crash reports or usage data, and does not check for updates over the network.
- The CLI and MCP server make no network requests. Their dependency tree carries no HTTP client.
- The desktop app's only network use is a local Ollama server at
127.0.0.1:11434, if one is running, to list and remove models. - The Mac App Store edition (coming soon) collects no data and makes no network connections at all. Apple handles its purchases under Apple's own privacy policy.
- This website is a static site with no analytics, no cookies, no trackers and self-hosted fonts.
The SweepLoom software
This covers the sweeploom CLI, the MCP server, the Rust library, the desktop app (including its Mac App Store edition), the Codex plugin and the browser companion extension. They are built by Sergii Ziborov at Weavatrix (“we”), and none of them sends data to us. We operate no server they talk to.
What it reads on your computer
SweepLoom works mostly from metadata:
- Files and folders: names, sizes (allocated blocks), file counts and timestamps, in the folders you scan and in known developer, cache and AI tool locations.
- Processes: names, IDs and start times, parent relationships, CPU and memory use, working directories, and, where the operating system exposes it, network connection state. Command-line arguments are redacted (for example
--tokenvalues and credentials in URLs) before they are shown or stored. - Projects: project kinds and Git status, to tell live source from rebuildable output.
- AI tool folders: classified by file name only. SweepLoom does not open secret files such as
.credentials.jsonor SQLite databases. - Local tools you already use: cleanup in the desktop app can query and run
docker,xcrun simctl,rustupand the local Ollama API. Those tools follow their own behavior and terms. The Mac App Store edition runs none of them.
What it stores, and where
Settings, scan history, the last browser companion snapshot and the Later shelf of saved tab titles and URLs are stored in SweepLoom's local config and data directories on your computer. Nothing is uploaded. You can delete them at any time.
Browser companion
The optional extension exchanges messages only with a local SweepLoom process through the browser's native messaging channel. It makes no network requests. Per tab it reports the tab and window id, title, URL with the query string, fragment and user info removed, lastAccessed, and the pinned, audible, discarded and incognito flags. Details: docs/BROWSER.md.
When you connect an AI agent
This is the one path by which SweepLoom output can leave your machine, and it is the agent's, not ours. When an MCP host or Codex calls SweepLoom's tools, the results (paths, sizes, process and project details) enter that agent's context and may be sent to the agent's model provider under that provider's terms. Choose what you ask your agent to inspect accordingly.
Building from source
Installing SweepLoom uses Git and Cargo, which download source from GitHub and dependencies from crates.io under those services' own policies. That happens at install time, not when SweepLoom runs.
Mac App Store edition
The desktop app also has a sandboxed Mac App Store edition. It is coming to the Mac App Store and is being tested through Apple's TestFlight; it is not on sale yet.
- The app collects no data. It has no analytics, makes no network connections, starts no other programs and sends nothing to us.
- It reads only folders you grant. It runs in the macOS App Sandbox and works only inside folders you choose in the macOS folder picker. Each grant is remembered as a security-scoped bookmark in the app's own container, together with its settings and scan history. You can remove a grant in Settings at any time.
- Apple handles the purchase. Buying and downloading the app is processed by Apple under Apple's privacy policy. We do not receive your payment details or other personal data from Apple. Apple gives developers aggregate reports in App Store Connect, such as sales and download totals and app analytics, which do not identify you.
- Apple's own diagnostics. If you choose to share analytics with app developers in macOS, Apple may pass on crash reports for the app. If you test it through TestFlight, Apple may share the details you were invited with and any feedback you send. Both follow Apple's settings and terms; SweepLoom itself collects neither.
This website
- No analytics, no trackers, no cookies. There is no analytics script, pixel, or third-party embed on any page.
- Fonts are self-hosted. They are bundled at build time and served from this domain, so loading a page makes no request to a font provider.
- Your theme choice (auto, light or dark) is saved in your browser's local storage under
sweeploom-theme. It never leaves your browser, and you can clear it with your site data. - Hosting. The site is served as static files by nginx on our own server at Hetzner in Germany. Access logging is turned off for this site, so visits are not recorded; the server keeps only error logs needed to keep it running. DNS for the domain is provided by Cloudflare.
- Links. Links to GitHub and other sites take you to services with their own policies.
Children
SweepLoom is a developer tool, and this website does not knowingly collect information from anyone, including children.
Changes
If this policy changes, the effective date above changes with it, and the history is kept in the repository. The privacy section of the Terms of Use (from TERMS.md) says the same thing in fewer words.
Contact
Questions go through GitHub issues. For a security problem, open an issue that asks for a private contact and leave out exploit details and secrets.