Cookie Policy
Effective Date: 01-Jan-2025
Last Updated: 01-Sep-2026
What are cookies?
This Cookie Policy explains what cookies are, which ones Bitsaga uses, what they are used for, and how you can refuse or delete them.
Cookies are small text files that store small pieces of information. They are placed on your device when a website loads in your browser. Some are needed for a website to work at all, such as keeping a shopping basket together. Others count visits, so that Bitsaga can see which pages are worth writing.
A browser can also store data without cookies, in what is called local storage and session storage. It is not a cookie, but it is still something kept on your device, so this policy describes it too.
The short version
- bitsaga.be, this website, sets no cookies at all, and that includes the shop at bitsaga.be/shop. There is nothing to accept, so you are shown no cookie banner.
- A few pages do keep data in your own browser, without cookies. Your basket and your delivery details are the main ones. They stay on your device.
- One thing leaves this website: if you choose to pay by card or PayPal, checkout sends you to a separate payment page that does set cookies.
bitsaga.be, this website
This website sets no cookies of its own, on any page.
Visits are counted by Matomo, the visitor statistics software that Bitsaga hosts on its own server at analytics.bitsaga.be. Matomo is configured with cookies switched off, so it stores nothing on your device. Your visit is not sent to Google, to an advertising network or to any other third party, and Bitsaga does not sell or share it. There are no advertising cookies on this website. That is why you are not shown a cookie banner here.
What this website keeps in your browser
Some pages need somewhere to keep your basket or your progress. They use browser storage instead of cookies. Nothing listed below is sent to Bitsaga by itself, and you can delete all of it at once by clearing site data for bitsaga.be in your browser.
| Where | What is stored | How long |
|---|---|---|
| /shop/, the shop and its checkout | Local storage, under the keys cart, wooToken and addr, plus lastOrder in session storage. Between them they hold what is in your basket, the reference that ties that basket to the shop, and the delivery details you typed in: name, email address, street, postcode, town, country, telephone number, VAT number and any note. They are kept so that you do not have to type them again. The details you type are of course also sent to Bitsaga when you place the order, because otherwise the parcel cannot be addressed. | Basket and details until you clear site data, the order reference until the order is placed, the last order until you close the tab |
| /seedsigner-simulator/ | Session storage, under keys beginning sim-milestone:. It records which explanations you have already been shown, so that reloading the simulator does not repeat them. | Until you close the tab |
| /td/, the Freedom TD game | Local storage, under the keys abratd_name, abratd_anon, abratd_run, abratd_scores and mazeTD.research.v1. Between them they hold the name you type in, a random handle if you type none, an unfinished game so you can resume it, your high scores and your upgrades. There is no account and no server: the scoreboard is yours alone. | Until you clear site data |
If you would rather leave nothing behind, use a private window. Everything above disappears when you close it, and the shop still works.
Content loaded from other companies
Some pages on bitsaga.be embed videos through youtube-nocookie.com. Nothing is stored until you start a video. From that moment Google may store data on your device under its own policy, which Bitsaga has no access to and no control over.
Most of this website loads its typefaces from the Bitsaga server, but a few of the longer articles still load them from fonts.googleapis.com and fonts.gstatic.com. Google sets no cookie for this, but it does see your IP address when it serves the font.
Paying
Everything above this line is cookie-free. Below it is the one place in the whole of Bitsaga where a cookie is set, and you only reach it by choosing one particular way to pay. Reading an article, browsing the shop, filling a basket and paying with bitcoin never go near it.
Bitcoin, Lightning or bank transfer. You stay on bitsaga.be the whole way. The bitcoin payment runs on BTCPay Server, which Bitsaga hosts itself. No cookies are set.
Card, PayPal, Google Pay or Apple Pay. Bitsaga does not process cards itself, so this option hands you over to a second address, shop.bitsaga.be, and from there to PayPal. That address used to be the full Bitsaga webshop. Today nothing links to it and nobody browses it: it is kept running to take card payments, and that is the only thing it still does. If you pick this option your browser does load it, and unlike bitsaga.be it does set cookies.
Two of them are needed to take the payment. The rest are measurement tags left over from the years when that address really was the shop. They were never removed, so they still run on the payment page, and this policy would rather name them than pretend they are gone:
- WooCommerce and WordPress cookies, which hold the basket and the order while it is being paid for. Without them the payment cannot be completed.
- Google Analytics and Google Ads tags. These run under Google Consent Mode, which sets every storage type to denied for visitors in the European Economic Area, the United Kingdom and Switzerland, Belgium included. In that state Google does not write its _ga and _ga_* cookies. Outside those countries the denied default does not apply and they are set for two years.
- HubSpot, which recognises a returning visitor and records the checkout pages you pass through. It sets hubspotutk, __hstc, __hssc and __hssrc, with lifetimes HubSpot sets and can change. The Google setting above does not cover it.
- Ahrefs Web Analytics, a visitor counter that uses no cookies, and WonderPush, a push notification service that stores nothing unless you allow notifications from that address.
Once you reach PayPal you are on PayPal's own website, under PayPal's own cookie policy, which Bitsaga has no control over.
Choosing bitcoin, Lightning or bank transfer avoids all of the above.
Refusing or deleting cookies
To stop Matomo counting your visits to bitsaga.be, use the Bitsaga analytics opt-out page. It takes one click and it needs no account. The refusal itself is then remembered by a single cookie whose only content is that you said no.
To stop the Google tags on the card payment page, and everywhere else you browse, install the Google Analytics opt-out add-on.
To stop HubSpot tracking you across the sites that use it, set the HubSpot opt-out in your browser.
Every browser can also block or delete cookies itself, and clear the local storage described further up. Listed below are the support pages of the major browsers:
If you are using any other web browser, please visit your browser's official support documents. Note that blocking cookies on the card payment page stops a card payment from completing.
Questions
Write to contact@bitsaga.be. This policy is checked against what the website actually loads, and the date at the top is the date of the last such check.
Cookie Policy · Effective Date: 01-Jan-2025 · Last Updated: 01-Sep-2026