Privacy policy
Last changed 24 October 2026
The short version.
- There is no account, no sign-in and nothing to register.
- Pikefall’s own code sets no cookies and gives you no identifier of any kind.
- The game shows ads from Google, which asks your consent where the law requires it; see Advertising.
- This site uses Google Analytics, which sets cookies and asks your consent first; see Google Analytics.
- Your campaign is saved in your own browser and is never uploaded.
- Anything this site sends is listed below, field by field.
Who is responsible
Liviusz Lovasz,
Humperdinckstraße 7
80807 München
Germany
(also in the Impressum).
You can reach them about anything on this page at
[email protected].
What stays in your browser
The game keeps its save in your browser’s local storage, on your device. It is not a cookie, it is never sent to any server, and nobody but you can read it. The landing page reads it too, to show your own progress on the campaign chart, and changes nothing in it.
| Stored as | What it holds |
|---|---|
pikefall.save.v1 |
Your campaign: stars and results per map, unlocked heroes and doctrines, your loadout, sound, music, graphics and speedrun-timer settings, which tips and story pages you have seen, honours, the coat of arms and tower colours you chose, the in-game crowns, endless records, your last run (so it can be shared from the map, together with its replay — the same code a replay link carries, kept until your next run replaces it), the name you last signed a challenge with, how ads are spaced where the game shows any, and any licence key you redeemed, with a note of which keys have already paid their crowns. A key is checked on your device against a public key built into the game; it is never sent anywhere. |
pikefall.maps.v1 |
The maps you drew in the map editor, if you have drawn any: each map, its title, the name you signed it with when you shared it, whether you have shared it, the day you made it and the day you first shared it, and the replay of your own win on it (your clear — the same code the “author’s clear” link carries). Beside them, the maps you received: each map you opened from somebody else’s link, the name it was signed with and the day it arrived, so it is listed under My Custom Maps on the world map, where you can remove it. All of it is kept apart from your save, so starting over does not delete the maps you drew or the ones you received. |
pikefall.save.backup |
A copy of the above, taken only before the game does something that could lose it, so a damaged save can be recovered. |
pikefall.consent.v1 |
Your answer to a consent question, if you have been asked one, and which services it covered, so you are not asked again. See Cookies and consent. |
This storage is what makes the game save at all, which is the service you asked for by playing it, so it needs no consent. Clearing this site’s data in your browser deletes all of it, and your campaign with it; the game’s own options also have a “start over” control, which keeps any licence keys you redeemed and the maps you drew, and deletes everything else. The map editor’s own Delete takes one map off your shelf.
Purchases
Remove Ads and the Cosmetic Pack are sold through Stripe’s managed
payments service, under which Stripe’s Link is the seller of record:
it takes the payment, handles tax and is the party your purchase contract
is with. What you enter on its checkout page is governed by
Stripe’s own privacy policy.
When you have paid, Stripe sends you back to this site’s
/claim address with a reference to your order. Pikefall’s
server asks Stripe whether that order is paid and what it was for, signs
a licence key and opens the game with it. No e-mail is sent, and none is
kept: the key reaches you in that page.
The key holds a reference derived from the order, what was bought and when — not your name, e-mail address or card. The game checks it on your device and keeps it in the save described above. Nothing is sent when you play, so Pikefall cannot tell where or how often a key is used.
If you lose the key, /recover gives it back. You enter the e-mail address you paid with and the receipt or invoice number from Stripe’s receipt; they are used once, to look the order up at Stripe, and are not stored — the only place they are written back is that page itself, which is not cached. Both are needed: an e-mail address alone finds nothing. The same page offers a refund for 30 days after purchase, unless the purchase has already been refunded, and asks you to confirm the item and the amount before Stripe is told to pay it back. A refunded key keeps working; nothing is revoked.
Cloudflare’s logs of the server’s requests, kept for a limited
time so errors can be found, include the /claim address and
so the order reference in it; the e-mail address and receipt or invoice number are
sent in the body of a form and do not appear there. The legal basis is
the performance of the purchase contract (Art. 6(1)(b) GDPR).
Hosting
The site is served by Cloudflare Pages, run by Cloudflare, Inc. Like any web host, Cloudflare has to process your IP address and the details of each request (the address asked for, your browser’s user agent, the time) to deliver the pages and protect them from abuse. Pikefall’s own code never reads, stores or logs your IP address. The legal basis is the legitimate interest in running a website at all (Art. 6(1)(f) GDPR); Cloudflare’s own handling is described in its privacy policy.
The site loads no fonts, images or styles from anybody else: every picture on it is drawn in your browser by the game’s own code. It loads no scripts from anybody else either. The game’s ad script, described under Advertising, is loaded from Google. The visitor-count script, described under Visitor counts, is loaded from Cloudflare once you allow it. The Google Analytics script, described under Google Analytics, is loaded from Google once you allow it.
Data outside the EU
The services named on this page — Cloudflare, Google, Google, Stripe — are run by, or belong to, companies in the United States, so what they process to serve this site may be handled there. Each is certified under the EU–U.S. Data Privacy Framework, which the European Commission has found to give an adequate level of protection (Art. 45 GDPR), and also relies on the Commission’s standard contractual clauses (Art. 46(2)(c) GDPR).
Gameplay statistics
To find out how hard the maps really are, the game sends a short message when a battle ends, and another if your device turns the graphics quality down because it is running slowly. To find out what its advertising costs the game in players, it also sends one each time an advertisement ends and each time a results card offers Remove Ads. These are all the fields there are:
- When a battle ends: which map, the difficulty, the mode, whether it was won or lost, the stars earned, the wave reached, how many waves the map has, how many seconds of game time it lasted and which hero you took. Not sent for a replay you watch or a challenge you answer.
- What you built, with the same message: a count of each tower type built, each tower level reached, each tower branch and ability bought, and each spell cast. Counts only: not where, not in what order, and nothing that could replay your battle.
- Where from: the country Cloudflare reports for the request, as a two-letter code. The server does not read your IP address; Cloudflare derives the country from it before the message arrives.
- When quality drops: the quality level before and after, and the frame time that caused it.
- When an advertisement ends, or Remove Ads is offered: where it was offered (after a results card, for crowns on the map, to double a Daily Orders payout, or the Remove Ads line on a results card) and what came of it (shown, none available, closed early, or an error).
- When you share something: which kind of thing went out (a results card’s picture, a replay link, a challenge link, a map link, the Daily Orders text or a saved clip) and how it went out (through your system’s share sheet, the clipboard, a download, or not at all). Not the picture, the link or the text: only the kind and the way.
- When a shared link brings you here: which kind of link it was (a results card, a challenge, a replay, a map), or none for a plain visit to the landing page. Sent once per visit, and only by that page.
Nothing else is sent: no cookie, no identifier, no session, nothing that could connect one message to another or to you. The receiving server, a Cloudflare Worker, does not read your IP address and stores at most those fields, as counters. Cloudflare keeps that server’s operational logs for a limited time so errors can be found; Pikefall writes nothing about you into them. The legal basis is the legitimate interest in balancing the game and in knowing what its advertising costs it (Art. 6(1)(f) GDPR).
None of these is sent unless you allowed gameplay statistics — the game asks the first time you open its map, and this site’s pages ask too; one answer covers both. A player who has not answered is not counted. The legal basis is your consent (Art. 6(1)(a) GDPR and Art. 5(3) of the ePrivacy Directive, in Germany § 25(1) TDDDG), which you can withdraw under Cookies and consent.
Sharing a result
When you share a result, the picture is drawn on your device and handed to your system’s share sheet, clipboard or downloads folder — Pikefall uploads nothing of the picture, the link or the text. The only thing it counts is that something went out, and the way it went, as described under gameplay statistics. The link that goes with it carries a short code describing the run and nothing else: the map, the difficulty, the stars, the wave reached, lives lost and the mode. It contains no name, no identifier and no time, and anybody holding the link can read it, which is why it holds nothing worth keeping private.
A replay link is that link with a second, longer code after a
#: the replay. It carries what the battle needs to be played
again and nothing more — the map, the difficulty and mode, the hero,
the Armoury cards and spells you marched with, the battle’s random
seed, every order you gave with the moment in the battle you gave it, and
the result it reached. It contains no name, no identifier and no date. The
part after the # is a fragment, which your browser never sent
to any server, ours included; the game reads it in the page. Watching a
replay writes nothing to your save.
A challenge link is the same replay under a different name —
#c= rather than #r= — and carries the
same things, plus one: the name you choose when you send it, so your
friend knows whose run they are beating. It is whatever you type, up to
twenty letters, numbers and spaces; it need not be your real name, and
like the rest of the fragment it never reaches a server — it is
shown only inside the game, to whoever opens the link. Whoever opens it
plays the same map, difficulty, mode, hero and seed with their own
Armoury cards, and is then shown both results side by side. A challenge
on a map somebody made carries that whole map, as a map link does, and,
if its maker signed it, the name its maker signed it with, under the same
rules as yours; it has no card part, so it opens on the front page, and
the same goes for a replay of a run on such a map, which carries no name
at all. Answering a
challenge, won or lost, writes nothing to your save: no stars, no
unlocks, no record of it. Nothing about a challenge is sent anywhere
— not the link, not the name, not either result — when you
open, play or answer one. The one message
playing one can cause is the quality drop described under
Gameplay statistics, if your device turns the
graphics down while you play; it says nothing about the challenge.
A map link carries a map somebody made — its roads, water, scenery,
starting lives and gold, its waves and the version of the game it was made
on — after #m=, and, if its maker chose one, the name
they signed it with, under the same rules as a challenge’s name. It
contains no identifier and no date, and like every fragment it never
reaches a server. Opening a map link keeps a copy of the map on your
device, with the name it was signed with and the day it arrived, so you
can find it again under My Custom Maps; it is stored as described
above, never sent anywhere, and you can remove it
there. Playing it, won or
lost, writes nothing to your save — no stars, no crowns, no record
— and nothing about the map or the result is sent anywhere. As with
a challenge, the one message playing one can cause is the quality drop
described under Gameplay statistics; it says
nothing about the map.
When you share a map you drew, the game asks for the name to sign it with and copies its map link; the name is kept with the map in your browser, as described above, and nowhere else. A map can only be shared once you have won it yourself, and that win can be shared too, as a second, separate link: the author’s clear, which is an ordinary replay link as described above. Neither link is sent anywhere by the game; whoever you give them to opens them in their own browser.
The copy of the game other sites embed is a demo of the first three
campaign maps. Its Continue on pikefall.com button opens this site in a
new tab with your demo progress after #carry=: for each of
those maps you held, its stars, best lives, difficulty and challenge
marks, plus the enemies you have met, the lessons and dispatches you
have been shown, and whether you finished the training course. It
contains no identifier and no date and, like every fragment, never
reaches a server. Opening it adds that progress to the save on this
site, as described above, and is read once and
removed from the address bar.
On browsers that can record video, the game keeps the last ten to twenty seconds of a battle as you play it — the picture and the sound — so that it can offer Save clip when a boss walks on, on a killing spree and when a battle ends. That recording is made by your browser on your device and is kept only in the page’s memory: it is never written to your save, it is thrown away when you leave the battle, and it is not sent anywhere. A clip never leaves your device unless you share it, by pressing Save clip and choosing where it goes from your system’s share sheet or your downloads folder. It contains what was on your screen and nothing else.
Visitor counts
This site uses Cloudflare Web Analytics to count page views and see which
links bring visitors in. According to Cloudflare it sets no cookie, stores
nothing in your browser and does not fingerprint you; it records the page
you opened, the page that linked you here, your browser type and your
country as derived from your connection. Its script is loaded from
static.cloudflareinsights.com. The legal basis is the
legitimate interest in knowing whether anybody finds the site
(Art. 6(1)(f) GDPR). The
script is not loaded at all unless you allowed visitor counts, in the game
or on this site’s pages; the legal basis is your consent
(Art. 6(1)(a) GDPR, Art. 5(3) ePrivacy Directive,
§ 25(1) TDDDG), which you can withdraw under
Cookies and consent.
Google Analytics
This site uses Google Analytics 4 to count page views and see which pages
and links bring visitors in. It records the page you opened, the page that
linked you here, your browser and device type, screen size and language,
and the events Google’s Enhanced measurement adds to page views, such
as scrolling and clicking a link that leaves the site. Google does not log
or store your IP address; it derives an approximate country and region from
it. Its script is loaded from www.googletagmanager.com, and the
data goes to Google’s servers, which are in the United States and
elsewhere (see Data outside the EU). It is not
loaded on the game’s page, play.html.
Google Analytics sets cookies in your browser, which is why it is asked
about first. They are called _ga and _ga_ followed
by an identifier of this site, and they let Google tell visits apart without
knowing who you are. Google keeps event data for 14 months here, the longest
the setting allows, and Pikefall has switched off Google signals, the feature
that joins this data to signed-in Google accounts, and advertising
personalisation. Google’s own handling is described in
its privacy policy.
The legal basis is your consent (Art. 6(1)(a) GDPR and Art. 5(3) of the ePrivacy Directive, in Germany § 25(1) TDDDG). Nothing is loaded and no cookie is set until you allow it, and you can withdraw under Cookies and consent.
Advertising
The game shows ads through Google AdSense’s H5 Games Ads, and only
inside the game itself — never on this site’s other pages. Google’s
ad script is not loaded at all until you have cleared the game’s third
map, and not for anyone who has bought Remove Ads. Once loaded, it comes
from pagead2.googlesyndication.com, receives your IP address
and browser details as any request does, and may set cookies and similar
storage — including on this site’s own address — and read
your device’s identifiers to show, personalise, limit and measure
ads. Google, and the advertising partners its consent message names, are
responsible for that processing; how Google uses it is set out in
How Google
uses information from sites that use its services.
Where the law requires it (in the EEA, the UK and Switzerland), Google’s consent message asks you before any of that happens, and the game reads your answer from it and from nowhere else: refuse, and the game shows no ads and plays exactly the same. The legal basis is your consent (Art. 6(1)(a) GDPR, and for the storage on your device Art. 5(3) of the ePrivacy Directive as your country implements it — in Germany § 25(1) TDDDG). You can withdraw or change it at any time, as easily as you gave it, from the game’s Options, under “Privacy and cookie settings”; withdrawing does not affect ads already shown.
Wherever you are, you can turn off personalised advertising from Google in My Ad Center.
If you are in the United States: Pikefall itself sells nothing about you and holds nothing that could be sold. Letting Google’s ad script run may count as “selling” or “sharing” personal information for targeted advertising under some state privacy laws, such as California’s. Where Google’s message offers to opt out of that, your choice there applies; My Ad Center turns off personalised ads in any case.
An ad only ever plays where you choose: on leaving some results screens, and when you ask to watch one for crowns. The game keeps two numbers about this in its save — how many results you have finished since the last ad, and when it was — so it can space them out. Neither leaves your browser.
Links to other sites
The support buttons lead to Ko-fi and PayPal — and, where a card button is shown, to a Stripe payment page — and the community links to GitHub. Nothing is loaded from any of them until you click, and once you do, their own privacy policies apply. The game is never told whether you contributed, and nothing in it changes if you do. The payment service does tell the operator what it tells any recipient of a payment — usually the name and e-mail address you gave it, the amount and any message you wrote — and those are kept only for the bookkeeping the law requires (Art. 6(1)(b) and (c) GDPR) and never connected to your game.
Bug reports, feature requests and discussion live in a public GitHub repository. Anything you post there is public, is hosted by GitHub under its own terms and privacy statement, and needs a GitHub account. The game sends nothing there by itself: a report is only ever what you type into GitHub's form.
Pikefall also has profiles on TikTok, Facebook and Instagram. The links in this site’s footer are plain links: nothing from those networks is loaded on this site, and they learn nothing about you from it until you click. On the networks themselves, their own terms and privacy policies apply (TikTok, Meta for Facebook and Instagram). If you follow, like, comment or message there, the operator sees what that network shows any account holder, and the network may give the operator anonymous statistics about visits to the profile. For the Facebook Page and the Instagram profile, Meta and the operator are joint controllers for those statistics (Art. 26 GDPR); Meta’s Page Insights Controller Addendum sets out who does what, and Meta is the party to ask about your rights over that data, though you may also write to the operator. The legal basis is the legitimate interest in reaching players where they already are (Art. 6(1)(f) GDPR).
Cookies and consent
Pikefall sets no cookies, and nothing on this site today needs your consent: the save file is necessary for the game to work, and the services above neither store anything in your browser nor identify you. So you will not see a cookie banner.
Pikefall’s own code sets no cookies. The save file is necessary for the game to work and needs no consent, and the other services above neither store anything in your browser nor identify you. Google’s ad script does store and read information on your device, which is why it asks first; nothing else on this site does.
Pikefall’s own code sets no cookies. Google Analytics does, and it is
the one service on this site that stores something in your browser (the
_ga cookies named under Google
Analytics). It asks first, nothing is loaded or set until you allow it,
and the game plays the same whichever you choose. The save file is necessary
for the game to work and needs no consent.
You can change your answer here at any time.
Pikefall sets no cookies of its own, and the save
file needs no consent. The gameplay statistics and visitor counts described above store nothing
on your device and identify
nobody — but this site asks before running them all the same. It
asks once, on its pages or on the game’s map, “Decline” is
exactly as easy as “Allow”, nothing is counted until you allow
it, and the game plays the same whichever you choose. You can change your
answer here or under Statistics in the game’s Options at any time;
it is kept in your browser as pikefall.consent.v1.
If a future version adds something that does need your permission — advertising, for instance — a notice will ask before it runs, with “Decline” exactly as easy as “Allow”, and the game will play the same whichever you choose. You will be able to change your answer here at any time.
The game’s advertising is the exception, and it is asked about by Google’s own consent message inside the game rather than here, so that there is one answer about it and not two. See Advertising.
Children
Pikefall is a game for a general audience. It has no account, never requires a name, an age or an e-mail address, and collects nothing from anyone that would identify them, so it holds nothing about a child that it does not hold about everyone else. The name you can sign a challenge or a map with is optional, need not be your real one, and stays in the link and your own browser.
If you are under 16, please ask a parent or guardian before you allow Google Analytics. Declining changes nothing in the game.
Advertising is the one place age matters. In the EU a child under the age of digital consent — between 13 and 16 depending on the country, 16 in Germany — cannot give the consent Google’s message asks for alone; a parent or guardian answers it for them, and “Do not consent” leaves the game exactly as it is. Pikefall cannot know a player’s age and does not ask. Remove Ads switches the ad script off entirely.
If you believe something about a child has reached the operator anyway — through a contribution or a support request — write to the address above and it will be deleted.
Your rights
Under the GDPR you may ask what personal data about you is held, have it corrected or erased, restrict or object to its processing, and receive it in a portable form. There is no account, Pikefall’s own code gives you no identifier, and the save in your browser is already entirely in your hands. The personal data that can exist about you is what Cloudflare processes to serve a request, what Google Analytics records once you allow it, under the cookie identifier it sets, the order Stripe holds if you bought something, and the name and e-mail address a payment service passes on if you contributed (see Links to other sites). Write to the address above with any request; for a purchase, the e-mail address you paid with and the receipt number let the order be found. Where anything here rests on your consent, you may withdraw it at any time, as easily as you gave it, without affecting what happened before; for the game’s advertising, see Advertising. You may also complain to a data protection supervisory authority, in particular in the country where you live.
Changes
If what the site stores or sends changes, this page changes with it, and the date at the top says when. Earlier versions are available from the address above on request.