What this site stores, and what it never asks a reader for

This page sets out, in plain terms, what information this site holds and what it will never request from you. The short version is that this site is a research and reference publication: it models, calculates and cites, and it does not take bets, run games or hold any kind of wagering account. Below is the detail, including the technical footprint any ordinary website leaves and the steps you can take if you want something corrected or removed.

What this site does, and what it deliberately does not do

This is a publication, not a product you log into. Every page you can read here is available on the same terms to every reader. The site models odds and returns, works through the arithmetic behind a market or a promotion, and cites the public sources it relies on so that a reader can check the working. That is the whole purpose of the operation. There is no game to play on this site, no spin, no simulated round and no live market to join. The site does not test products on a reader's behalf, does not run trials for a reader, and does not act as an intermediary between a reader and any operator.

It follows that the site holds no gambling account data of any kind. There is no reader betting balance stored here, no wagering history, no deposit or withdrawal record, no loyalty tier and no account statement. If you have an account somewhere else, that account lives with that other business, under that business's terms and its own data practices. Nothing about it is mirrored, copied or referenced in a file held on this site, because the site has no mechanism to receive it in the first place.

The distinction matters because a reader who arrives from a search engine may reasonably expect a site that talks about markets to be a place where money moves. This one is not. It is closer to a statistical almanac with footnotes: numbers, method, sources, and a clear statement of what the numbers do and do not imply. Everything the site stores is consistent with that role, and nothing it stores would be useful to someone trying to access an account, a wallet or a payment instrument.

Information this site never asks a reader for

The clearest way to describe the site's data posture is by listing what it will never request. The site never asks for a card number, including the long number, the expiry date and the security code on the back. It never asks for a bank login, an online banking customer number, a password, a one time code sent by a bank, or any other credential that would open a financial account. It never asks for a wallet credential of any kind, whether that means a wallet address, a seed phrase, a recovery phrase, a private key or a wallet password. It never asks for a copy of an identity document such as a passport, a driver licence or a birth certificate, and it never asks for a selfie holding one.

It also does not ask for the surrounding material that identity checks usually require: a date of birth combined with a residential address, a tax file number, a Medicare number, a utility bill, a bank statement or a proof of address. None of these have any use in modelling a market or checking a citation, so none of them are collected. If a page on this site ever appeared to request any of the items above, it would be a fault or an impersonation, and the correct response is to close the page and report it using the contact route described at the end of this article.

The same applies to reading itself. No newsletter sign up is required to read a page, no account creation is required, and no paywall stands between a reader and the reference material. There is no member area, no saved watchlist tied to a login and no profile that a reader has to maintain. A reader can arrive, read, follow a citation and leave without identifying themselves in any way. The site is built on that assumption and does not quietly undermine it elsewhere.

One further point about requests for information. The site does not run surveys that ask about a reader's income, debts, spending, gambling habits or financial circumstances, and it does not ask a reader to upload a document of any kind. Any message that claims to come from this site and asks for those things did not come from this site. Correspondence with the site is described in the final section, and the only thing genuinely useful in a message is a clear description of the error and the page it appears on.

What a normal web server logs, and why

Like every website on the public internet, this one is served by a web server, and that server keeps a technical log of requests. The log records the page or file that was requested, the date and time of the request, the address the request came from, the browser and operating system identified in the request, the address of the page the reader came from if the browser supplies it, and whether the request succeeded or failed. This is standard machinery rather than a choice made by this site. A server that did not keep such a record could not diagnose a broken page, block a flood of automated requests, or tell whether a caching layer was working.

The purpose of the log is operational. It is used to keep the site available and correct: to find a page that returns an error, to notice a sudden spike of traffic that is degrading service for everyone else, to confirm that a change to the site was deployed as intended, and to investigate abuse such as an automated attempt to overwhelm the server. It is not used to build a profile of an individual reader's interests, and it is not sold or traded as a marketing list, because it is not a marketing list and does not contain the kind of detail such a list would need.

Logs are retained for a limited period consistent with those operational needs and are then discarded or aggregated. Aggregated figures, such as how many requests a page received in a month, may be kept for longer because they no longer identify a single visit. An address on its own is not a name. It can, however, be linked to a household by an internet provider that holds the connection records, which is why the site treats log data as sensitive operational material rather than as anonymous trivia, limits who can read it, and does not attach it to anything a reader has written or sent.

Readers who use a privacy tool that masks their address, or who browse through a shared network, will appear in the log in a form that says little about them. That is fine. The site does not attempt to defeat such tools, does not fingerprint a browser to recognise a returning reader, and does not maintain a persistent identifier that follows a reader across pages after the visit has ended. The log exists to run the service, not to remember people.

Cookies this site sets, and cookies it does not control

A cookie is a small text file that a site asks a browser to store and send back on later requests. This site uses a minimal set. There are cookies needed for the site to function, such as one that records a preference you have explicitly chosen or one that helps a form submission succeed without being repeated. These are limited in scope, hold no financial information, and exist to make the page work rather than to track a reader around the internet. Where a cookie is not strictly needed, the site aims to set it only after a clear choice has been made.

Beyond that, there are cookies that this site does not set and cannot read. If an advertiser, an analytics service or a linked page places a cookie, that cookie belongs to that other party and is governed by that party's own notice and its own choices. A reader who follows a link off this site may well pick up cookies from the destination before reading a word of it. The site can describe this, but it cannot switch those cookies off on another business's behalf, and it does not pretend otherwise. The practical control sits with the reader's browser, which can block third party cookies, clear stored data and set a preference to ask before storing anything.

It is worth separating the two categories in your own mind. Cookies set by this site concern the functioning of these pages. Cookies set by someone else concern that someone else's service, and their purpose may be advertising, measurement or something a reader did not anticipate. If a page you reach from here behaves in a way you dislike, the right place to raise it is with the business that runs that page, because that is where the data is being collected and held. The site's own cookie footprint is deliberately small and does not include a reader's financial details, because the site never receives them.

Following a cloak path, and where your data goes next

Some pages on this site link out to an operator's own site, and the link may pass through a redirect that records that the click came from here. This is sometimes called a cloak path. When a reader follows such a path, they leave this site. The redirect itself carries only the fact of the click and the destination, not a name, a card number or an account. From the moment the destination loads, the reader is on the advertiser's own page, under the advertiser's own terms, its own cookie practices and its own record keeping.

That handover is the important part. Once you are on the destination page, what is collected about you is decided there, not here. The destination may ask for information that this site would never ask for, and it may set cookies that this site never sets. A reader should read the destination's own notice before providing anything, and should treat a request for a card number, a bank login or an identity document on any site as a decision worth pausing over. This site's role in that journey is limited to the link and the fact that it was followed. It does not see what you do after you arrive.

There is no obligation to follow any outward link. Every link on this site is there because it is relevant to the modelling or citation on a page, not because a reader is expected to act on it. A reader who never leaves this site can use all of the reference material. If you do follow a path, do so with the same ordinary caution you would apply to any unfamiliar page, and remember that the destination's practices are the destination's responsibility, not something this site can vouch for or amend.

Asking for a correction or a removal

If you believe a page on this site contains an error, an out of date figure or a citation that misrepresents a source, you can ask for a correction. The most useful message names the page, quotes the passage, explains what is wrong and points to a public source that supports the change. Corrections are reviewed against sources and the arithmetic on the page. If the working was wrong, it is fixed and the page is updated. If the working was right but unclear, the wording is improved. A correction request does not require you to identify yourself beyond a way to reply, and the site does not ask for a document to prove who you are.

If you have sent something to the site and want it removed, you can ask for that too. Because the site does not run accounts, does not take payments and does not hold financial details, the material a reader might have sent is usually a message: a question, a correction, a note about a broken link. A removal request is acted on by deleting that message and any reply thread attached to it, subject only to the need to keep a minimal record where a legal obligation requires it. You do not have to give a reason, and you will not be asked for a card number, a bank login or an identity document in order to have your message erased.

Requests are best made once, clearly, through the contact route named on the site's own contact page. Include the page address and the specific words you want changed or removed, and a reply address if you want an answer. Do not send sensitive material such as a card number, a password, a wallet seed phrase or a copy of a passport in support of a request, because none of it is needed and the site will not use it. If you are unsure whether something you sent is held, ask, and the answer will be given plainly. The site would rather delete a message it does not need than keep one a reader has asked it to release.

Questions about data

Does this site hold my betting account or my balance?

No. This site models, calculates and cites. It holds no gambling account data of any kind: no balance, no wagering history, no deposits or withdrawals and no loyalty record. Any account you have with an operator lives with that operator, under that operator's own terms and data practices. Nothing about it is stored here.

Will I ever be asked for a card number, a bank login or a wallet credential?

No. The site never asks for a card number, a bank login, a one time bank code, a wallet address, a seed phrase, a private key or a copy of an identity document. It has no use for any of them, since it does not take payments and does not run accounts. A message that asks for those things while claiming to come from this site did not come from this site.

What does the web server record when I read a page?

An ordinary technical log: the page requested, the date and time, the address the request came from, the browser identified in the request, the referring page if supplied, and whether the request succeeded. It is kept for a limited period to keep the site available and to investigate abuse, and it is not used to build a profile of an individual reader or sold as a marketing list.

Which cookies does the site set, and which does it not control?

The site sets a minimal set of cookies needed for pages to function and for preferences a reader has explicitly chosen. Cookies set by an advertiser, an analytics service or a page reached by a link belong to that other party and are governed by its notice. Those cannot be switched off by this site, and the practical control is in your browser settings.

What happens to my data if I follow a link to an operator's page?

You leave this site. The redirect records that a click was followed and the destination, not your name or any financial detail. Once the destination loads, that business decides what it collects, so read its notice before providing anything. This site does not see what you do after you arrive, and no outward link needs to be followed to use the reference material here.