Privacy

Short version: no account, no name, and nothing you type into a calculator ever leaves your browser. One signal can go to Meta after you have read for a while, so our ads can look for people like our readers; in Quebec or Europe (the EU and EEA countries, the United Kingdom and Switzerland) it is only sent if you say yes, and elsewhere a notice with a "No thanks" comes first, as described in full below.

Last updated October 30, 2026

What gets collected

Usage measurement

To know whether the Lab is worth building, we count how it is used. On your first visit the site stores a random identifier in your browser's local storage, along with the list of dates you have opened the site. That is how "did anyone come back on a second day" gets answered without a login.

Alongside that we record which kind of page was opened (board, player, card, results), and which controls were used (a market filter, a sort, a book selection, a position or games pill on a research table). Once per page it also notes when the page has been on screen for five and for fifteen seconds, when you have scrolled at least 200 pixels and when you have scrolled past half of it, so that a page that was read can be told from one that was only opened. On an arrival from one of our ads it also records whether the browser reported the page as visible or hidden at that moment, and every visit carries one of two words, "ad" or "site", so that paid arrivals can be read apart from everyone else; a browser that arrived from an ad keeps an expiry time in its own storage for seven days so that its later visits are grouped with that arrival, and that stored flag holds nothing else. The path of the page is recorded; the query string is not, because that is where a book choice or a search term would sit. When you arrive from one of our own ads, the browser sends the ad's name (which campaign, which ad), read from the address and reduced to plain letters; the address itself is still not recorded. The browser counts days on the site and days on the Lab separately, so that reading an article is not mistaken for using the product; the Lab day count rides along with each usage event, and the site day count stays in your browser. The browser also keeps a short note of the current sitting (when it began, whether a control was used, whether the Lab was reached), so that one engaged visit is counted once however long you stay; it expires after thirty idle minutes.

Email, if you give it

There is no email signup on the site at the moment, so no addresses are held. If that changes, this section will say exactly what is stored before the form goes up.

Feedback, if you write it

After a few days on the Lab the site may ask a few short, optional questions. No answers are sent until you press Send feedback; saying no or closing them sends no answers, and they are not asked again in that browser. The site does count, as usage events with no answers in them, that the invitation was shown and whether it was opened. Sending feedback or saying no thanks also adds one to a single count of responses kept at our host, so the questions stop once 100 people have answered or said no; that count is one number with nothing about who stored beside it (the one-hour flood check below is kept apart), and each browser adds to it once. Closing the questions adds nothing. Answers picked from a list (where you first heard about the site, and whether you would recommend it) are sent as one usage event, like the ones above. Anything you type into the text box goes somewhere else: it is sent to steezanomics.com itself, links and web addresses (including ones written with numbers or look-alike dots) are taken out, though a plain number such as 127.1 is left as typed (even with a port or path after it) and a few rare forms may get through, and it is stored with the minute it arrived and nothing more. No identifier, page address, visit dates or other answers are stored with it. It is kept in private storage at Cloudflare, our host, that only Steezanomics can read, and copied once a day to a private file on our own computer so we can read it. It is never sent to the analytics provider or published. It is deleted 90 days after it arrived: at our host automatically, and from our own copy at its next daily check.

So neither the box nor the count of responses can be flooded, each time you send feedback or say no thanks the server also keeps a hashed form of your IP address for an hour after its last use, to count how many came from it. The hash is not keyed with a secret, so it hides the address from a casual look rather than from a determined one; it is kept apart from the text and the count, never with them, and is gone after that hour.

Please do not type your name, email or anything about a sportsbook account. If you do, it is kept as typed until it is deleted. Write to the address under "Getting rid of it" with roughly when you sent it and what it said, and it will be deleted sooner.

What is never collected

Unless you type it into the feedback box yourself (see above), the site never collects:

• Your name, address, phone number, or date of birth
• Any sportsbook account, login, or balance
• Any bet you place, anywhere, including bets on props you found here
• Anything typed into the calculators, which run entirely in your browser and post nothing
• Payment details of any kind; there is nothing to buy

Cookies, and what leaves your browser

The site sets no cookies. The identifier and the visit dates live in local storage on your device. The identifier itself is not transmitted: what gets sent with a usage event is the Lab day count, not the id that produced it, so the analytics provider receives "this visitor's second day on the Lab" and never an identifier we assigned. Clearing site data for steezanomics.com deletes all of it and the next visit starts a fresh count.

If that ever changes, this paragraph changes with it and will name the provider receiving the identifier and what it is used for.

Who else sees it

The site is hosted on Cloudflare Pages, so Cloudflare processes requests and may log them for security and delivery, as any host does. Typed feedback is stored there too, as described above.

The site also runs Cloudflare Web Analytics, which Cloudflare injects into every page. It is cookieless and does not identify or follow you between sites, and it records the page address, the referring site, and coarse device and performance information. Because it is added by the network rather than by this site's code, the opt-out below does not stop it; a tracker-blocking extension does.

Usage events go to our own copy of Umami, an open-source analytics tool, running on a server Steezanomics rents from Hetzner in Germany (EU) at stats.steezanomics.com. Steezanomics runs it; Hetzner hosts the server and Cloudflare relays the connection to it, as it does for the rest of the site. The analytics data is not sold or shared beyond that. Umami records the page address, the referring site, and your browser, operating system, device type and country of origin. The country comes from Cloudflare's reading of your IP address; the address itself is not stored with the events. Its tracker sets no cookies. It is configured here to exclude query strings from the addresses it records, and to run only on steezanomics.com.

To measure repeat visits, our analytics server uses your IP address, browser information and a server secret to derive a pseudonymous visitor identifier specific to this site. We do not automatically reset this identifier each month, so visits with matching details can be linked across months without cookies; changes to your network or browser can create a different identifier. You can stop future Umami collection using our analytics opt-out.

On a sample of visits to the home page and the Lab board, we also collect click positions, scroll depth, page and screen dimensions, and times, linked to the same analytics visit. We send the page path without query strings or fragments, not page text or what you type. Session replay is off. The same analytics opt-out applies. We delete click and scroll records older than 30 days in a daily cleanup; encrypted backups retain them until those backups expire.

Like any web server, the stats server keeps an operational access log of the requests it receives, including IP addresses. The log is rotated daily and each entry is deleted about eight days after it was written, at most. Backups of the analytics data are encrypted; the server keeps its newest 14 daily backups and our own copy the newest 30, and older ones are deleted.

Meta, only after you have read

We run a small number of ads on Facebook and Instagram, and we would like Meta to show them to people who are like the ones who actually read this site. For that, this browser can send Meta one signal, the word "Reader", at most once per visit in a tab (a visit ends after thirty idle minutes or when the tab closes). The conditions, both needed: a page has been on screen for fifteen seconds, and you have also either used a control (a position filter on a matchup table, a market switch on a player page, saving a prop) or opened a second research page (the Lab, a player, the picks, the results, a tool). Someone who lands and leaves sends nothing and is shown nothing.

After those conditions are met, your browser may send Meta our site origin and a Reader event. The request also exposes connection and browser information, and Meta may use its own cookies or app context to associate it with you. It does not include our visitor identifier, the page path or query, or anything you type. It is a plain image request to facebook.com carrying our pixel id and the word "Reader"; we load none of Meta's code on this site, so nothing of Meta's reads the page. Our code sets no cookies; Meta may receive or set its own where your browser permits it.

Where you are decides which of two things you see. The first time, nothing is sent without a question or a notice with a "No thanks"; in later visits a notice already given stands until you say no. Where you are is read once per tab by our host from your connection, at that moment only, as a country and region code, with no page address attached, and is kept nowhere but in that tab; when the reading is missing or unclear, you are asked.

If you are in Quebec or Europe (the EU and EEA countries, the United Kingdom and Switzerland), a question appears at the foot of the page and nothing is sent until you answer "Yes". "No thanks" is remembered in this browser and the question does not come back; the Lab works exactly the same either way.

Everywhere else, a one-line notice appears at the foot of the page instead, with one button, "No thanks". The signal is then sent at the first of: your next control, your next research page, or fifteen more seconds with the page on screen, unless you pressed "No thanks" first. The notice is shown once per browser; after that, a later visit that meets the reading conditions sends the signal without showing it again. "No thanks" is remembered in this browser and stops every later send.

To stop it at any time: press the button below, and nothing more is sent from this browser; the analytics opt-out further down stops it as well. A browser that sends the Global Privacy Control signal is treated as having said no, without being asked or shown anything. Clearing site data clears your answer too, so the question or the notice can appear again. A tracker-blocking extension may prevent delivery; we never work around it. What Meta does with the signal is governed by Meta's Business Tools Terms, not by us. Meta may use its own cookies to recognise the browser for its ads; you control that on Meta's side in your ad preferences.

Stop sending the Reader signal from this browser

Email, if you give it, goes to the list provider that sends the newsletter. Nothing is sold, and nothing is shared with sportsbooks or advertisers beyond the one Meta signal described above.

Getting rid of it

Clear site data in your browser and the identifier and visit dates are gone. To have an email address removed, use the unsubscribe link or ask and it will be deleted. Typed feedback goes by itself after 90 days, from our host and from our own copy, or sooner if you ask. You can also ask what is held about you. Clearing site data removes the visit history stored on your device, but does not delete analytics already held on our server or necessarily change the server-generated identifier. It also removes this browser's opt-out setting, so set the opt-out again if you want collection to remain off. Write to privacy@steezanomics.com and it will be answered.

Turning it off

To stop the usage measurement on a device, run this once in your browser's console on steezanomics.com:

localStorage.setItem('umami.disabled', '1'); localStorage.setItem('sz.disabled', '1')

The first key is the one the analytics provider checks and the second is this site's own, the same pair the opt-out page below sets, so the one line stops both rather than half of them, and the site never mistakes your choice for one of its own. Nothing further is sent, and no visit dates are recorded on that browser either. It also turns off the feedback question, so nothing typed there is sent. It also stops the Meta Reader signal described above.

Turn off analytics for this browser. The home-screen app and Safari keep separate settings, so it has to be done in each.

It does not stop Cloudflare's edge-injected analytics described above, which this site cannot switch off from the page. A tracker-blocking extension does, and blocking is never worked around here.

Age

This site is for adults of legal betting age in their jurisdiction, 19+ in Ontario. It is not directed at anyone under that age and nothing here is knowingly collected from them.

Changes

If what is collected changes, the date at the top changes and the section describing it is rewritten before the change goes live, not after.