Privacy Policy

1. GitHub OAuth Authentication

CodeForge AI uses GitHub OAuth to verify user identities and establish secure sessions. We request read-only permissions for your public user profile and repositories list. Your credentials and auth tokens are handled directly by Supabase Auth and are never exposed to or stored by our own application logs in plaintext.

2. Repository Analysis & Code Ingestion

When you submit a repository URL for indexing, CodeForge clones the files main branch into a temporary workspace. Our scanner walks the directory, parses dependencies, abstracts circular symbol references, and computes vector representations (768 dimensions) using Google Gemini embedding APIs.

We do not retain raw source code files in permanent storage. All temporary directories are fully deleted as soon as code chunks are vectorized and secure analysis reports are compiled.

3. Data Storage & Security

All parsed metadata (file structures, class signatures, security warning cards, circular reference locations, and chat session histories) is stored securely in our Supabase PostgreSQL database. Access to these tables is governed by strict PostgreSQL Row Level Security (RLS) policies, ensuring that only you (the authenticated GitHub user) can read or modify your scanned data.

4. User Deletion Rights

You retain absolute ownership and control over your repository statistics. Clicking the Delete Repository button in the dashboard executes a cascading deletion query inside PostgreSQL. This permanently wipes out all associated scans history, file indices, pgvector chunk embeddings, and chat thread messages instantly.