Privacy & your data — your work stays local

TakeoffQuote runs entirely in your browser. Your plan PDFs are rendered locally and your takeoff autosaves to this browser's own storage (IndexedDB + localStorage) about a second after every change — there is no account, and nothing about your plans, measurements, or prices is ever uploaded. Close the tab and come back: your work is still there. Clear the browser's site data and it's gone, so export a backup for anything that matters.

What lives where

• Your plan files — read and rendered in the browser; stored in this browser’s IndexedDB so the set reopens instantly. They are never transmitted.
• Your takeoff — shapes, conditions, scales, markups — autosaves to IndexedDB + localStorage about a second after every change; the toolbar ticks saving… / saved ✓.
• Quote bindings and unit prices — your assembly choices, parameters, prices, and company name are kept in the same local storage, so the next project opens the Quote builder already configured.

“Client-only” means exactly this: in TakeoffQuote there is no server in the takeoff loop. Nothing about your plans, quantities, or prices crosses the network.

What does cross it on takeoffquote.com is a count of eight product events — a plan opened, a quote completed, the Pro gate shown, an upgrade clicked, checkout started, a key activated, a pricing path clicked, interest in a per-project pack — so we can tell whether the paywall is working and which way of paying people prefer. Each carries the event’s name — plus, where one applies, a single word from a fixed list (“monthly”/“yearly”, “subscription”/“per_project”, or a pack size of “5”, “10” or “20”) — and nothing else: no cookie, no identifier, nothing from your drawings. The Privacy Policy spells out exactly what each one contains.

Closing the tab, and the real boundaries

Closing the tab loses nothing — reload, close the browser, come back tomorrow; autosave has it. The boundaries that do matter:

• Storage is per browser, per device. A different browser profile or a different machine is a fresh, empty workspace. Work doesn’t follow you across devices, because there’s no server to carry it.
• Clearing site data clears your work. The browser’s “clear browsing data” for this site deletes the IndexedDB and localStorage that hold your takeoff.
• Private/incognito windows typically discard site storage when the window closes.

Take it out of the browser

Export takeoff… writes 〈project〉.takeoff.json — the exact document autosave writes — to a normal file you can back up, archive for years, or hand to another estimator. Import takeoff… reads it back as an editable takeoff. Export one at every milestone; it’s the answer to every boundary above. The report and quote exports are likewise generated in the browser and downloaded straight to your disk.

Failure honesty

If a saved project ever fails to load, autosave pauses itself and a banner says so — a load failure never overwrites your saved work with an empty canvas. And if the app updates in another tab, the stale tab asks for a reload instead of writing over the newer one.