Built with security by default

BlueFairy operates on a minimal-access, minimal-retention principle. Here's exactly how your data is handled.

Read-only GitHub access

BlueFairy connects to your repositories via a GitHub App with read-only permissions — enforced at the API level by GitHub itself. We can read the code, commit history and pull requests of the repositories you select. We cannot write code, create branches, delete repositories, or make any modification to your codebase. Write access is structurally impossible, not just a policy.

GitHub App permissions

✓Read code
✓Read commits
✓Read pull requests
✗Write code
✗Delete repositories

Write access is structurally impossible

Your code doesn't train AI models

Repository context is sent to Google's Gemini API on a paid tier, where Google's terms explicitly prohibit using API data to train models. Google does not use it to improve its products. BlueFairy stores excerpts of code changes alongside the updates they relate to, so your team can ask follow-up questions, and never keeps a full copy of your repositories. Everything is deleted within 30 days of account closure.

Repository context
Gemini API
Response delivered
✓Not used to train models
✓No full copies of your repos

Auth handled by GitHub, not BlueFairy

BlueFairy never stores or handles passwords. Authentication is delegated entirely to GitHub's OAuth system and managed by Supabase. We request only the minimum scope — read:user — granting identity information only. Session tokens are issued by Supabase and transmitted exclusively over HTTPS.

Auth flow

GitHub
→
OAuth
→
BlueFairy
✓No passwords stored by BlueFairy
✓Tokens managed by Supabase
✓Transmitted over HTTPS only
✓Scope: read:user (identity only)

Encrypted storage, GDPR-compliant

All data is encrypted at rest using AES-256 via Supabase and in transit via TLS across all services. BlueFairy operates as a GDPR-compliant data processor under a published Data Processing Agreement. Your data is deleted within 30 days of account closure — we do not archive it. Backups and logs expire on our providers' standard schedules.

AES-256
At restAES-256 · Supabase
In transitTLS / HTTPS
On deletionRemoved ≤ 30 days
ComplianceGDPR · DPA published

Detailed legal documentation

Privacy PolicyData Processing AgreementTerms of Service