Privacy Policy

ArchGit turns GitHub repositories into architecture maps. This page explains, in plain words, what we keep and why. We don't sell your data, and we don't show ads.

If you use ArchGit as a guest

• You don't need an account. Maps of public repositories may be saved so the next visitor gets them faster.
• To stop abuse, we count how many maps each visitor makes per hour. We store a one-way scrambled code made from your network address, never the address itself, and delete it after a day.

If you sign in with GitHub

• Your GitHub username, name, email address and profile picture, so we can show your account.
• A GitHub access token, stored encrypted, so ArchGit can read the repositories you choose and save notes to them when you ask it to.
• Your projects, their maps, a list of each repository's file names, and the notes you write.

We read your code to draw the map. We don't keep copies of your source files, and we skip files that look like they hold secrets, such as .env files and private keys.

AI keys

If you add your own Claude or OpenAI key, it is kept only in your browser. Your browser sends requests to Anthropic or OpenAI directly, and the key never reaches our servers. Those requests are covered by that company's own privacy policy and are billed to your account with them.

Services we use

• GitHub, to sign you in and read repositories.
• Supabase, to store accounts and maps.
• Vercel, to run the website. Its visitor counts are anonymous and use no cookies.
• Anthropic or OpenAI, only when a detailed map or a question uses AI.

Cookies

We use cookies only to keep you signed in. There are no advertising or tracking cookies.

Deleting your data

You can delete a project at any time, which removes its map and file list. To remove your whole account, contact us and we'll delete it. You can also revoke ArchGit's access in your GitHub settings under Applications.

Changes

If this policy changes, we'll update this page and the date at the top.