BuildGist

Privacy

Effective October 6, 2026.

Who we are

BuildGist is provided by Kayvan Andre Zahiri, an individual in San Francisco, California, United States ("BuildGist", "we" or "us"). He is responsible for the personal data this page describes: he decides why and how it is used. For legal and privacy questions and requests, email kayvanandre@gmail.com.

What BuildGist collects

In BuildGist for Mac, What BuildGist can send shows exactly what is sent, including what is sent to write explanations. To leave a project out entirely, pause it there: nothing in it is recorded, sent or explained. Disconnect this Mac stops all sending.

How explanations are made

BuildGist writes each explanation with an AI model from Anthropic, which BuildGist pays for. You don't need an account with Anthropic or any other AI provider.

To explain a run, your computer sends BuildGist what that run needs, and BuildGist passes it to Anthropic:

BuildGist does not send your whole repository or files the run did not change, and never sends files named like secrets, such as .env files and keys. Your computer masks secrets in all of it before it leaves.

BuildGist does not keep this material. It is used to write the explanation and then discarded, and it is not kept in BuildGist's database, logs or backups. BuildGist keeps only what is listed under Your runs.

Anthropic processes it for BuildGist under its commercial terms. It does not use it to train its models, and it deletes it within 30 days. The exceptions: it may keep content it flags as breaking its usage policies for up to 2 years, and it keeps what the law requires it to keep.

What BuildGist does not collect

How BuildGist uses your data

When you connect a Mac, BuildGist for Mac asks before it sends anything. That is your choice of whether your Mac sends your runs to BuildGist to be kept and explained. You can stop it at any time: choose Disconnect this Mac, or pause a project to leave it out.

Who else receives data

BuildGist does not sell your data or share it with anyone other than those listed above.

Where your data is processed

BuildGist is offered to people in the United States. It is run from the United States, and what it collects is stored and processed there: by BuildGist, by Fly.io, which hosts BuildGist's servers there, and by Anthropic, which writes explanations for BuildGist. Fly.io and Anthropic may also process it in other countries where they operate. GitHub, Stripe and Link handle what they receive under their own privacy policies.

How long it is kept, and deleting it

What BuildGist collects is kept until you delete your account, apart from what is listed here; none of the rest is deleted automatically.

Settings → Download my BuildGist data gives you your account, including the word for where you heard about BuildGist when your account has one, your computers, your sign-ins, your activity, your billing status, the record of each explanation made for your account and every synced run, as JSON.

Settings → Delete my account immediately deletes your account, including the word for where you heard about BuildGist, every synced project, run, explanation and task, the record of each explanation made for your account, your read history and activity, your BuildGist Pro records, your connected computers and every sign-in. One thing is kept until shortly after the next day begins (00:00 UTC): what your explanations have cost that day, under a keyed hash of your GitHub user ID, so deleting your account and creating it again does not reset the daily limit on explanations. A BuildGist Pro subscription is canceled at once, first; if Stripe cannot cancel it, your account is not deleted. Stripe and Link keep their own payment records, under their privacy policies. Nothing on your computer is deleted, and your computers stop syncing.

Your choices

For anything not in that copy, such as server logs or the waitlist, to have something corrected or removed, for anything else, or if you would rather ask, email kayvanandre@gmail.com. BuildGist may first ask you to confirm the account is yours.

Known limits

Secret masking is best-effort: it catches common credential shapes, not every secret. A secret in an unusual shape, in code a run changed, could be sent to BuildGist and Anthropic, and could appear in a cited excerpt. If that matters for a project, check What BuildGist can send, or pause the project.

Changes to this policy

If we change this policy, we will post the new version here with its effective date and, for changes that matter, tell you in BuildGist before they take effect.

Contact

Questions, requests, and privacy and legal requests: kayvanandre@gmail.com.