What a visit to this site leaves behind
What is recorded when you read a page here, why no cookies are set, how the self-hosted Umami counter works, and what the outbound redirect passes on.
Written by Rowan Sayer/Last checked:
Compiler of the operator records, working from published terms and licence registers
The site is made of pages you read. There are no accounts, no sign-in, no comment boxes and no forms to fill in, so most of the usual routes by which a website gathers personal information do not exist here.
Below is what does happen, from the moment a page is requested to the moment you leave through a link.
The request itself
To send you a page, the server has to receive a request, and that request includes your IP address, the address of the page, the time and your browser's user-agent string. Every website receives the same; it is how the reply finds its way back to you. Requests pass through a content delivery network on the way to the server, and it sees them in the same way.
Nothing you tell us is stored, because there is nowhere to tell us anything. The only way to send information is to write to the contact address, and a message sent there is an ordinary email.
The visit counter
Page views are counted with Umami, an open-source analytics tool that runs on the same server as the site. Its script is loaded from this domain under the path /arc/ and reports each page view back to the same path, so no outside analytics company receives the data and nothing is sent to Google.
The counter records pages rather than people: which page was opened, which page sent the visitor there, and basic details such as browser type, screen size and language. It sets no cookie, assigns no advertising ID and does not follow anyone across other websites. Its figures are read as totals.
If your browser or an extension blocks the script, every page works exactly as before.
Cookies and browser storage
The site's own code sets no cookies and writes nothing to your browser's storage. Language is not remembered between visits: the address decides it, with English at the root and Japanese under /ja.
Once you arrive on a casino's site, that site may set cookies of its own. That happens on its domain and under its privacy policy, not ours.
When you leave through a link
Buttons that lead to a casino go first to an address on this domain beginning with /go/. The server answers with a redirect to one commercial offer, Vave's, whichever button was pressed. That offer address carries a partner code so Vave can attribute the visit to this site. Nothing about you is added to it; it is the same address for every reader.
Search engines are asked not to index or follow the /go/ addresses, and the buttons are marked as sponsored in the page code.
Links to licence registers and regulators open those sites directly and pass on only what a browser normally sends when it follows a link. We sell no data, share none with data brokers and run no ad targeting; there is no personal profile on our side to sell or share.
Questions people ask
- Is Google Analytics used?
No. Visits are counted with Umami, hosted on the site's own server and loaded from this domain.
- Will the site work with trackers blocked?
Yes, completely. No page depends on the counter in any way.
- Does the site use cookies?
Not of its own. A casino you reach through a link may set cookies on its own site.
The home page ranks the best crypto casinos in Japan by what each operator publishes about itself, and explains how the register of crypto casinos in Japan was filtered.