Privacy

Nothing is collected. The analytics library is not even downloaded unless you have accepted. Decline and nothing is sent, and the calculator works exactly the same.

Your choice is remembered in your browser, so if you accepted once, analytics load on your next visit without asking again.

We send your calculation to PostHog, an analytics service, so we can see which states and situations people are using this for. That includes the figures you typed: what you won, what you lost, your other income, your other itemized deductions, and the federal, state and total tax we worked out. It also includes your state, filing status and tax year, which screens you filled in, whether you finished the year up or down, whether you used the losses estimator, a rating of none, moderate or severe for how far your state taxes winnings that your losses cancel out, and whether that hit you on this return.

We also send a short event when you start a calculation and when you open one of the optional sections. Each one carries your state, and the page you are on or which section you opened.

Those are real amounts, not ranges. We send a band alongside them for grouping, but the amount itself is what the event carries. We send the amount, not only the band, because the band hides the cases we most need to see.

If you use the “I don’t know my losses” estimator, we also send how much you had wagered, which is the figure that estimate is built from.

We also record every click and page view on the site, which is ordinary analytics. Each one carries the address of the page you are on. That matters here more than it usually would, because when you run a calculation we put what you entered into the address bar so you can share or bookmark the result. That covers what you won, what you lost, how much you had wagered, your other income, the winning spouse’s own income, your Social Security benefits, your other itemized deductions, the federal and state tax already withheld and your betting-day totals. It also covers your state, filing status and tax year, whether you are 65 or older and whether your spouse is, and whether you used the losses estimator. So all of that travels with those events as well.

Like most analytics, PostHog also records by default the page that sent you here, any campaign tags in the link, your browser, operating system, device type and screen size, and when you leave a page. It works out an approximate location from your connection. To tell one visit from the next, it keeps a random identifier in a cookie and in your browser’s local storage.

Your browser sends only this site’s name, and never the address with the figures in it, when you follow a link to somewhere else. We set that header rather than relying on your browser to default to it.

Those events reach PostHog through this site’s own address rather than theirs, so an ad blocker does not silently drop them. That is a delivery detail and not a way of hiding anything: the same events arrive either way.

PostHog is configured to store this in the United States. This is a setting we can change, so read it as what we do today.

We do not record your screen. There is no session replay, no heatmap, no record of clicks that do nothing, no error reports, no page timing or network data, and no recording of what you type before you submit it.

Your email address goes into our database. Beside it we store your state, a rating of none, moderate or severe for how far your state taxes winnings that your losses cancel out, whether that hit you on this return, whether you finished the year up or down, which screens you filled in, the page you signed up from, a random id tying your price answer to your email, and your price answer if you gave one.

Not your figures. Where the analytics carry the amount, this row carries a band rather than an amount, so what sits next to your email is “under $5,000” and not what you actually owe. We chose this because an email next to an exact tax bill is more sensitive.

If you accepted the cookie notice, joining also sends two events to PostHog: one when you join and one when you answer the price question. They carry your state, the rating above, your tax as a band, whether you finished up or down, the page you signed up from, and your price answer. They do not carry your email address or any amount.

If we cannot save your signup, we do not keep your email anywhere. You see an error and can try again. Our server log records that a signup failed, with the other details above but never your email address.

When we save a new signup, we may send ourselves a short notification in our team chat, which runs on Discord, that someone joined. It names your state, and holds no email address and no figures.

We do not sell anything to anybody. We do not run advertising.

We never write your IP address to a database or a log. If you submit the waitlist form, the server keeps it in memory to stop one machine flooding us. It is dropped when the server restarts, or sooner once ten thousand other addresses have arrived. It is not stored anywhere that survives either.

We do not prepare or file returns, and nothing here is tax advice. The calculator is an estimate.

Write to support@getkindworks.com and we will delete your waitlist row and look for the analytics events that match it. Those events hold no email address, so we can find them only by the time and details of your signup, and we may not find them all. You do not have to give a reason.

A lawyer has not read it. It describes how this site works, accurately and in full, which is a different thing from being a compliant privacy notice in any particular jurisdiction.