Last updated 14 September 2026

Privacy

Hunter Apps, Inc. (a Delaware corporation) runs Do Not Build. This page says what we hold, why, and what you can ask us to do about it. It describes the service as it is actually built — where we do not do something, it says so rather than reserving the right.

What we hold

  • Your account. The email address you signed in with, how you signed in (password or Google), your name, and — if you tell us it is a business account — a registered name, tax ID and country for invoicing. Nothing here is required beyond the email and a name for the account.
  • What you do in the tool. The markets you save, the stances you take on them, the runs you start, and what each run cost. The spend record exists because runs cost real money at third parties and an account has a monthly limit; without it we could not tell you what you have spent.
  • Conversations with the analyst. The questions you ask, the answers it gives, and any file you attach to a question.
  • Ordinary server logs. Requests, errors and timings, which include IP addresses. Used to keep the service up and to find bugs.
  • Recordings of how you use the tool. While you are signed in, we record your sessions in the board — the pages you open, where you click and scroll, what was on screen, and technical details such as errors and how long pages took to load — so we can see where the tool confuses people or breaks, and fix it. Everything you type into a field is masked in your browser before it is sent, and so is the text of your analyst conversations, your comments and your notes. Your account settings are never recorded. Recordings are tied to an internal user ID rather than your email, and are deleted after 30 days.

What we do not hold

  • No tracking before you sign in unless you allow it. On the public pages — the front page, the public verdicts and the welcome page — we count a handful of named events, such as which sections were seen and which link was followed, without cookies and without identifying you, and nothing is recorded. Google Analytics runs on every page; until you allow its cookies it sets none and measures visits only in aggregate. There is no advertising pixel.
  • No card details.Payments run through Stripe. Card numbers are entered on Stripe's pages and never reach our servers; we store the identifiers Stripe gives us so we know which subscription belongs to which account.
  • No selling, and no sharing for advertising. We do not sell personal information and we have no advertising business to share it with.

Cookies

The event counts and the recordings described above set no cookies at all. The only cookies not needed to run the site are Google Analytics', and we ask before setting them.

  • Session. Your signed-in session, issued by Supabase. Removing it signs you out.
  • Preferences. Which account you are acting as, which sign-in method you used last, whether the sidebar is collapsed, and whether the analyst panel is open, and your answer about analytics cookies. All of them are conveniences and none of them identifies you to anyone else.
  • Analytics, only if you allow it.Google Analytics' _ga cookies, which hold a random identifier so a returning visit is counted as one visitor rather than two. They are never used for advertising. Say no, or change your mind later, and they are not set or are removed.

Who else processes it

We use a small number of providers, each for one job. They act on our instructions and may not use your data for their own purposes.

  • Supabase — the database and sign-in, hosted in the EU. Everything in the first section above lives here.
  • Stripe — subscriptions and payment. They are the controller of the card data you give them.
  • Anthropic and OpenRouter — the models behind the analyst and behind the judgements a screen makes.
  • PostHog— the public pages' event counts and signed-in session recordings, hosted in the US.
  • Google — visit measurement through Google Analytics, with cookies only if you allow them.
  • Our hosting provider — runs the application and its logs.

What the analyst sends to a model

When you ask the analyst something, we send the model your question, the conversation so far, a short note about which page you asked from — the route and any filters in force, never the rows on your screen — and any file you attached. It reads the corpus through the same endpoints you can open yourself, carrying your own permissions.

Our model providers do not train on data sent through their business APIs. Do not paste anything into the analyst you would not want leaving our servers under that arrangement.

Why we are allowed to

If you are in the UK or the EEA: we process your account and your use of the tool to perform our contract with you; we keep logs and spend records, and record signed-in sessions, on our legitimate interest in running a service that stays up, does not lose money and gets easier to use; we count visits to the public pages on the same interest, without identifying anyone; we set Google Analytics cookies only with your consent, which you can withdraw under Cookies above; and we keep invoicing records because the law requires it.

How long

Account data and your work in the tool are kept while the account exists, and deleted within 30 days of you asking us to close it. Server logs are kept for a short operational period. Invoices and the spend ledger behind them are kept as long as tax law requires, which is longer than the account.

What survives deletion is the corpus itself — markets, screens, verdicts and the evidence behind them. Those are measurements about companies and industries rather than about you, and they are not tied to your identity once your account is gone.

What you can ask for

A copy of what we hold about you, a correction, deletion, an export, or that we stop a particular use. Write to [email protected] and we will answer within 30 days. If you are in the UK or EEA and think we have got it wrong, you may complain to your data protection authority.

Where it goes

We are a US company using EU-hosted infrastructure, so data moves between the two. Those transfers rely on the standard contractual clauses in our agreements with the providers named above.

Children

This is a tool for people deciding where to invest their working time. It is not for anyone under 16 and we do not knowingly collect their data.

Changes

If this page changes in a way that matters we will update the date at the top and tell account holders by email. Continuing to use the service after that means the new version applies.

Questions, or anything that reads wrong: [email protected]. See also our terms.