Privacy policy

Effective August 15, 2026

StackFolder organizes GitHub's native stacked pull requests in your browser. It has no analytics, advertising, developer-operated backend, or remote code.

Information StackFolder handles

• GitHub pull request metadata: Pull request numbers, titles, base branches, draft state, and merge state are fetched directly from GitHub and processed to render folders.
• Optional GitHub token: If you enter a personal access token, it is stored in Chrome's local extension storage and sent only to api.github.com over HTTPS to make requests you initiate.
• Local preferences: Settings, custom folder names and icons, and expanded or collapsed state are stored in Chrome's local extension storage.
• Current GitHub page: StackFolder reads the current repository path and visible pull request links only to identify the rows it should group. It does not collect or retain browsing history.

Storage and retention

Preferences and an optional token remain on your device until you clear extension data or uninstall StackFolder. GitHub API responses are cached in Chrome's session storage and ignored after ten minutes; session storage is cleared when the browser session ends. The developer does not receive or retain this information.

Sharing and sale

StackFolder does not sell data, use it for advertising or creditworthiness, or transfer it to the developer or unrelated third parties. Data is sent only to GitHub when necessary to provide the extension's single purpose.

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Security

Network requests use HTTPS. For private repositories, use a fine-grained GitHub token limited to the repositories you choose with read-only Pull requests permission.

Changes

Material changes to this policy will be published on this page with a new effective date.

Contact

For privacy questions or support, open an issue.