Privacy

Remige is local-first. There is no account, no app telemetry, and no background daemon.

Effective 2026-10-19

What Remige stores

• ~/.config/remige/config.json — only if you create custom tools or source settings.
• ~/Library/Caches/app.remige — the last scan snapshot, release notes, and HTTP responses used to avoid repeated network calls.
• app.remige — standard macOS preferences for window and app settings.

The cache contains package names, versions, release notes, and URLs fetched from update sources. It is not uploaded anywhere. You can remove it with remige cache clear.

Network requests

Remige contacts only the services needed to build the update list:

• Homebrew, the npm registry, and your configured pnpm/Bun registries;
• GitHub release pages, the GitHub API, and release Atom feeds;
• the SUFeedURL appcasts of installed apps;
• the Mac App Store through mas when it is installed;
• https://remige.app/latest.json and GitHub Releases for Remige’s own updates;
• any latestURL you declare in your own custom-tool or app configuration.

These requests necessarily expose your IP address and user agent to those services, under their own privacy policies. Remige does not add accounts, identifiers, or analytics parameters to them.

Website

remige.app is a static site hosted on Vercel. It sets no cookies, runs no analytics or advertising scripts, and embeds no third-party content. Vercel processes standard request logs (IP address, user agent, path, timestamp) to serve the site and protect it from abuse.

Update checks

Checking for a Remige update downloads the public latest.json feed and, when a newer version exists, the release asset. No machine identifier is sent. The app verifies the asset’s SHA-256 and size before installing it.

Changes and contact

Material changes to this policy will be recorded in the changelog and on this page. Questions or corrections: open an issue in GitHub Issues.