Privacy

Domus Day does not ask for an account, and reading a guide requires nothing. The residency calculator runs entirely inside the browser: the answers are held in the browser’s own session storage and are not transmitted anywhere. Page analytics runs through Firebase, which counts visits and where people stop reading; advertising signals are switched off. One other thing is stored, and only when it is typed in and submitted deliberately: an email address, given at the end of the calculator in exchange for a fuller comparison.

The calculator asks about a move — the states involved, timing, and bands rather than exact figures. Those answers are written to sessionStorage, which the browser clears when the tab closes. They are deliberately not written to persistent local storage, and they are not sent to a server: the calculation happens on the page.

Exact amounts are never requested. The questions offer ranges, every money question can be skipped, and the estimate appears on screen before an address is asked for.

The calculator ends with an offer to send a fuller comparison by email. Submitting an address stores it. Nothing is stored until the send button is pressed — leaving the page, or closing the tab, leaves nothing behind.

What a submission records, in full:

• the email address as typed;
• the two state codes of the move, where the calculator knew them;
• which branch of the questionnaire was taken;
• the banded answers — the range chosen, such as “under $100k”, never a figure;
• the date of first contact.

What it does not record: the estimate itself, or any amount computed from the answers. Exact income and net worth are never asked for by the questionnaire, so neither exists to store. This is enforced rather than promised — the endpoint validates against a closed schema and rejects a submission carrying any field not on the list above.

The address is used to send the comparison, and for nothing else. It goes out once, in answer to the request that supplied it; there is no newsletter and no sequence behind it. Every message carries a postal address and a one-line way to stop, and replying with “unsubscribe” removes the address. It is not sold, rented, or shared for anyone else’s marketing. There is no advertising on this site.

To see what is held against an address, or to have it deleted, write to contact@domusday.com from that address. Deletion removes the record entirely rather than flagging it, and needs no reason.

This site uses Firebase Analytics, which is Google Analytics. It records which pages are read, how people arrive, and roughly where they are — country and region, from the network address, which is not itself retained by this site.

Advertising signals are switched off.Ad storage, ad personalisation and ad-user-data are all denied before the library starts, so no advertising identifier is written and nothing collected here feeds Google’s ad products. There is no tag manager, no advertising pixel, and no session recorder — nothing replays what happens on screen.

The calculator additionally reports which question was answered or skipped, which branch was taken, and when the email step was reached. Those events are defined so that they cannot carry a financial detail: they hold question identifiers, section names and branch names, and the type has no field capable of holding an answer, a band, or a computed figure. The estimate itself is never sent.

Firebase Analytics writes an identifier to the browser so that repeat visits are counted as one reader rather than several. It is used for measurement only, and it carries no advertising identifier.

The calculator writes its answers to sessionStorage, which is not a cookie, is never sent with a request, and is discarded when the tab closes.

Browser-level controls work here: blocking cookies, or any content blocker, stops the analytics library loading. Nothing on this site depends on it, and every page reads normally without it.

Pages are static. Fonts are served from the site’s own domain rather than a font CDN, and the national map is drawn from boundary data compiled into the site at build time — so reading a guide does not call out to a third party.

Three third-party services handle data. Two are Google: submitted email addresses are stored in Cloud Firestore, and page analytics runs through Firebase Analytics. The third is Twilio SendGrid, which delivers the report — an address given at the calculator is passed to SendGrid so it can send the message, and is held there as part of that delivery record.

Nobody else receives any of it, and none of it is sold or shared for anyone else’s marketing. The Firestore collection is closed to browsers entirely by a rules file — the only path that can write to it is this site’s own server.

Guides link out heavily to state statutes, regulations, and revenue department publications. Following one of those links is a visit to that agency’s own site, under its own privacy practices.

Residents of states with consumer privacy statutes — California among them — have rights to know what is held about them, to have it deleted, and not to have it sold. Those rights are honoured here for everyone who writes in, regardless of which state they live in, because the alternative is asking people to prove residency in order to exercise a right, and the list is short enough that there is no reason to.

Nothing here is sold or shared, so there is no sale to opt out of. Requests go to contact@domusday.com.

This site is written for adults dealing with a move between states and is not directed at children. No address knowingly belonging to a child under 13 is kept; if one reaches the list, writing to the address above has it removed.

Every claim above describes how the code behaves rather than an intention, and each one is noted in the source so that changing the behaviour forces changing this page. If collection begins, this page is updated in the same change that begins it.