Privacy policy

At a glance

MergePulse does not require a MergePulse account. The app uses the GitHub CLI authentication already configured on your Mac and requests pull-request information directly from GitHub. App settings, cached pull-request metadata, and worktrees are stored locally.

Information the app processes

• GitHub account and pull-request data. MergePulse invokes the authenticated GitHub CLI to obtain repositories, pull requests, review status, branch names, and related metadata needed to display your queue.
• Local configuration. Repository selections, filters, appearance, refresh interval, notification preferences, and the project directory you choose are kept on your Mac.
• Local files. When you choose Open in Editor, MergePulse may use git worktree to create a local checkout for the selected pull-request branch and ask macOS to open it in your default IDE.
• Notifications. If enabled, notification state is evaluated locally from fetched pull-request metadata.

Information we collect

MergePulse does not operate an application backend that receives your GitHub token, repository contents, pull-request queue, comments, or source code. We do not sell personal information, use it for targeted advertising, or build advertising profiles.

This website does not provide user accounts or submission forms. Like most hosted websites, its hosting and delivery providers may process routine request information such as an IP address, browser type, requested URL, timestamp, and download status for security, reliability, and delivery.

Third-party services

Your use of GitHub and the GitHub CLI is governed by GitHub’s own terms and privacy policy. This website also loads fonts from Google Fonts, styling code from the Tailwind CDN, and app downloads from Cloudflare R2. Those providers may receive ordinary network request information when your browser connects to them.

Storage, retention, and deletion

Local settings and cached data remain on your Mac until they are replaced, cleared, or the app and its data are removed. Worktrees and their files remain in the project location until you remove them. Information held by GitHub or website infrastructure providers is retained under their respective policies.

Security and your choices

You control the GitHub CLI account and permissions used by MergePulse. You can sign out or change authentication with the GitHub CLI, disable notifications, change selected repositories, and remove local app data or worktrees. No method of storage or transmission is completely secure, but MergePulse limits its data flow by relying on local storage and direct GitHub CLI access.

Children and policy changes

MergePulse is a developer tool and is not directed to children under 13. We may update this policy as the product or its distribution changes. A revised policy will be posted here with a new effective date.

Questions

For privacy questions, use the support contact supplied with your MergePulse download or future store listing. Please do not include credentials, access tokens, source code, or other secrets in a support request.