BountyDeskPrivacy policy
BountyDesk is a demonstration project with no company behind it. This page describes the data it handles as it runs today. It does not sell data, and it shares nothing beyond the services it needs to do its job: GitHub for issues, the model provider that runs the agent, and the email provider that delivers a verdict.
Signing in
Signing in with Google or GitHub goes through Clerk and identifies you as a reviewer. BountyDesk reads your account identity from Clerk and checks it against a reviewer allowlist. It does not see your password.
What the system stores
It keeps the reports it is sent and their evidence, the reporter contact address it needs to deliver a verdict by email, the GitHub account, installation, and repository metadata it receives through the GitHub App, the target configuration it is authorized to touch, the raw inbound webhook and email payloads, processing errors, the verdict and delivery text a reviewer approves, the delivery provider’s response to each attempt, and a step-by-step log of each agent session.
GitHub access
Through the GitHub App, BountyDesk asks for the least access it needs: read access to repository metadata and read and write access to issues, so it can read a report and post an approved verdict back. Two permissions are optional and only used when an owner grants them: read and write access to repository security advisories, to take a report filed as an advisory and write the approved verdict onto it, and read access to contents, so a private repository can be cloned for reproduction. A connected public repository is cloned anonymously. When an installation is suspended or removed, intake and delivery stop.
Mobile notifications
If you turn on notifications in the BountyDesk mobile app, it stores your device’s push token and platform, linked to your reviewer account, and sends it through Expo’s push service. A notification carries only ids and a short title, never verdict text or report content, and BountyDesk keeps a record of each one it sends. Turning notifications off or signing out revokes the token.
Retention
Because this is a demonstration, data is kept for as long as the project runs and is not on a fixed deletion schedule. Some records are deliberately permanent: a verdict, an approval decision, a session event, and a delivery attempt cannot be edited or deleted, so there is an honest, tamper-evident trail of what was decided and sent.
Contact
BountyDesk is developed in the open at github.com/Vaibhav91one/bountydesk. Open an issue there with any question about your data or the project.