Privacy

The rest of this page is the detail behind those three lines: exactly what we collect, where it goes, and how to ask us to delete it. If something here ever stops being true, this page changes to match — not the other way around.

The free tools run in your browser

The invoice generator, the quote generator, the terms & conditions builder, the client follow-up planner, the calculators (rate, markup & margin, late fee, minimum job price, job profit check, day plan check, discount check, callback profit check, materials up-front check, payment method check, client value check, quote pipeline check, unbilled work check, quiet season check, time off check, working hours check), and the admin health check all do their work on your device, in the page, right now — there’s no server involved in the math or the scoring. A client’s name, a job amount, a line item, which answer you picked on the health check: none of it is ever transmitted, and none of it is stored on our side. We couldn’t show you what you typed or answered into one of these tools if you asked us to, because we never had it. The follow-up planner's calendar-file download works the same way: the file is built in the page and saved by your own browser, and it never passes through us either.

A few of these tools do keep something on your device, in the same tab-only storage, and only so your own work carries forward instead of getting lost. The “turn this quote into an invoice” hand-off: when you click that button, the quote generator puts the details into your browser tab’s own storage so the invoice generator can pick them up, and the invoice generator deletes them the instant it reads them. The terms builder’s “send this into the quote generator” hand-off works the same way. Anything left over from either disappears when you close the tab. Neither leaves your device, and neither reaches us.

The invoice and quote generators also each keep a running draft in that same tab-only storage, as bb:invoice-draft and bb:quote-draft. Every reload restores what you were typing — the client’s name and address, the line items, the dates, all of it. A stray tap no longer costs you the document you were building. Close the tab, and the draft closes with it. Nothing in either draft is sent to us.

The terms builder also remembers the details you fill in at the top of it — a notice period, a deposit percentage, and the four other numbers its clauses use — saving them as you type into bb_terms_fields in localStorage so you don’t retype them next visit. That stays on this device until you clear it, and it is never sent to us. The calculators, the follow-up planner, and the admin health check have no hand-off and write nothing at all — the health check puts none of your answers in localStorage or sessionStorage, so they’re gone the moment you close the tab or reload the page. (The two random visit ids described under “How we count visits” below are set on every page of this site, including this one; they carry nothing you typed or answered.)

The one exception: once you finish all ten health-check questions, we log a single anonymous event — your overall score, the band it falls in (e.g. “mostly under control”), and which one stage came out weakest. That’s it; none of your ten individual answers are ever sent. It’s the same kind of aggregate signal described below, and it’s how we decide which guide to write next.

One set of your own details is shared across every free tool on purpose, for convenience rather than a hand-off: your business name, your own name, a contact line, your business address, your usual currency, your default tax rate, and your default payment notes — seven fields, stored together in bb_profile in localStorage. Fill them in once from the “fill it in once” card at the top of the free tools hub, and they show up already filled in on the invoice and quote generators, every printables sheet, and every templates pack. On the invoice and quote generators it’s opt-in — a checkbox, unchecked by default — so nothing is remembered there unless you ask for it; on the printables and templates pages, the “fill it in once” box saves as you type, the same as it always has. Client names, client addresses, line items, amounts, dates, and invoice or quote numbers are never part of this — only your own business details are. The profile card clears all seven fields. So do the invoice and quote generators. The printables have no Clear button. Typing in one still saves your details. Each templates pack clears one message’s client, invoice number, amount, and due date. Your name and business stay saved. All of it also disappears if you clear your browser’s storage. None of it is ever sent to us.

If you’d already filled in the old, separate “fill these in once” boxes before this shared profile existed — bb_tpl_fields on /templates/, bb_print_fields on /printables/ — the first tool page you open after this change copies your name and business over to bb_profile automatically, once, and removes the old, now-duplicated copy. The per-message fields on /templates/ — client, invoice number, amount, and due date — aren’t part of that move; they stay in bb_tpl_fields, because they’re specific to one message, not your identity.

To be precise about what that promise covers and what it doesn’t: visiting a tool’s page still counts as a page view, the same as any other page on this site (see “How we count visits” below) — so we can tell that a tool page was opened. What we can’t tell, and never ask for, is what you typed into it. “What you type into a tool never leaves your browser” is the honest version of the claim; “we don’t know you were here” isn’t.

If you ask for early access

The early-access form asks for your name and email, and optionally your business name and a note. If you fill it in, those fields — plus which page and campaign sent you, and a random id for your visit — go to a relay so a person can read it and reply. That’s the whole reason it exists: it is not a newsletter list and nothing on it is sold or shared. Submitting the form also logs an anonymous event to the analytics described below, so we can tell the form is working — but that event never carries your name, email, or note, only whether you filled in the optional business field (yes/no) and which topic you picked from a fixed list. Optional fields you leave blank arrive empty; there’s nothing in them to read.

How we count visits

Our own analytics is first-party and cookieless — worth being precise about what that means. It is not “we store nothing on your device.” It’s no cookies, but two random ids that identify a visit without identifying you: bb_anon_id, held in your browser’s localStorage so we can tell repeat visits from new ones, and bb_session_id, held in sessionStorage and cleared when you close the tab. Alongside those, we keep a snapshot of the campaign/referrer that brought you here (things like a UTM parameter or which site linked to us), so we can tell which guide or ad actually works — not so we can identify you.

Google Analytics also runs on this site, for the same reason: so we can see which pages get traffic and which channels bring people in. It’s Google’s own tool, and unlike the analytics above, it does use cookies — _ga and _ga_<id>, set in your browser. On every page it sends Google the page URL, the referrer, basic device and browser details, and an approximate location Google works out from your IP address; that’s Google’s standard collection, not something we added on top. We don’t send it your name, your email, or anything you type into a form or tool here — but that data belongs to Google, under Google’s terms, not ours.

Two of those are worth calling out on their own, because they’re the ones people actually worry about: searching this site (via the ⌘K overlay or /search/) never sends the words you typed — only how long the query was and how many results it found. And your email address, if you give it to us, is never hashed or folded into analytics in any form — it exists only in the early-access relay, for replying to you.

Your data, your call

If you want to know what we hold on you, or want it deleted, ask through the early-access form — mention that’s what you’re asking for, and a person will read it and respond. We don’t keep a public support address on this site; that form is the one channel that reaches us, so it’s also the one channel for this. During early access we keep what you send us until you ask us to delete it — we don’t yet have a fixed retention period to promise beyond that, and we’d rather say so plainly than invent one.

This is a young, self-funded product built by a small team — see who’s behind it. We’ll update this page as that changes, and the date at the top will always say when it last did.