Privacy Policy
The Housing Model at thehousingmodel.com and plan.thehousingmodel.com is operated by Brooks Digital Ventures LLC, a New Jersey limited liability company. The website and the five-minute look are at thehousingmodel.com; the full plan — the web application where household figures are entered and saved plans are stored — is at plan.thehousingmodel.com. This policy covers both.
Your household inputs, calculations, saved plans, and any paystub image you select stay in your browser. We do not receive them. There is no account and no server-side database of household information. This is not a promise about how carefully we handle your data — it is a description of software that never sends it anywhere. Two measurement services count visits and clicks (section 6); neither is given anything you type. The full plan is open to anyone and needs no code. The private beta, and the record it left, are described in section 14; the code controlled who could open the full plan and had nothing to do with what anyone entered once inside.
On this page
1 The short version
Four different things can be called “your data” here, and they are governed by four different answers. Conflating them is how a privacy policy ends up technically true and actually misleading, so they are kept apart throughout this document.
1. What you enter. Income, debts, childcare, balances, your ages and the ages you plan to stop working, the Social Security and health-cover figures you type, the home you own and its loan, sale and rental, the rent, renter’s insurance and security deposit if you compare selling it and renting instead, the projects you date and which home each is for, a second home’s price, loan, use and rent, a paystub image, the projections computed from them, and every plan you save. This never leaves your browser. We do not receive it, we could not produce it if asked, and there is no account or server-side database that holds it. Sections 2, 3 and 4.
2. What any web request reveals. Loading a page from us means your browser connects to the companies that host and serve it, and they see your IP address and the usual connection details, as they would for any website. We do not control that and neither does any website. What those requests do not carry is category 1. Section 5 names every company involved and which page each one is on.
3. What we deliberately count. Page views, through Cloudflare Web Analytics, which sets no cookies and does not identify you. Page views and clicks on both sites, through HeyCatch: which pages are opened, and what kind of thing on them is clicked — never what you typed, the words on what you clicked, or the part of an address after a ? or # — under a random identifier kept in your browser. With Do Not Track or Global Privacy Control turned on, HeyCatch does not run at all. That a Pass was sold, which our server tells HeyCatch with nothing about who bought it. And two tallies in the full plan: how many browsers have finished setting up a plan, and how many have opened the full report. Each is a single word sent once per browser, with no figure and no identifier. That is the entire list. While the private beta ran, we also recorded that an access code had been used; section 14 says what that record contains. Sections 4, 6 and 14.
4. What you choose to hand over. An email address, if you submit the optional signup form. Your payment details, if you buy, which go to Paddle and to the card processor Paddle uses, and never to us — though Paddle does tell us that a purchase was made and the email address you bought with, because that is how your license key reaches you, and the page you bought on passes us Paddle’s id for the purchase so it can fetch your key at once. Neither is required to use the five-minute look or the full plan. And feedback, if you press Send feedback, write a note and send it — only the notes you write and what section 15 lists, never your plan. Sections 5, 8, 10 and 15.
Category 1 is the one that matters most and it is the one we designed hardest around: it is not a promise to handle your figures carefully, it is software that never sends them anywhere.
2 What you enter
Household figures can be entered in two places: the five-minute look at thehousingmodel.com, which is on its own page and at the top of the home page, and the full plan at plan.thehousingmodel.com. A paystub is only ever read in the full plan. Both process what you type there — income, debts, childcare costs and every other input — entirely within your browser. Your financial inputs and calculated projections are not sent to us, or to our hosting, font, measurement, or chart-library providers.
Going from the five-minute look to the full plan. When you follow “Build your full plan” from the five-minute look, the figures you changed there go with you — any of the five, and any you set under “Numbers it filled in for you” (the down payment, mortgage rate, property tax, how many years to project, and the three growth rates), or none — so the full plan can start from them. Figures you left at the example are not sent, and the full plan leaves those boxes for you to fill in. They travel in the part of the link after the # sign, which browsers do not send to any server — not to us, not to our hosting, and not in the address a site you visit next is told you came from. The full plan takes them out of the address as the page opens, before either measurement script runs, and holds them only in that browser tab until it has filled them in. If the full plan is already keeping a plan of yours, it asks before anything replaces it. Your browser may still list the visit in its own history, as it does any page you open; that history stays on your device.
The home page. The top of the home page is the five-minute look itself, the same as on its own page, and it works the same way: what you type stays in the page, nothing of it is kept in your browser, and only “Build your full plan” carries figures on, as above. Until 15 October 2026 the home page had a five-figure card instead, which kept the figures you changed in this browser under their own name (thehousingmodel.starter) and passed them to the five-minute look after the # sign. The home page no longer reads or writes that entry; clearing site data for thehousingmodel.com removes any left behind. The home page does not load Paddle’s checkout library; the pricing page does (section 5), and it takes no household figures.
An assistant on the page. Where your browser supports it, an assistant you use on the full plan’s page can read what you entered and change a few of its inputs; without the Housing Model Pass it is given none of the plan’s results, and with it, only what the page shows you, and nothing is sent to us. The inputs it can change are cash, the reserve, the home’s price, the down payment, rent, the mortgage rate and the target month, and only on the plan you are looking at; it cannot save a version or export a file. What your assistant does with what it reads is between you and its provider.
3 Paystub images
If you select a paycheck stub, it is read in your browser and is never uploaded to us or to an external processing service. Three things are worth keeping apart. The file itself is never written into your saved plan and is discarded when you finish with the importer. What was read off it automatically is discarded with it. The figures you review and apply become part of your plan, and are stored in your browser with it exactly as they would be had you typed them.
A text-based PDF can be read automatically. A scan or a photograph cannot, in this version: it is displayed to you and the figures are typed in by hand. Nothing is sent anywhere to read it either way.
Clearing website storage does not delete the original image file from your device. You control that file separately.
4 Saved plans and browser storage
Saved plans use localStorage in your browser on your device. Local storage is not a cookie, and it may remain after you close the page or restart the browser. It is not an account or a backup with us.
What else the full plan keeps there. Besides the versions you save (thehousingmodel.plans.v1), the full plan keeps the plan you are working on as you type, without your pressing Save (thehousingmodel.draft.v1), so that it is there when you come back, finished or not. When something replaces the plan on screen — the example plan, clearing the plan, the five-minute look’s figures or an assistant’s answers — the plan that was there before is kept in a second entry (thehousingmodel.draft.replaced.v1) until you put it back or discard it. These entries hold everything you entered. For a household that owns its home that includes the home’s value, what was paid for it and when, the loan’s balance, rate and payment, how a move is timed and paid for (with a HELOC’s or bridge loan’s terms), a rental’s rent and costs, the rent, renter’s insurance and security deposit if you compare selling the home and renting instead (and the month it would be sold), your filing status and the income figure the rental rules use; for a second home, its price and loan, the nights you would use it and rent it out, its rent and running costs; and, on any plan, the projects you date and which home each is for. None of it is sent anywhere.
The automatic backup. After you save a version, the full plan downloads a backup file of your saved plans to your device, as any download is saved: on the first save on a device, and after that when your saved plans have changed and the last copy is more than ten minutes old. It says so on screen when it does, and you can turn it off. That setting is kept in thehousingmodel.autobackup.v1, with the time of the last copy and which saved versions it held, by their identifiers rather than their figures. The file is yours and is not sent to us; it holds the inputs of your saved plans, not their results, which are worked out again from those inputs when you restore it. If you have unlocked the full plan with a license key, a backup file (automatic or one you ask for) also holds that key, so that restoring it on another device unlocks it there: keep the file as you would keep the key (section 9).
Someone with access to your browser profile may be able to open your saved plans. Take care on shared devices.
To delete saved plans, clear site data or local storage for plan.thehousingmodel.com in your browser settings. Browser storage is kept separately for each site, so clearing site data for thehousingmodel.com will not remove plans saved in the full plan at plan.thehousingmodel.com. Clearing browsing history alone may not do this. Repeat it on each device, browser, or profile where you saved plans. Clearing site data may also remove locally stored preferences, your age and Terms confirmation, or license information, if present (a license key you entered is kept in thehousingmodel.licence.v1).
It also keeps two preferences, neither of which holds anything you entered: thehousingmodel.setup-mode, whether you chose the simple plan or the full one (the word simple or full), and thehousingmodel.install.dismissed.v1, which records only that you dismissed the suggestion to install the full plan as an app (the digit 1).
The full plan also keeps two small markers, hm-counted-plan-built and hm-counted-report-opened, which record only that this browser has already been counted in the tallies described in section 6, so it is not counted twice. They contain the digit 1 and nothing else.
After a payment is reported on the page you bought on, that browser tab keeps one more marker, hm-payment-reported, in its session storage: the time the payment was reported, and nothing else — no transaction id, no key, nothing about your household. It is there so that reloading the page while your key is on its way does not offer the Pass again. It is removed when your key is in place, when the tab is closed, and is ignored after an hour.
Two entries that last no longer than the tab. If you follow the five-minute look’s link into the full plan, the five figures you typed there travel in the part of the link after # (section 2). The full plan moves them straight into one entry in that tab’s session storage, hm-quick-handoff, and removes the entry as soon as it has read them into your plan. While Send feedback is open, the tab also keeps hm-review. It records only that the tab is in feedback mode: the word feedback, or the review code in the link you were given. While it is there, the tallies in section 6 and HeyCatch stay off for the rest of the visit. It is removed when you close the feedback panel or the tab.
Feedback you have not sent yet. Notes you write with Send feedback (section 15) are kept in local storage, in the browser and on the site where you wrote them, until you send them:
hm-review-notes-v1holds each note, the tag you chose, the sentence on the page it is about, the page’s address (without anything after a?or#), your screen size, when you wrote it, and the name you typed, if you typed one;hm-review-name-v1holds the name you typed so your notes can be told apart, if you typed one;hm-review-context-v1is used only if you turn on the optional route record. It holds that record: the pages and setup steps you visited, roughly when, the printed names of fields that showed an error, and your screen size. It never holds what you typed into a field.
Notes are removed from your browser once they are sent. Clearing site data removes all three entries.
HeyCatch’s entries. On both sites, HeyCatch (section 6) keeps two entries in local storage: ph_phc_…_posthog, holding a random identifier for this browser, the current visit’s identifiers, the page you first arrived on (our pages remove anything after a # from the address before HeyCatch starts) and the site you came from; and heycatch_session_volume, a count it uses to limit how much one visit can send. While a tab is open it also keeps the same visit’s details in that tab’s session storage, under names beginning ph_phc_. None of them holds anything you typed. Clearing site data for thehousingmodel.com or plan.thehousingmodel.com removes them, after which HeyCatch sees a new browser. With Do Not Track or Global Privacy Control turned on, HeyCatch does not start, so it keeps none of these. If Review Mode starts while HeyCatch is running (section 6), HeyCatch stops for the rest of that visit: it removes its ph_phc_…_posthog entry and keeps two small entries, __ph_opt_in_out_phc_… and thehousingmodel.heycatch-review-pause, which record only that it was stopped. On a later visit both are removed and HeyCatch runs again as usual.
Your confirmation that you are 18 or older and accept the Terms is stored in the same way, in your own browser (thehousingmodel.assent.v1). It is a short record of the date you confirmed and which version of the Terms you confirmed against. It is never sent to us, it contains nothing about your household, and clearing site data removes it — after which the full plan asks again.
We cannot recover or remotely delete plans we never received.
5 Hosting and external assets
Cloudflare hosts and delivers both thehousingmodel.com and plan.thehousingmodel.com.
Both sites send each page with instructions to your browser that limit what the page may do: load scripts, styles, fonts and connections only from the hosts this policy names for that page (a Content Security Policy), use HTTPS only, never be shown inside another site’s page, and never use your camera, microphone or location. They restrict what a page can load; they change nothing that is collected or sent.
Beyond that, different pages load different third parties, so they are listed page by page rather than lumped together. This list was produced by loading each page and recording every request it made, not from memory of what the code should do.
Every page at thehousingmodel.com also runs HeyCatch, described in section 6. Its script is served from thehousingmodel.com itself, and it sends to in.heycatch.ai; it loads nothing from there.
Every page at thehousingmodel.com, and the full plan, also has the Send feedback to the creator button. It sends nothing unless you write a note and press Send; then it sends what section 15 lists to our own site at plan.thehousingmodel.com, and nothing else.
The home page at thehousingmodel.com and the five-minute look’s page each serve their own fonts and the five-minute look’s own script, one file from this site that both pages share, and load the Cloudflare measurement script described in section 6 and a charting library from cdnjs.cloudflare.com, operated by Cloudflare, which draws the five-minute look’s chart; the home page carries the five-minute look itself. Neither loads Paddle or Paddle Retain.
The pricing page at thehousingmodel.com/pricing serves its own fonts and loads the Cloudflare measurement script, and Paddle’s checkout library from cdn.paddle.com. Paddle’s library in turn loads Paddle Retain from public.profitwell.com. Opening the payment window loads more than that — Paddle brings its own payment processor, error monitoring and translation service with it. Section 10 lists every one of them by name. It is the only page at thehousingmodel.com that loads Paddle, and it takes no household figures.
The legal pages (this one included), the third-party notices page (thehousingmodel.com/third-party-notices), the questions page at thehousingmodel.com/faq, the guide and comparison pages, the pages for homeowners trading up (thehousingmodel.com/trade-up) and for second homes (thehousingmodel.com/second-home), and the page shown for an address that does not exist (the 404 page) serve their own fonts, load the Cloudflare measurement script and run HeyCatch, and nothing else, apart from your feedback if you press Send (section 15).
The full plan at plan.thehousingmodel.com — the only place a paystub is ever read, and where the detailed household figures are entered — contacts two third parties while you are using it: the Cloudflare measurement script and HeyCatch, both described in section 6. Nothing else. HeyCatch’s script is part of the full plan’s own code; it sends to in.heycatch.ai and loads nothing from there. It does not run on the page a buyer lands on after paying (plan.thehousingmodel.com/pass), whose address carries Paddle’s transaction id. HeyCatch’s script can add three random visit identifiers (X-HeyCatch-Session-Id, X-HeyCatch-Window-Id and X-HeyCatch-Distinct-Id) to requests a page makes to its own site; we switch that off as it starts, on both sites, so no request to our sites or to Cloudflare’s measurement carries them. The full plan serves its own fonts, requests none from Google, and carries no advertising and no analytics beyond these two. Where your browser supports it, it also offers an assistant you use on the page two tools — one reads the plan’s free figures, one changes a few of its inputs (section 2). They run inside your browser and send nothing to us.
The full plan’s copy of the third-party notices (plan.thehousingmodel.com/third-party-notices) is a plain page with no script of its own. It loads nothing from a third party, apart from the Cloudflare measurement script where Cloudflare adds it (section 6).
And Paddle, if and only if you ask to buy. The Housing Model Pass can be bought from inside the full plan and from its product page, plan.thehousingmodel.com/product. Paddle’s checkout library is requested from cdn.paddle.com at the moment you click the buy button — not when the page loads, and not when you open the panel that describes the Housing Model Pass. If you build a plan, read what it says and leave, your browser never contacts Paddle at all. Once the library does load it brings Paddle’s own supporting services with it — a card processor, error monitoring, translation and Paddle Retain — exactly as it does on the pricing page; section 10 lists every one of them by name. Neither is given anything you entered: the checkout is told which price you are buying, and that is the whole of what passes it. It is not told anything about your household, and it is not given an address to send you to afterwards.
This was not always so. Until 2 October 2026 the full plan’s buy button was a link out to the home page, and this section said the full plan carried no payment code of any kind. That is recorded here rather than quietly replaced, because a policy that silently stops saying something is worse than one that says what changed.
One request the full plan makes to us. If this browser holds a license key, the full plan downloads a short file from our own site listing the keys that have been withdrawn — keys belonging to purchases that were refunded, or whose payment was reversed by a chargeback decided against us. It is a plain list and we send all of it, every time, to every visitor. That is deliberate: asking us “has this key been withdrawn?” would tell us which key you hold, so the full plan never asks that question. It downloads the whole list and compares against it on your device. The comparison uses a one-way fingerprint of your key computed in your browser; your key itself is not in the request and never reaches us. The request carries no household figure, no plan and no paystub, and it goes to our own site rather than to a third party. If it fails for any reason — you are offline, the file is unreachable — the full plan carries on working; a key is never locked out because the list could not be fetched.
A second request: the usage tally. The first time a browser finishes setting up a plan, and the first time it opens the full report, the full plan sends one word to our own site — plan-built or report-opened — and nothing else. Section 6 says what is kept.
A third request: today’s mortgage rate. Beside the mortgage-rate box, the full plan shows Freddie Mac’s weekly 30-year fixed average as a guide. To get it, the full plan asks our own site for /api/rate, with nothing in the request: no figure, no plan, no identifier. Our server, not your browser, reads the figure from Freddie Mac (or from the St. Louis Fed’s copy of it) about once a day, so your browser never contacts either. The guide never fills in or changes your own rate.
A fourth request, only after you pay. When the checkout reports that your payment went through, the page you bought on sends our own site the transaction id Paddle gave it for that purchase (it begins txn_), and nothing else. In the full plan that is a request to /api/pass on plan.thehousingmodel.com, the site you are already on, tried up to five times over about twenty seconds while Paddle settles the payment. On the pricing page at thehousingmodel.com, which is a different site, your browser is taken instead to plan.thehousingmodel.com/pass with the id in the address. Either way our server asks Paddle whether that transaction completed and was not refunded, for the Housing Model Pass, and only then answers with your license key: in the full plan the page checks it and keeps it in your browser, as section 9 describes, and /pass shows it to you. The request carries no household figure, no plan and no paystub. To limit abuse, our server keeps your connection’s address (for an IPv6 address, the network part of it) in memory while it counts requests, and lets it go once a minute has passed since the last one it counted, the next time it answers a request. It never writes it down or sends it anywhere.
And one message Paddle sends us. Separately, when a payment completes, Paddle tells our server so directly. The server checks that the message really is Paddle’s, asks Paddle for that transaction and the email address it was bought with, and emails your key to that address through Resend, the provider we use to send email. Your browser takes no part in it, and nothing about your household is in it.
We test this rather than assert it. Before each release the full plan is driven by an automated browser with a household made of numbers nobody would type by accident, every request it makes is recorded, and every URL, header and body is searched for those numbers. The measurement requests are searched along with the rest. Finding one anywhere fails the release. HeyCatch ignores automated browsers, so it sends nothing in that test; a second test makes it treat the browser as a person, types such numbers into the five-minute look on the home page, clicks through it and on into the full plan, and searches everything HeyCatch would have received. That test answers HeyCatch’s requests itself, so none of it reaches HeyCatch. That browser test does not see the usage tally, because the tally is never sent from an automated browser or from a test copy of the full plan; a separate check holds it to the one word, the two places it is sent, and the once-per-browser rule.
The two claims above are tested in two ways, because they are different claims. That run uses the full plan without buying anything, and fails the release if a payment host is contacted at all — which is how the sentence about Paddle loading only on the click is held to be true rather than merely intended. It does not click to buy: it runs with a license key, and a browser holding one is not offered the Pass. So after each release of the full plan a second check clicks the live buy button with every request to Paddle blocked, so that no checkout opens and nothing is bought, and passes only if nothing reached for Paddle before the click, the click asked for Paddle’s checkout library, and the page stayed on the full plan and said nothing was charged.
Last verified: 2026-11-05, against https://plan.thehousingmodel.com/plan. 80 requests were recorded and searched for 7 household values planted in the plan; none were found in any of them. Hosts contacted before any request to buy: https://plan.thehousingmodel.com, https://static.cloudflareinsights.com. in.heycatch.ai is not among them because HeyCatch ignores automated browsers; it is checked separately, most recently on 2026-11-05, when 47 requests to it were read and none carried a household figure (section 6).
These providers receive your IP address as part of the network connection, as any web request does. The requests do not transmit your household inputs, saved plans, paystub images, or calculated results.
Cloudflare’s privacy information: cloudflare.com/privacypolicy
Google’s privacy information: policies.google.com/privacy
6 Measurement
Two services measure how the sites are used: Cloudflare Web Analytics, which counts page views, and HeyCatch, which counts page views and clicks. Neither is given anything you type. Each is described below.
Cloudflare Web Analytics. We use Cloudflare Web Analytics to count page views and see which pages people visit. It runs on every page of the website and on the full plan.
It works in two parts, and both are named here because naming one and not the other would understate it. A small script is fetched from static.cloudflareinsights.com, which is a Cloudflare host and not part of this site. That script then sends the measurement to /cdn-cgi/rum on whichever of our sites you are visiting. Cloudflare inserts this at its edge rather than it being written into our pages.
It sets no cookies, does not identify you, and does not follow you across other websites. It receives no part of your household inputs, saved plans, paystub images, or calculated results. We use it only to know how many people visit and which pages they reach. We do not use advertising or advertising trackers anywhere on either site.
HeyCatch. We also use HeyCatch, provided by HeyCatch, Inc. (heycatch.ai), to see how people move through the website and the full plan: which pages they open, and where they click. It runs on every page at thehousingmodel.com and on the full plan. Its script is part of our own pages; it sends what it records to in.heycatch.ai.
What HeyCatch records. Each page view and when you leave a page, with how far down it you scrolled; the page’s address and title, with anything after a ? or # removed; the address of the site you came from, cut the same way, and a link’s campaign tag (utm_) if it carried one. Each click: what kind of thing was clicked (a button, a link, a box) and where it sits in the page’s layout, by the names of its parts; for a link, the address it goes to, again without anything after a ? or #; and repeated clicks on the same spot. Your browser and its version (including the full browser identification string it sends), operating system, language, time zone and its offset, screen and window size, and device type. A random identifier for your browser and for each visit (section 4), and the technical details its script adds to every record: the time, a random identifier for each record and page view, our project’s public key and our site’s address. HeyCatch keeps these as an anonymous profile for the random browser identifier, with no name or email.
Do Not Track and Global Privacy Control. If your browser sends either signal, HeyCatch is not started at all on either site: nothing is recorded, nothing is kept in your browser for it, and nothing is added to any request.
What HeyCatch is not given. Anything you type, on any page: no household figure, saved plan, paystub, result or license key. Not the words on what you click, nor its other details (a box’s value, an element’s label). Not the part of any address after a #, which is where a link to a five-minute look and the link into the full plan carry your figures, nor the part after a ?. Nothing from the page a buyer lands on after paying, and never Paddle’s transaction id: HeyCatch does not run on that page, and the page removes the id from its address once your key is shown. No name or email address — there are no accounts to give it. These limits are settings in our code, applied in your browser before anything is sent, and section 5 describes the test that checks them before each release. Only the kinds of record listed above are sent; anything else HeyCatch’s script could produce, such as an error report or copied text, is dropped before it leaves. HeyCatch does not run in Review Mode, on any copy of the sites but the live ones, or for a browser driven by automated testing. If you start Review Mode on a page where HeyCatch is already running (for example by pressing “Send feedback”), HeyCatch stops at that moment and nothing further is recorded or sent for the rest of that visit; on a later visit it runs again as usual. On a page where HeyCatch does not run, none of its script is loaded or run at all.
What the click records can show. Because a click is recorded by where it falls in the page’s layout, the records can show which part of the full plan was used — for example, that the section on children or the report was opened. They cannot show what was entered there, or what the plan worked out.
A sale. When Paddle confirms a payment, our server tells HeyCatch that a Pass was sold (pass_purchased), under an identifier made one-way from that purchase with a key only our server holds, so that if Paddle tells us about the same purchase more than once it is still counted once. The identifier cannot be turned back into anything about the purchase. It does not send your email, name, license key, Paddle’s transaction id, the price or your country.
Short links. Addresses such as thehousingmodel.com/a are short links for posts we share. Each sends you to the home page with a campaign tag in the address (?utm_source=heycatch&utm_campaign=a), so HeyCatch can count where visits came from. HeyCatch’s script takes the tag back out of the address bar a moment after the page opens.
Why we measure, and how to say no. We use Cloudflare Web Analytics and HeyCatch because we have a legitimate interest in knowing how the sites are used, so that we can fix what confuses people and improve the full plan; neither is given anything you type. You can say no at any time: turn on Do Not Track or Global Privacy Control in your browser and HeyCatch does not start, or clear site data (section 4) to remove what it kept. Section 12 says how to ask us anything else about your information.
HeyCatch’s side. HeyCatch processes these records on our behalf. Its privacy notice says that it acts as a processor for the analytics its script collects; that it receives the IP address and device details of visitors, as any web request reveals them; that it processes data in the United States; that its sub-processors include PostHog for this analytics and, for its AI analytics features, AI model providers; and that it keeps these records while we use the service and for two months after. HeyCatch’s privacy notice: heycatch.ai/privacy.
What Cloudflare can and cannot see on the full plan. The full plan is a single page: every step of the plan, every result and every panel happens at one address without the page ever changing. Web analytics counts pages. So what this records on the full plan is that the full plan was opened — not which step you reached, not what you entered, not whether you finished, and not what the model worked out. Web analytics has no mechanism by which it could record those. HeyCatch, above, records clicks and so can show which parts of the full plan were used; the pair of tallies below records that a step was reached, not by whom or with what.
Two tallies in the full plan. To know whether people get further than opening the full plan, it counts two things: a browser finishing guided setup on a plan that calculates, and a browser opening the full report. Each is counted once per browser, the first time it happens. What is sent is one word, plan-built or report-opened, to our own site. No figure, plan, result, step, key or identifier goes with it, and no cookie is involved.
What we keep is a running total for each word and a total for each day, in Cloudflare’s storage. We do not keep your IP address, your browser or where you came from with it, so a tally cannot be connected to you, and we see the totals only. To limit abuse, our server keeps your connection’s address (for an IPv6 address, the network part of it) in memory while it counts requests, and lets it go once a minute has passed since the last one it counted, the next time it answers a request. It never writes it down or sends it anywhere. Nothing is counted from the five-minute look, from Review Mode, or from a browser driven by automated testing. Clearing site data for plan.thehousingmodel.com removes the markers described in section 4; the full plan would then count that browser once more.
7 Cookies
The website sets no first-party cookies, and neither does the full plan. During the private beta, which has ended, the full plan set exactly one: it recorded that you had entered a valid access code so you were not asked again on every page. That cookie held the code’s label and a signature proving the label had not been edited; it contained no household figures, no identifier for you, and nothing readable by any other site. Nothing now asks for a code, and nothing of ours sets a cookie. HeyCatch is set to keep its identifier in local storage rather than a cookie (section 4).
Cloudflare’s security cookie. Cloudflare, which hosts both sites, may set one cookie of its own, __cf_bm, to tell people from automated traffic. It lasts about 30 minutes, holds no household figure and nothing that names you, and is used for that check alone. We do not read it. Cloudflare’s privacy information is linked in section 5.
Paddle’s copy of the same cookie. Paddle’s checkout library, which the pricing page loads (section 5), is itself served through Cloudflare, so a cookie of the same name, __cf_bm, may be set for paddle.com when the pricing page opens, even if you never click to buy. It is Paddle’s and Cloudflare’s, for the same 30-minute bot check, and holds nothing about you or your household. We cannot read it. Paddle’s privacy information is linked in section 10.
Saved plans use local storage, as described in section 4, which is a different mechanism and is not affected by clearing that cookie.
This does not mean external providers never use cookies. The email signup service described below has its own practices, set out in its own notice.
8 Optional email signup
If you submit the optional signup form, your email address is sent to FormSubmit at formsubmit.co, which forwards it to our inbox. The email address is the only thing you type that is sent. Three fixed values go with it, the same for everyone: a subject line for the email we receive, a setting that turns off FormSubmit’s own captcha page, and a tag naming the page the form is on (thehousingmodel.com/calculator.html), so we know where a signup came from. The submission does not include household inputs, plans, or a paystub. As with any internet request, the receiving service also sees connection information such as an IP address.
We use a signup address to send educational housing content and product updates about The Housing Model. Signing up is optional, is not required to use the five-minute look or the full plan, and gives us no access to your saved plans.
We keep a signup address until you ask us to stop. To unsubscribe, use the unsubscribe link in any message we send, or email hello@thehousingmodel.com and we will remove you. When you unsubscribe we remove the address from the active list and keep only a minimal record that you asked not to be emailed, used to honor that choice and for nothing else.
FormSubmit’s privacy notice: formsubmit.co/privacy.pdf
9 License keys
License keys are cryptographically signed and the signature is checked inside your browser. Your key is never transmitted to us or to anyone else, and neither is anything about your household. There is one related request, described in section 5: while you are online, the full plan downloads the whole public list of withdrawn-key fingerprints and compares against it on your device. It asks us nothing about your key — it takes the entire list and does the checking here — so that request reveals neither which key you hold nor whether you hold one. A browser that cannot check a key’s signature keeps the full plan locked and says so on the page; it still downloads that list, as every browser holding a key does, and sends nothing else about the key.
10 Purchases
Checkout is handled by Paddle, acting as the merchant of record for your purchase. Paddle collects the information it needs to process the payment and any applicable tax, under its own privacy notice. We do not receive or store your card details. Paddle tells us that a purchase was made and the email address you bought with, so that we can send you your license key; the exact contracting Paddle entity is named on your receipt.
When the library loads, which differs by page. On the pricing page at thehousingmodel.com/pricing it loads from the moment you open it, before you click anything. In the full plan it is the other way round: it is requested on the click and not before, so a visit that does not ask to buy does not reach Paddle. Either way its purpose is the same — to open the payment window when you ask for it — and until you ask, it takes no payment details. It is never handed anything you entered: the pricing page takes no household figures, and the figures you type into the five-minute look or the full plan stay in your browser, exactly as section 2 describes.
What opening the payment window actually loads. Paddle’s checkout is not one script from one host. When the payment window opens, it brings its own supporting services, chosen by Paddle rather than by us, and we disclose them because your browser requests them whether or not we picked them. Recorded by driving the deployed full plan at plan.thehousingmodel.com, clicking the buy button and logging every request:
cdn.paddle.com,buy.paddle.com,checkout-service.paddle.com— Paddle’s own library, payment window and checkout service.checkout-analytics.paddle.com— Paddle’s measurement of its own checkout.public.profitwell.com— Paddle Retain, described below.js.stripe.com,m.stripe.com,m.stripe.network— Stripe, which Paddle uses to process card payments and to check for fraud. Your card details go to Stripe and Paddle, and never to us.o522631.ingest.sentry.io— Sentry, Paddle’s error monitoring, so that a checkout that breaks is reported to Paddle.global.localizecdn.com— translation of the checkout’s own wording.fonts.googleapis.com,fonts.gstatic.com— the fonts the checkout uses.
All of these belong to the checkout. Two of them — Paddle’s library from cdn.paddle.com and Paddle Retain from public.profitwell.com — are loaded by the pricing page when it opens, as section 5 says; the rest are not loaded until you ask to pay. None is given anything you entered into the five-minute look or into the full plan: your household figures are not passed to the payment window, and the automated run above searches every one of these requests for them. This list is kept accurate by that run rather than by memory — if Paddle adds a service, the check fails and this page is wrong until it is updated.
Paddle Retain (ProfitWell). Paddle’s library automatically loads a second Paddle service from public.profitwell.com. It is Paddle’s subscription-analytics and payment-recovery product, included in Paddle’s checkout by default rather than something we added or configured. It is covered by Paddle’s privacy notice, linked above. We disclose it because your browser requests it whether or not we chose it, and a policy that listed Paddle but not this would be describing our intentions instead of your browser’s behavior.
Neither Paddle’s checkout nor Paddle Retain is loaded on the home page, the five-minute look’s page, the questions page or these legal pages. In the full plan they are loaded only after you click to buy. No page sends your household figures or a paystub to either of them, on any page, at any point — which is the claim that matters and the one we test.
11 Children
The Housing Model is intended for adults aged 18 and over. It is not directed to children under 13, and we do not knowingly collect signup email addresses from children under 13.
If you believe a child under 13 submitted an address, contact hello@thehousingmodel.com so we can investigate and remove information we hold. We cannot identify or retrieve information entered only into a visitor’s own browser.
12 Your choices and requests
You can use the five-minute look and the full plan without joining the email list and without selecting a paystub. You can delete locally saved plans through your browser settings, and you can ask us to remove signup information we hold, subject to the minimal do-not-email record described above.
Deleting browser storage does not delete an email address you already submitted through signup. Asking us to delete an email address does not clear the plans in your browser. Please do not send paystubs or household financial details with a privacy request — we do not need them, and we would rather not receive them.
We will handle requests about information we hold as applicable law requires.
13 Policy changes
We will update this policy when our practices change and show a new effective date. For materially different uses of personal information we will give appropriate notice, and obtain consent where it is required, before beginning the new use.
14 Private beta access
The private beta ended on 23 September 2026 and the full plan is now open to anyone. While it ran, opening the full plan required an access code that we handed out individually. Each code carried a short label so we could tell them apart — a first name, or a number.
When a code is used we record three things against that label: the first time it was used, the most recent time, and how many times. That is the whole record. We do not record your IP address, your browser, the page you came from, or anything at all about what you enter in the full plan. The record exists so we know which invitations have been taken up.
Nothing in section 2, 3 or 4 changed during the beta. Household figures, saved plans and paystub images stayed in the browser exactly as described there, and the access code gave us no way to see them. What the record does show is that a labeled code was used, and how often. Because we handed each code to a particular person, we may be able to associate its label with that person. It tells us nothing whatever about their plan.
When the beta ends the codes stop working and the record is deleted. If you would like the entry for your code removed sooner, ask us at the address below.
15 Feedback you choose to send
Every page of the website and the full plan has a Send feedback to the creator button. It lets you tap the part of the page your note is about and write what was confusing or wrong. Notes are kept in your browser until you press Send and confirm; nothing is sent before that, and nothing is sent at all if you close it instead.
What is sent when you press Send. The notes you wrote and the tag you chose for each; the sentence on the page each note is about, with dollar amounts and percentages replaced by “$…” unless you tick the box to include them; the address of the page without anything after a ? or #; the width of your screen; and a short description of where on the page the sentence sits. If you turned on the optional route record and tick the box to include it, the list of pages and setup steps you visited, roughly when, which fields showed an error (by their printed name, never what you typed), and your screen size. Whether you ticked each of those boxes. The name you typed in the panel, if you typed one, so your notes can be told apart. An email address, only if you type one, so we can reply. Leave both blank and the feedback carries no name or email address.
What is never sent. Your plan, your saved versions, any figure you entered, any paystub, and anything typed into the page other than your notes. Section 2 is unchanged by this.
Where it goes. To our own site at plan.thehousingmodel.com, which emails it to hello@thehousingmodel.com through Resend, the provider we use to send email, and keeps no copy of it. To limit abuse, our server keeps your connection’s address (for an IPv6 address, the network part of it) in memory while it counts requests, and lets it go once ten minutes have passed since the last one it counted, the next time it answers a request. It never writes it down or sends it anywhere. As with any request, the hosting company sees your IP address while delivering it (section 5). The email stays in our inbox. If you sent feedback with your email address and would like it deleted, ask us at the address below.
Contact
Brooks Digital Ventures LLC — hello@thehousingmodel.com