Skip to content
GitIssue

10 issues created with GitIssue

Report a bug

Privacy policy

Last changed on 1 November 2026.

GitIssue keeps as little personal data as possible. This page tells you what it keeps, why, for how long, and which outside services receive data.

What GitIssue keeps

GitIssue does not keep your email address. It does not keep the text that you dictate after the issue is posted; that text is in the GitHub issue, under your name.

What stays on your device

Your draft, recent repos and last device choice are kept in the local storage of your browser. They do not leave your device until you ask for a draft or post. GitIssue uses only two kinds of cookies: the ones that keep you signed in, and one with a random device ID that is used, as a hash, only for rate limits. It does not use cookies for analytics or ads.

Outside services that receive data

ServiceWhat it receivesWhy
GitHubYour sign-in, and the issues and comments that you postSign-in, reading repos, posting
SupabaseThe data in the list aboveSign-in, database and screenshot storage
GroqYour description, device details and short parts of the repo code and docsWriting the draft
Google GeminiThe same as Groq, only when Groq fails. The free tier lets Google use this data to improve its models.Backup for the draft
VercelRequests to the site, and cookieless page views and speed numbersHosting, Web Analytics and Speed Insights

The buttons on the Support GitIssue page open Buy Me a Coffee and GitHub Sponsors. These services receive data only if you choose to go there.

Your choices

Changes

When GitIssue starts to use a new outside service, this page changes in the same update. The history of this page is in the source code (opens in a new tab).