Privacy Policy for Readers of This Service
Falling Pickaxe is a static publication of 9 content pages plus its section and service pages, running since 2026 without user accounts, a comment system or a newsletter. It holds no personal data about readers beyond ordinary web-server logs, it sets 0 cookies of its own, and every screenshot of the game is a frame from our own recorded session. This policy lists the 4 log fields, what the 2 scripts on each page do, and how a reader in India, the European Union or the United Kingdom can ask about their data.
Table of contents
4 Fields the Server Logs Record
The server logs record 4 fields and nothing more: IP address, requested URL, user agent and timestamp. They exist for security and error diagnosis. No name, email address or payment detail is among them; the IP address is, and that is the one identifying value a log of this kind keeps.
| Log field | What it holds | Why it is kept |
|---|---|---|
| IP address | The address your connection presents, as the web server sees it | Blocking abuse and reading error reports; it is the one identifying value here |
| Requested URL | Which page was asked for | Finding broken links and pages that answer with an error |
| User agent | The browser and operating system string your browser sends | Checking that a layout fault is real on the device that hit it |
| Timestamp | The date and time of the request | Matching a reader request about their own visit to the right log lines |
Nothing is sold. Server logs here stay unsold and unmerged with anything else. They feed no profile, they stay inside this one site, and the pages ship without an analytics script, so a tracking pixel is simply absent.
In Short, What We Hold About You
Here's the honest summary: it's a web server log and that's all. There's no account, no newsletter and no advertising identifier, so there's very little to hand over even when you ask.
You'll still get a straight answer to a data request. If the log has already been discarded, the reply says exactly that, because an empty answer beats an invented one.
- Accounts
- None
- Cookies this site sets
- 0
- Analytics scripts
- None
- Server log fields
- 4 (IP, URL, user agent, time)
- Images site-wide
- All original, served from this domain
- Policy dates
- /
What Should You Do Before You Start Reading?
Three steps are worth taking before you start, and none of them needs an account anywhere. Browse the range of privacy settings your browser offers, then explore the operator policy for any casino you intend to visit.
- Check the privacy settings your browser already applies to this site.
- Read the operator policy that takes over once a redirect hands you across.
- Note the date of your visit if you plan to ask what the server kept.
How long an access log survives is the host's setting rather than ours. Doing this in advance matters, because a request arriving days later can only be answered honestly.
What Those Logs Leave Out
Every identifying detail is missing from those server logs: name, email address, payment record and gambling history are absent, because none of that is ever gathered here. That is a real limitation of what a data request here can return.
An operator account is a separate world with separate records. We can see a click leaving Falling Pickaxe and nothing after it.
Cookies, Local Storage and Logs
Cookies here number zero right now, and none are set by this site at all. Cookies stay absent from this policy for a simple reason: the site sets none, so the logs are the only record here. The 2 scripts each page loads rewrite the affiliate button address and add small conveniences such as copy link and back to top.
Neither script sends data anywhere, and the pages ship free of advertising tags. Our methodology for this site keeps the front end static, so a page offers nothing for a tracker to attach to.
Anything else a reader sees is ordinary browser behaviour. Neither script stores anything on the device: there is no cookie, no local storage entry and no session entry to clear.
Affiliate Redirects Beside the Logs
Beside the logs sits one outbound hop. Affiliate redirects are the only outside traffic in play, and that hop runs in two steps: this site records the click in a file of its own, then forwards the browser to the affiliate network that accounts for the commission. An outbound link to a gambling operator may pass through an affiliate redirect that records the click for commission accounting, and the terms of use explain that arrangement in full.
Once a reader lands on an operator or a regulator site, that site's own policy takes over. Casino domains are named here only where a public register lists them, and never as a recommendation, so the one affiliate link a reader meets is the play button; the rest lead to the maker's own pages and to the support services in the footer.
What a Redirect Passes On
The redirect provides a click record and nothing more. It includes no name, no email address and no payment detail, because this service collects none of them from you.
An operator supplies its own tracking once you arrive, and they answer for it under their own regulator. Compared to this site, which collects nothing, the notice at the far end of a redirect is the one worth reading. Their privacy policy governs everything after that moment, so you should read it before you register.
The weakness of this arrangement is visibility: we cannot see what an operator stores about you, and that limitation is stated instead of glossed over.
Third-Party Software and Embedded Content
No third-party software loads. Pages carry no video players, social widgets or advertising scripts, so opening one contacts no other server.
Every screenshot here is a frame from our own recorded demo session of the studio's client, dated in the manifest it is published from and served from this domain. The testing method page explains where those frames come from.
How Long the Logs Are Kept
Nobody here can state that window yet. Retention will belong to the host, not to us. Whatever window that host keeps, it will exist for security and error diagnosis instead of for analytics, and nothing gets copied out of it. Every log stays inside that single system, for every page this site serves.
The length of that window is the one thing this page cannot state: the host is not chosen yet, and inventing a number of days would be worse than naming the gap. It gets printed here the day the host is settled. So write early if you intend to ask about a specific visit, because the log may be gone before the question arrives.
Reader Rights over Those Logs
Reader rights over the current logs follow the privacy law of the reader's own country. In India that is the Digital Personal Data Protection Act; in the European Union and the European Economic Area it is the GDPR, and in the United Kingdom the UK GDPR together with the Data Protection Act 2018. Each of those grants more than there is anything here to answer: a reader may ask what data, if any, the server holds about their visits, and may request its deletion.
Write to the author through the contact page, name the approximate date and time of your visit, and the request is checked against whatever logs survive. To verify the answer, the author reads the server log directly. However, a log already discarded cannot be produced, and the reply says exactly that.
What Is Left Behind by a Deposit?
The complete list of what a deposit leaves here is empty. A deposit, a withdrawal or a bonus claim happens entirely inside an operator account under its own regulation, so none of it reaches this service. The about page sets out who is responsible for Falling Pickaxe.
The responsible gambling page explains that this site holds no gambling account data whatsoever, which is also why this desk cannot help with an operator balance.
Terms This Policy Uses
- Access log
- The line a web server writes for each request, holding an IP address, a URL, a user agent and a timestamp.
- Affiliate redirect
- A short link that records a click for commission accounting before sending the reader to the operator.
- Local storage
- A small store inside the browser itself, cleared from the browser settings and never read by this site.
- Data request
- A message asking what the server holds about a visit, answered against whichever logs still exist.
Does This Site Set Any Cookie?
This site sets no cookie of its own, and the pages load no analytics script, so a reader has nothing here to opt out of and nothing to clear afterwards.
An operator is a different matter once you leave. Their cookies, their tags and their retention rules take over the instant you land there.
Recap: This Policy Compared with an Operator
If you want a one-line answer, the operator policy is the better one to read. This one is short. Compared with an operator, this policy is short: the server logs 4 fields, the site sets 0 cookies, embedded content is absent, affiliate redirects record a click, retention belongs to the host, and a reader may ask what survives. That short list is the whole of the record.
This policy was first published on and changes only when the technical setup behind Falling Pickaxe changes; the current wording dates from . Because no accounts exist here, a change reaches readers through this page instead of by email.
This site takes no deposits and runs no identity checks; both stay off it entirely.
Related Reading on This Game
More on this game, from the same section first:
