About

What this covers

Whatever I am interested in and think is worth writing down properly: technology, money, crypto, the internet and how the things built on it actually work. So far that has meant security and protocol failures, personal finance, and the rules publishers and platforms have to live under.

I write about one thing at a time and try to cover it properly before moving on, rather than posting a little about everything. If a subject stops being interesting, I stop writing about it.

Some of it is first-hand. I run experiments — putting real money into a crypto position, trying a strategy, using a product properly for a month — and write up what actually happened, including when it loses. A report of what I did is not a suggestion that you do it: my circumstances are not yours, and nothing here is advice. The disclaimer says that in the language it needs to be said in.

The tools are the other half, and the part I most want to build. Some questions are not answered by reading — you need something you point at your own case and get an answer from. Those get built here rather than borrowed. Over time I would like there to be enough of them that they are the reason people come.

Who writes this

MoneyVision is written and maintained by Kush Binaku, whose full name is Kushtrim Binaku, working alone. There is no content team, no agency and no rota of freelancers. Full contact details, including a postal address, are on the contact page.

Nobody here is authorised or regulated by a financial regulator, and nothing published here is advice. Where a piece touches money, the disclaimer sets that out properly, and it is worth two minutes of your time before you use anything on this site to make a decision.

How the writing is made and checked

Every article is reviewed on its substance by a person before it is published, and that person holds editorial responsibility for it. Nothing is published straight out of a model, and a spell-check is not a review.

The process, stated so you can hold it to account:

• AI assistance is used, and disclosed. Language models help with research, first drafts, and the code behind the site and its tools. They decide nothing. Every factual claim, number and formula is checked against a primary source by a human before it goes out, and the human is the one answerable for the result.
• Claims are sourced. Where an article states a rule, a rate, a fee or a fact about how something works, it links to whoever set it or shipped it — the documentation, the specification, the regulator, the vendor — so you can check it rather than take it on trust.
• Dates are visible. Every article carries the date it was published and, where it has been revised, the date of the revision. In these subjects nothing is true indefinitely.
• Publishing rate follows review capacity. Articles should be published only when their claims, figures and sources have been reviewed.
• Corrections happen on the page. An error is fixed where it was made, and a material correction is noted there rather than quietly overwritten. If you find one, say so.

How the numbers and the tools are checked

Every figure the site works out comes from one shared library, so the same question gets the same answer wherever it is asked. It is covered by tests with values worked out by hand, including the awkward cases — a zero rate, a disposal larger than every acquisition, a conversion that cannot be represented exactly.

Where an article's figures are computed from inputs you can change, that computation happens in your browser. Edited example values can appear in the page address so the example can be shared. A tool that fetches other pages says what it sends on its own page. Every piece states the assumptions its model makes, because a model whose assumptions are hidden is worse than no model, and every output is an estimate rather than a settlement figure.

How this is paid for

Nothing yet. There is no advertising on this site at the moment. When there is, it will be advertising and nothing else, it will be marked as advertising, and no advertiser will see an article before it is published or have any say in what it says.

If any of that ever changes, it will be said on the page it affects rather than buried in a policy. What advertising would mean for your data is in the privacy policy.

What this site knows about you

There are no reader accounts. When measurement is configured, small first-party scripts send article-view or tool-use counts and page-performance measurements. The API stores daily totals and performance bands by page, rather than a history for each reader. These measurement payloads contain no reader identifier, referrer or input values.

Browser storage remembers your appearance and advertising choices. Contact messages, server logs and advertising have their own data handling, described in the privacy policy.

Get in touch

Corrections, questions about how a figure was worked out, and anything else: the contact page.