Privacy policy
How LockBounty intends to collect, use, and protect account, bounty, repository, and payment-related data.
Last updated: July 4, 2026
1. Data we may collect
- Account details such as name, email, avatar, and GitHub identity.
- Repository, issue, pull request, claim, and review metadata.
- Trust and moderation events needed to prevent abuse.
- Payment provider metadata when payments are enabled.
- Technical data such as logs, device information, and security events.
2. How data is used
Data is used to authenticate users, operate bounties, link claims to pull requests, run AI-assisted review, coordinate payouts, prevent abuse, improve reliability, and comply with legal obligations.
3. Payment data
LockBounty should not store full payment card numbers. Payment processing and payout onboarding are expected to be handled by third-party payment providers such as Stripe Connect when enabled.
4. AI processing
AI review may process bounty descriptions, pull request metadata, diffs, test output, and repository context. Secrets and private data should be minimized before any AI review job is executed.
5. Sharing
LockBounty may share data with service providers needed for authentication, hosting, analytics, payments, email, security, and AI review. LockBounty does not intend to sell personal data.
6. Retention and deletion
Account and operational records are retained as needed to operate the platform, resolve disputes, maintain audit trails, and comply with legal obligations. Users may contact contact@qintaris.app for privacy requests.
7. Security
LockBounty should use access controls, signed webhooks, audit trails, and least-privilege handling of credentials. No system can be guaranteed completely secure.