Rebusque Labs · Privacy · Support

Privacy Policy

This policy is for the Stalewatch GitHub App, operated by Rebusque Labs LLC, a Nevada limited liability company. Contact: eric@rebusquelabs.com.

It describes the product as of 13 November 2026 and becomes effective on the date this page is first published at rebusquelabs.com.

What the app can access

When you install the app on GitHub, you approve these permissions only:

Repository metadata: read
Pull requests: read
Issues: write (used to create or update one digest issue per repository)

The app does not request access to repository file contents or source code, and it does not read your code.

What we process

On each weekly digest run, the app calls the GitHub API, using an installation token, to:

List the repositories in your installation (up to 5 on the free plan)
Read open pull request metadata: number, title, last-updated time, draft status, and the usernames of requested reviewers
Find an existing open issue titled “Stale PR digest” with the label stale-pr-digest, or create that issue
Write the digest (pull request numbers, titles, days idle, and reviewer usernames) into that issue in your repository

GitHub also delivers webhooks to our HTTPS endpoint. We verify each delivery with the X-Hub-Signature-256 signature. We use:

Installation events, to know when the app is installed, uninstalled, or has repositories added or removed
Marketplace purchase events, if you use a GitHub Marketplace plan: account id and login, plan name, billing cycle, action, and effective date

The current free-tier build is stateless. It has no database. Digest content lives in the GitHub issue in your repository, which you control. While handling a request we may write short operational logs (for example, event type, action, installation account login, and plan name). We do not sell this information, share it with advertisers, or use your repository data to train AI or machine-learning models.

The free plan does not send email or Slack messages. Paid plans described in the code are not offered until GitHub’s published install threshold is met; we will update this page before collecting any additional data for a paid plan.

How long we keep data

API responses and webhook bodies are processed in memory to complete the request. Operational logs may be kept on the host for debugging and security. Uninstalling the app on GitHub ends our API access. The digest issue stays in your repository until you delete it. Email eric@rebusquelabs.com if you want us to delete operational logs we hold; we will delete what we reasonably can, except records we must keep for law or security.

Changes

We will post changes on this page with a new effective date.

Governing law

This policy is governed by the laws of the State of Nevada, United States.

Contact: eric@rebusquelabs.com