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
- Your runs: what you asked your coding agent, which files each run changed and by how many lines, the test commands your coding agent ran during it and what each reported (not their output), the short IDs and messages of commits made during it, the project's folder name and branch, and your Current task's instructions if one is open. For explained runs, also the explanation and short cited excerpts of changed code (at most 12 lines each), and, for each explanation, when it was made, whether it succeeded and how much processing it used. For each explanation shown in your coding agent, when it was first shown there and how many times. When you use Continue, which agents it was between, and when. Your computer masks secrets in all of this before sending it. What your computer sends to write an explanation is not kept (see How explanations are made).
- Your account: your GitHub user ID, username and display name, when you agreed to the Terms, with the date they took effect, and one word for where you heard about BuildGist, kept only if you choose it or a link to BuildGist names it. A cookie, your IP address, or the address of a page that linked here is not used to choose that word.
- Your computers: each one's name (its short host name), when it connected and last synced, its BuildGist version, which supported coding agents it has set up and how far each setup got, whether BuildGist for Mac set it up, how many folders BuildGist could not record (a number, never a name or path), and when each setup step happened, to measure how long setup takes. Nothing about your projects or files.
- Your sign-ins: for each browser you sign in with, a one-way hash of its sign-in cookie and a label such as "Safari on macOS" so you can recognize it.
- BuildGist Pro: when your free trial started and the Stripe checkouts you started, with when each started and completed; if you subscribe, also your Stripe customer and subscription identifiers and your subscription's status and dates.
- Product activity: which days you signed in or opened the Inbox or the setup
page, which explanations you opened, whether you downloaded BuildGist for Mac, how far you got in
setting up, how you connected each computer, and your steps with BuildGist
Pro, such as starting a trial or subscribing. Downloads
of BuildGist for Mac are also counted as one anonymous number per day. We count downloads by the
site that linked to us (for example, Hacker News), as a daily number with nothing about you.
Visits to the home page are counted the same way. When an account has the word, the counts of
accounts that open an explanation, are in a trial, or pay are counts of accounts, not of visits,
and they have no address. Visits and downloads are also counted by the kind of device (a Mac,
another computer, or a phone or tablet), read from the browser's description of itself, which
is not kept. A download asked for from a computer or phone that is not a Mac shows a page
saying what BuildGist runs on instead, and that page is counted the same way, by day and
kind of device, as is asking it to email you the link. When you choose Download for Mac, the
short "what to do next" panel that appears under the button is counted the same way, and so is
whether the download reached your computer whole and, for one that stopped partway, roughly
how far it got (under a tenth, between a tenth and nine tenths, or more), the hour (UTC) it
stopped, and whether a page of this site sent your browser there (read from the Referer, which
is not kept). The page that says how to open BuildGist is counted the same way, and so
is whether its Download button was used; on a Mac, that count also notes whether the
browser said its chip is Apple or Intel (only Chrome and similar browsers say). Views of the sign-in page and clicks of
Continue with GitHub are counted the
same way as anonymous daily numbers (and forwarded to PostHog with the linking site's word and
device kind). The Mac app may send one-time anonymous notes as it is set up: that it was
opened, that a filled-in sample was on screen the first time it opened, that you asked to
see that sample's explanation, that its sign-in screen was shown, that it copied itself to
Applications, that you chose Sign in, that your browser handed the connection back, and that
no supported coding agent was found, each with a random install id; the first one also says
whether the Mac
has an Apple or Intel chip and its macOS version number, and nothing else about you or your Mac,
unless you turn that off in this Mac's machine config (
cloud.anonymous_setup). This is used to learn whether BuildGist is useful and easy to set up. To leave your browser out of these counts of visits and downloads, open /count-me-out in it: that page sets a cookie that is used for nothing else. Our server forwards these same facts to PostHog, our analytics provider, to see where setup stops: anonymous visits and downloads (with the linking site's word and device kind, nothing that links two of them), and your account's steps above under a one-way pseudonym of your account ID. Never your name, email, GitHub details, IP address, prompts, code or file paths, and no cookie or script from PostHog runs in your browser. Leaving yourself out with /count-me-out leaves your visits and downloads out of this too. - Server logs: the requests made to BuildGist, with your account ID and in some cases your IP address. Never your prompts or code.
- The waitlist: if you joined it, the email address and coding agent you gave, used only to tell you about BuildGist. Email kayvanandre@gmail.com to have it removed.
- Save my email: if you leave an address on the download page from a computer or phone that is not a Mac, the email address you give, the word for the site that linked you and when you asked. We email you the Mac link once, from kay@mail.grokbot.com. Nothing else is sent to it, it is not an account and it is not added to any list. It is deleted within 30 days, or sooner if you email kayvanandre@gmail.com.
- Email me the 2-minute setup and one tip: if you leave an address in this optional field on the page shown after you download BuildGist for Mac, the email address you give, the word for the site that linked you, when you asked, and when we emailed you. We email you the setup and one tip once, from kay@mail.grokbot.com, and one short note the next day asking how it went. To keep scripts from filling in strangers' addresses, the page carries a short-lived signed code for its own visit, and we keep an address only when that visit was a browser that started the download a few seconds to 30 minutes earlier and the hidden "leave this empty" field is empty; phone text-message gateway addresses are not kept. We check this when you submit and keep no link to the visit, your IP address or your browser. Refused submissions are only counted, with the reason. Nothing else is sent to your address, it is not an account, it is not added to any list and it is not sent to PostHog. It is deleted within 30 days, or sooner if you reply "stop" or email kayvanandre@gmail.com.
- Try it in your browser (/try, and on the page after you download): what you paste is masked for keys and tokens in your browser and again on our server, sent once to our AI provider (Anthropic) to write the explanation, and then dropped. The same paste box and sample are on the page shown after you download BuildGist for Mac (/download/next). The handoff for your next agent is built on our server from the same masked paste and that explanation, with no further AI call, and is masked again before it is shown. BuildGist keeps neither the paste, the explanation nor the handoff; a finished explanation and its handoff wait in memory for at most 10 minutes until your page picks them up. A first-party cookie with a random ID (no name, address or IP) lets the page allow 3 runs a day; we keep only a daily count per keyed ID, deleted the next day. "Try a sample run + handoff" shows a built-in session and an explanation written for it ahead of time: nothing is sent to the AI provider, and it does not use a run. A handoff you copy is copied in your browser; we only count that a copy happened. We count a view when the page is shown in a browser (a small request after it is visible), and every request as a raw total. We also count sample views, runs, explanations, failures, handoff copies and clicks to the Mac download as daily totals, without IP addresses or browser details. Views, runs, explanations, failures, and a click on Download for Mac from the step shown after an explanation are also counted split by whether the browser says it is on a Mac or not (read from the browser's user agent, which is not kept). A file you choose or drop is read in your browser into the same box and handled as a paste. A browser left out with /count-me-out is in none of these split counts. If you leave an email for more runs, it is kept and used as in "Email me the 2-minute setup" below.
- A public pull request or commit link (buildgist.com/owner/repo/pull/n or /commit/sha): BuildGist fetches the public .diff from github.com and, when GitHub publishes them, the title, body and commit messages from GitHub's public API, then checks what was claimed against the diff and may explain the change the same way as /try, under the same daily spend cap. Nothing is kept except a cached copy of the public result (so a repeat view of the same URL and diff costs nothing) for up to 14 days, and daily counts (views, runs, explanations and refusals), without IP addresses or browser details. A view is counted when the page is shown in a browser (a small request after it is visible), and every request as a raw total. A crawler or a link preview does not start an explanation. Private repositories and addresses GitHub does not have return a short error; BuildGist does not send any GitHub credentials, so it cannot see a private repository. The visitor's free /try is not used.
- BuildGist in the Claude apps (the connector at /mcp): if you add BuildGist as a connector in one of the Claude apps (claude.ai, Claude Desktop or Claude Code), the app sends us the diff, git log or agent session chosen for that call. It is masked for keys and tokens on our server and, for an explanation, sent once to our AI provider (Anthropic); the handoff and the built-in sample use no AI call. BuildGist keeps neither what was sent nor what it returned: both are dropped when the answer goes back. The connector has no sign-in and sets no cookie, and we do not read your other Claude chats, memory or files. We count connects, calls of each kind, failures and the day's AI spend as daily totals, with a one-word name of the Claude app that connected (as the app reports it), without IP addresses; an IP address is used in memory only, to limit how often one address may call.
- The Claude Code check (/hook): if you install the one-line check, it sends BuildGist the diff of files changed since the session started, or the uncommitted changes when that start was not recorded, and, when it is short, the last thing you asked. Files named like secrets, such as .env files and private keys, are left out on your computer before anything is sent, and keys and tokens still in the diff are masked there and again on our server. An explanation is sent once to our AI provider (Anthropic) and then dropped. BuildGist keeps neither the diff nor the explanation nor the handoff. The check has no sign-in and sets no cookie. We count installs, runs, explanations and refusals as daily totals, without IP addresses; an IP address is used in memory only, to limit how often one address may call. A check we run ourselves is counted with the others and again under an internal mark, so it can be taken out of the totals. Set BUILDGIST_DISABLE=1, or leave a file named disabled beside the check, and nothing is sent. You can remove the check with the one-line uninstall.
- Tell me when the plugin is ready: if you leave an address for the planned plugin for Claude Code, Codex and Cursor, the email address you give, the word for the site that linked you and when. We email you once, when the plugin ships. Nothing else is sent to it, it is not an account, it is not added to any list and it is not sent to PostHog. It is deleted within 90 days, or sooner if you email kayvanandre@gmail.com.
- What would make this worth opening, or paying for: if you answer this optional one-line question under Did BuildGist open? on the page shown after you download BuildGist for Mac, the words you write, the word for the site that linked you and when. It is not linked to an account, a visit or a download, is not sent to PostHog, and is read only by us, to decide what to build next. It is deleted within 90 days, or sooner if you email kayvanandre@gmail.com. The same page has the Try it in your browser paste box and sample; what is kept when you use them is described under Try it in your browser above.
- Did BuildGist open?: if you tap Yes, it opened, or one of the Didn't open? choices on the page shown after you download BuildGist for Mac (Nothing happened, macOS blocked it, Couldn't find it, Something else), one is added to a daily count for that choice, and to a daily count of answers on that page (yes, no, or a written answer). Nothing else is kept: no text, email address, cookie, IP address or browser details, it is not linked to an account, a visit or a download, no email is sent and it is not sent to PostHog. A tap on one of the Not opening it yet? reasons there (Later, not now; Not sure what it does for me; My Mac isn't Apple silicon; Not sure what it can see; Want the price first) is counted the same way, as a no, by reason. The Open BuildGist button on that page only asks your Mac to open BuildGist: nothing is sent to us.
- Visits to the after-download page: each time the page that starts the download and says how to open BuildGist is opened, we log one short entry to tell people from automated visitors: the time (UTC), whether the browser looks like a person's browser, an automated client or a headless browser, and whether the device looks like a Mac, another computer, a phone or tablet, or can't be told (both worked out from the browser's description of itself when the page is opened; that description is not kept), the name of the site that linked you (not the page), the word for that site, whether the download was fetched and whether it finished, and a code made from your IP address with a random key that changes every day. Your IP address itself is not stored, the daily key is never saved, and the code can't be turned back into an address or matched to another day. The log is not linked to an account, is not sent to PostHog, and each entry is deleted after 14 days. Leaving yourself out with /count-me-out leaves your visits out of it.
- What stopped you: if you answer this question on the sign-in page, the words you write, the word for the site that linked you and when. It is not linked to an account, a visit or a download, is not sent to PostHog, and is read only by us, to fix what gets in the way of signing in. It is deleted within 90 days, or sooner if you email kayvanandre@gmail.com.
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:
- what you asked your coding agent, and your Current task's instructions if one is open;
- the changes the run made, and the code around them in the files it changed;
- the names of the files it changed and by how many lines, and the messages of commits made during the run;
- selected test commands your coding agent ran during the run, and their results;
- project details: its folder name, branch, which coding agent made the run, and the names of its top-level files and folders.
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
- Your whole repository. To explain a run, BuildGist receives that run's changes and the code around them, and keeps only the short excerpts above (a very short file can fit in one).
- Files named like secrets, such as
.envfiles and keys. BuildGist never records them. - Your GitHub email address, repositories, organizations or access token. GitHub is used only to sign you in, and BuildGist keeps only the account details above.
- Your card or bank details: BuildGist never sees your card number. It does not keep the name, billing address or email you give at checkout.
- Your screen, clicks, scrolling or typing on BuildGist's pages. BuildGist uses no third-party analytics, advertising or tracking scripts, and it doesn't track you across other websites, so it treats every browser the same whether or not it sends a Do Not Track signal.
How BuildGist uses your data
- To provide BuildGist to you: recording and syncing your runs, writing and showing their explanations, your account, computers and sign-ins, Continue, and BuildGist Pro, including its trial, checkouts and subscription records.
- To keep BuildGist secure, working and fair to use: server logs, security and abuse checks, the code that lets Anthropic spot abuse, and the limits on each account's use, including what explanations cost each day.
- To learn whether BuildGist is useful and easy to set up: product activity, and the one word for where you heard about BuildGist when an account has it.
- The waitlist: only to tell you about BuildGist.
- Save my email: we email you the Mac link once, from kay@mail.grokbot.com.
- Where the law requires BuildGist to keep or disclose something.
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
- Anthropic writes explanations for BuildGist. It receives what How explanations are made lists, and a code standing for your account so it can spot abuse, only to do that, under BuildGist's agreement with it, and does not use it to train its models.
- The agent you continue in: when you choose Continue, that agent receives your task's context, under your own account with it and its provider's terms.
- Fly.io hosts BuildGist (United States).
- GitHub provides sign-in.
- Stripe and Link, a Stripe company, process payments for BuildGist Pro, which Link sells as merchant of record ("Sold through Link"). If you subscribe, you give them your name, billing address, email and card details, under their own privacy policies (Stripe, Link). BuildGist sends Stripe nothing about you but your BuildGist account ID, a random identifier, to match the subscription to your account.
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.
- What is sent to write an explanation is not stored by BuildGist.
- A sign-in is removed when you sign out of it.
- Server logs are kept by Fly.io's logging service, not in BuildGist's database or backups.
- The waitlist keeps your entry until you ask for it to be removed.
- An address left for the Mac link is deleted within 30 days of being left.
- An entry in the log of visits to the after-download page is deleted 14 days after the visit.
- Backups are kept for 7 days, so deleted data can remain in a backup for up to 7 days.
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
- A copy of your data: Settings → Download my BuildGist data.
- Deleting it: Settings → Delete my account.
- Stopping what is sent: in BuildGist for Mac, choose Disconnect this Mac, or pause a project.
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.