Privacy policy

Stapel is a free game that knows as little about you as possible. Here we explain exactly what we store, why, where, for how long, and what your rights are. It complies with South Africa’s Protection of Personal Information Act 4 of 2013 (POPIA). This is a translation of the Afrikaans policy; if the two ever differ, the Afrikaans one applies.

In short: players don’t have to give anything, and your game data stays on your own device, unless you choose to sign in with Google to save your progress (it is never needed to play; then we keep your progress and a number made from your Google account, not your name or email; you can delete it at any time: section 2d). We only count anonymously how often sponsors are seen, how high the daily towers get and how often results are shared; a live Challenger Series match keeps your (optional) nickname and heights for at most 7 days; and the daily leaderboard shows your nickname and today’s height (30 days; you can hide yourself) (section 2). Only advertisers (sponsors) give personal information, and only what is needed to invoice and contact them. This applies to the website and to the Stapel app on Google Play (Android), which is the same game.

1. Who is responsible

The “responsible party” (POPIA) for information collected by Stapel is:

Legal name: Sportscard Trading (Pty) Ltd (known on Google Play as “Lekker Local”)
Registration number: 2026/492510/07
Physical address: 39 Delport Avenue, Oatlands, Krugersdorp, 1739, South Africa
Email: lekkerlocal.apps@gmail.com
Phone: +27 81 264 6506
Information officer: Anandre Groenewald, lekkerlocal.apps@gmail.com

2. Players: what we collect and what we don’t

You don’t need to create an account or type in any information to play Stapel. Signing in with Google is optional (section 2d).
Your results, streak, best height and settings are stored only on your own device (see section 11) and are not sent to us. The exceptions are the anonymous count and the daily leaderboard below, and, only if you choose to sign in with Google, your saved progress (section 2d).
We use no analytics or tracking services from other companies, no advertising networks and no cookies to follow you. We do count anonymously how often sponsors are seen and how the daily tower goes; exactly what is below.
When you share your result, it goes through your own app (such as WhatsApp). We don’t receive it; we only count anonymously that the share button was tapped (section 2a).
The game fetches the list of sponsors, and how many free tries the Daily Tower has a day, from our website or server. These are anonymous requests without any information about you. As with any website, the services that send out the files (section 6) technically see your IP address; we don’t store it or use it to identify you.
Stapel is meant for players aged 13 and older. We never ask for a player’s real name, email or other contact details. The only player information we keep for a while is: for the daily leaderboard your nickname, your random player number and your result (height, blocks, playing time and tries), for 30 days; and after a live match a recording with your nickname and heights, for 7 days. After that it is deleted automatically (below). If you choose to sign in with Google, we also keep your saved progress until you delete it (section 2d). Please don’t use your full name as a nickname.

Anonymous counts

When a game ends, and when you tap a share button on the results, the game sends one small message to our server, but only when our server is on. It is just numbers with a date:

What is counted: the date; whether it was the Daily Tower or a practice game; how many times each sponsor’s name was on a block you dropped; which sponsor’s billboard stood on the island; whether the ad was shown on the menu; and how many times the share buttons on the results were tapped (just a number per day and kind of game).
The Daily Tower: your height (in steps of 0.5 m) is added to a list with everyone’s results of that day. That lets the game say “You did better than 72% of players today”. The line appears only once at least 10 people have played. The result is sent at most once a day per device.
What is never sent or stored: your name, email address, IP address, device ID, cookies, the time of day or anything else that tells one player from another. We only store totals (“there were 412 games on 6 October”), not a list of who played, and they can’t be linked to you. So this is not personal information.
Preventing abuse: to stop one computer from inflating the numbers, the server remembers your network address for at most an hour in its memory, as a key that changes every day (it can’t be turned back into an address). It is not stored in the database or the logs.
Why: so that we can tell sponsors how often their name was seen (they get a monthly report), and to be able to show the daily comparison.
How long: these totals are kept for about 13 months and then deleted automatically.
Is our server off, or are you without internet? Then nothing is sent and the game works as usual.

Challenger Series (head-to-head)

Against the computer or with a link: nothing is sent to us. A challenge link you share yourself contains your nickname and your tower’s height second by second. Whoever gets the link can see it.
Live matches: while you play, the server passes your nickname, your player card (your looks, your rank and the blocks you chose) and your height on to your opponent, and in a coin match how many coins each of you puts in; in Blok vir Blok (Block by Block) also every block you drop and how the tower stands afterwards, and in both modes the emojis you send (six fixed pictures, no written messages). After the match it keeps a recording (the nickname and the heights, nothing else) for at most 7 days, so that a player who finds nobody to play against can play against a real match. After that it is deleted automatically.
A friend’s link: whoever opens a room link (?kamer=) sees the nickname of the player who invites and the kind of match. If they tap “Sorry, busy right now” (or, for a coin match, “Let them know: not enough coins”), the player who invited gets their nickname (and, for a coin match, that they have too few coins for it); an older Stapel that opens a coin-match link passes its nickname on too, and the player who invited reads that it doesn’t know coin matches yet. The room keeps at most 5 such answers until that player’s game is back, and forgets everything when the room closes (at most a few minutes after the match).
Back after a dropped connection: the game sends a random code that only works for that one room, so you get your own seat back. It is used nowhere else and disappears with the room.
What is never stored: your IP address, device ID, cookies or anything else that points back to you. Your nickname is optional; without one you play as “Bouer” (Builder) with a number.

Daily leaderboard

What is sent: when you have finished the Daily Tower, the game sends your nickname (or “Bouer” with a number if you didn’t choose one), your tower’s height, how many blocks you dropped, how long you played and how many tries you played that day (the free tries and “One more try”), together with a random player number. That number is made once on your device and stays the same until you delete the game’s data (section 11). It is linked to nothing else and only serves to know your place on the leaderboard, except when you sign in with Google: then the number is also in your saved progress (section 2d), so “Delete my account” also deletes your leaderboard entries. The server also notes when your result first arrived (with an equal height, whoever played fewer tries is ahead, and then whoever’s result arrived first). We use the blocks and the time only to refuse impossible results.
Who sees it: the day’s top ten are shown with their nickname and height; every player also sees their own place. Switch off “Show me on the leaderboard” and others no longer see you (you still see your place). We may remove an entry with an unsuitable nickname or an impossible result from the list.
How long: 30 days, then it is deleted automatically. Your IP address is not stored; only a daily hashed derivative of it is kept briefly in memory to prevent abuse, as with the anonymous counts.
Deleting it sooner: send us the date and your nickname (section 9), and we will delete your entry.

Saving your progress (sign in with Google)

Optional: under ⚙️ Settings → ☁️ “Save your progress” you can sign in with your Google account. Then your towers, coins, looks and ranks are safe, and the same on your phone and the website. Signing in is never needed to play, to buy in the Shop or to play a match: without signing in, the game works exactly the same. If you are under 18, sign in only if your parent or guardian agrees (POPIA section 35).
What Google gives us: when you sign in, Google gives the game a signed “sign-in token” with your Google account’s number, name, email address and photo. Our server checks it with Google and then keeps only a number made from your Google account’s number with a secret key (it can’t be turned back into your Google number). Your name, email and photo are never stored.
What we keep: your progress as the game keeps it on your device (your finished towers and stats, Practice’s best, your Challenger Series nickname and record, coins, power-ups, looks, your tower style, ranks, the Daily Tower’s extra tries and how many you used, the weekly chest, how many times you used “Refill my coins”, the day of a tester’s gift, your random player number for the leaderboard and the ones your other devices used before (at most 8)), when the account was made and last used, and for each device you are signed in on a random session code (only a fingerprint of it). A tower you are building at that moment, and coins held in a coin match, are not sent (they stay on that device).
What you buy stays yours: what you buy with coins stays in your saved progress, even when an older version of the game doesn’t know it yet.
Why: so your progress isn’t lost (a new phone, a cleared browser) and is the same on all your devices.
How long: until you delete it. An account not used for 2 years is deleted automatically; a device’s sign-in not used for 400 days expires.
Signing out: it only ends that device’s sign-in. Everything stays on the device, and your account keeps its copy until you sign in again.
Google itself: the sign-in happens at Google, under Google’s own privacy policy. On the website, Google’s “Sign in with Google” button (from accounts.google.com) only loads when you open ⚙️ Settings, or when the game offers once to save your progress (on the results after a new best, or in the Shop after a purchase), and only while sign-in is open and you aren’t signed in yet; in the Android app the phone itself asks Google.

The testers’ vote on new ideas (October 2026)

What: on the preview page “Die Lewende Toring” (stapelspel.pages.dev/lewende-toring/) you can vote for the one of three new ideas you like most. When you vote, you send your name or nickname, your choice, a reason if you write one, and which of the ideas you played, with a random vote number the page keeps on your device (so you can change your vote instead of voting twice). The page fills in the name with your Challenger Series nickname on this device; it is only sent when you tap “Stem” (vote).
Why: so we can see which idea the testers want and read their reasons. Only the owner sees the names and reasons; we don’t publish them.
How long: votes are taken until 31 October 2026, and all of them are deleted automatically on 8 November 2026. To have your vote deleted sooner, write to us (section 9) with the name you voted with.
Under 18? Ask your parent or guardian first. A nickname is enough; never write a phone number or address (the server refuses them).

Ons dorp (your crew, the Weekly Tower and Saturday)

What is sent: when you open Ons dorp, the game sends a random player number with a secret code (both made on your device; the server keeps only a fingerprint of the code), your Challenger Series nickname (or “Bouer” with a number), your blocks’ style, how high your Daily Tower stood on each day of this week, and how your latest Daily Tower stood (each block’s shape, colour and place, to stand on your crew’s island). When you build, ride the river or throw bombs, it sends the floors you built (each one’s shape, colour, place and how it landed), how many people you rescued, and where each bomb landed.
What the server keeps: your crew (its name, its members’ nicknames and styles and each one’s latest Daily Tower, at most three), the crew’s Weekly Tower (every floor and who built it), its people, its news and its monuments (past weeks’ towers); for you, this week’s Daily heights, your build turns and bombs used, and whether you rode the river today; on Saturday your river: the four crews’ names and heights, the bombs that hit and the final order and prizes.
Who sees it: your crew sees all of it. On Saturday the other three crews on your river see your crew’s name, its tower and height, and the news of bombs. Whoever opens your crew’s invite link sees the crew’s name and who is in it, and can join while there is room.
Stopping abuse: the server counts how many requests come from one address each hour. Your IP address isn’t stored; only a daily hashed derivative of it is kept briefly in memory, as with the leaderboard.
How long: a Saturday’s river (standings, bombs, news) is deleted automatically six weeks later. Your crew and your player record stay until you ask us to delete them (write to us, section 9, with your crew’s name). Leaving a crew takes you and your nickname off it.
Under 18? Ask your parent or guardian first. A nickname is enough; the server refuses rude names, phone numbers and addresses.

Your town (Steal and Revenge)

Since 1.20: the game no longer uses Your town or the Castle Series below; what the server kept of them stays until you ask us to delete it.
What: where the server knows Your town, the game sends your town’s number, your Challenger Series nickname (or “Bouer” with a number), your tribe, how many people (golden ones too), raids and walls your towers earned, and the landmarks you bought. The server keeps your town: the numbers, who your neighbours are, and the news of raids (who stole from whom, how many and when).
Who sees it: your neighbours (friends who opened your link, or whom you stole from) see your nickname, tribe and numbers. A raid’s link shows who stole from whom, and how many.
Stopping abuse: the server counts how many new towns and requests come from one address, and how often a town is raided each hour. Your IP address isn’t stored; only a daily hashed derivative of it is kept briefly in memory, as with the leaderboard.
How long: until you ask us to delete your town (write to us, section 9, with your town’s number). That deletes your castle with it.
Under 18? Ask your parent or guardian first. A nickname is enough; the server refuses rude names, phone numbers and addresses.

The Castle Series (friends’ castles)

What: where the server knows Your town, the game sends your castle with your town’s number: how your last five Daily Towers stood (each block’s shape, place, tilt and whether it was Perfect, Good or Skew), your defence plan and the castle’s seed number, so your neighbours can attack it. When you attack a neighbour’s castle, the game sends how many stars you got and how much of the castle fell; that becomes their news (who, when and how much).
Who sees it: your neighbours (Your town, above) see your castle and your nickname; you see the news of attacks on your castle.
How long: until you ask us to delete your town (that deletes your castle with it).

Block Clash

Against Robot Rikus: nothing is sent.
Against a friend (with a room link): while you play, the server passes your nickname, your blocks’ style, how many extra blocks your Daily Tower gave you, and every turn (the card you pick, where you build or how you throw, and how the towers stand after the turn) on to your friend. None of it is stored: the room forgets everything when it closes (at most a few hours after it was opened). To stop abuse, the server counts how many rooms one address opens, as above.

Ride with a friend (Saam gly)

While you ride together (with a room link): the server passes your nickname, your blocks’ style and, a few times a second, where you are on the river (metres, lane, a jump or a duck, your hearts), your knocks, your end metres and a “once more” on to your friend, so each of you sees the other on the water. None of it is stored: the room forgets everything when it closes (at most a few hours after it was opened). Your metres count for the day’s River run ranking as any ride does. To stop abuse, the server counts how many rooms one address opens, as above.
Finding an opponent: while you look, the server keeps your nickname and a random code made for that one search (so a phone back from another app takes its own place again); the player you are paired with sees your nickname. Both go as soon as you are paired, or when you stop looking. A room also gets such a code from each phone, so a phone that lost its connection gets its own seat back; it goes with the room.

Hengel (the biggest fish of the day, the month and the year)

What is sent: when Oom catches a fish after your Daily Tower, the game sends the same random player number and secret code as the Afgly (with your nickname), the day, the kind of fish, its weight, whether the shark left only the head, and whether you want to be shown on the ranking (the ranking’s “Show me”).
What the server keeps: your biggest fish of the day, of the month and of the year (the kind, the weight and your nickname), and how many fish you caught today (only to stop cheating).
Who sees it: any player sees the top 10 of the day, the month and the year: the nickname, the fish and its weight. Switch off “Show me” and you keep your place but your name isn’t shown.
How long: a day’s ranking is deleted after 8 days, a month’s after 14 months and a year’s after 3 years.

Deleting your account

In the game: ⚙️ Settings → “Delete my account”. This deletes your account, your saved progress, all your devices’ sign-ins and your names on the daily leaderboard, at once, and within 7 days also from our database’s restore copy at Cloudflare. What is stored on your device itself (section 11) stays there until you clear it.
Without the app: open stapelspel.pages.dev/?rekening on any phone or computer, sign in with the same Google account and choose “Delete my account”.
By email: write to lekkerlocal.apps@gmail.com (section 9). We answer within 30 days and help you delete it yourself, in the game or at stapelspel.pages.dev/?rekening. We can’t find your account ourselves, because we don’t keep your name or email. An account nobody signs in to any more is deleted by itself after 2 years without use.

News on your phone (the Android app)

Only if you allow it: in the Android app, Android asks once whether Stapel may show notifications (the same question as the daily reminder). If you allow it, the app joins our news list at Firebase Cloud Messaging, Google’s notification service, so we can send a short note about a new version or Stapel news.
What is made: Firebase makes an address for the app on your phone (a random installation number and a notification token). It is not linked to your nickname, your account or your progress, and we don’t see who is on the list: every note goes to everyone on it. Nothing about how you play is sent. The website sends no notifications.
To stop: turn off notifications for Stapel in your phone’s settings, or uninstall the app; the address then stops working and Google deletes it.

Buying coins (the Android app)

When you buy a coin pack, Google handles the payment: we never see your card or bank details. To deliver the coins and to help if something goes wrong, our server keeps, with your account number (section 2: not your name or email): the pack, Google’s order number and purchase token, the date and time, the coins delivered, and whether the purchase was later refunded. Our server checks each purchase with Google before the coins arrive. The rules for buying are in our terms of use.

3. Sponsors: what we do collect

Please note: online sponsorships are not open yet. This section (and whatever else is said about sponsors and payments) describes what will apply once they start.

If you advertise on Stapel, we collect:

For the advert: your business name, and with the billboard an optional tagline and website address.
To contact you: your contact person’s name, your email address and an optional phone number.
Payment information: your card details are handled only by Paystack; we never see or store them. From Paystack we receive a customer code, a subscription code, the amount, date and status of each payment, and the plan you chose.
Consent record: which version of the sponsorship terms and of this policy you accepted, and when. We also store an encoded (hashed) derivative of your IP address, never the IP address itself. This helps us stop abuse and repeated attempts.
Technical records: copies of the messages Paystack sends us about your payments (with card and IP details already removed), so that we can trace errors.

You give this voluntarily, by filling in the form. Without this information we can’t manage your advert and payments.

4. Why we use it

Showing your advert, managing your subscription and invoicing you monthly: It is needed to carry out our agreement with you.
Keeping invoices, receipts and tax records: Legal obligation (tax and accounting law).
Your email about your subscription: payments, cancellation, changes, removal: Carrying out the agreement.
Preventing fraud, abuse and repeated attempts; securing the system: Our legitimate interest and your interest in a safe system.
Protecting our rights and answering complaints or claims: Our legitimate interest; legal obligation.
Saving your progress (players who sign in with Google, section 2d): Your consent: you choose to sign in (POPIA section 11(1)(a)). Withdraw it with “Delete my account”.

We don’t sell your information, don’t share it for marketing and don’t send you marketing without your consent.

5. What is public

Your business name, tagline and website address are shown in the game and are part of the public list of sponsors that anyone can download from our server. Your contact person, email, phone number and payment information are never part of the public list.

Players: on the daily leaderboard, everyone who plays sees the nickname and height of the day’s top ten, with a 🔁 and the number of extra tries for those who played more than one try that day (free or with “One more try”), except those who switched off “Show me on the leaderboard” (section 2). The random player number is never shown.

6. Who else handles your information (operators) and cross-border transfers

We use the following service providers (“operators” under POPIA) to make Stapel work. They process information only for our purposes and under their own terms and privacy policies.

Paystack: Payments and monthly subscriptions. Handles your email, your card details (only at Paystack) and your payment data.
Cloudflare: Sends out the game and these pages (Cloudflare Pages, stapelspel.pages.dev), plus our server (Workers) and database (D1, in Western Europe) for the anonymous counts, the daily leaderboard, the Challenger Series’ live matches, the saved progress of players who sign in and the sponsor system. Handles the information in sections 2 and 3 and technical requests, and technically sees the IP address of everyone who opens a page.
Google (Sign in with Google): Only if you choose to sign in with Google (section 2d): Google confirms who you are. From Google we only get the sign-in token, and of it we keep only a number made from your account’s number.
GitHub (GitHub Pages): The game’s old address (anandregroenewald.github.io/Toring) only forwards visitors to the new one. Technically sees the IP address of everyone who opens that old address.
Google Play: Distributes the Android app. What Google knows about you when you download the app falls under Google’s own privacy policy; from it we only get anonymous totals (such as the number of installs).
Google (Firebase Cloud Messaging): Only in the Android app, and only if you allow notifications (section 2, “News on your phone”): delivers our news notes to your phone. It handles the app’s notification address on our behalf.

Cross-border transfers (POPIA section 72): these providers process data in other countries, including outside South Africa. We use them because it is needed to carry out our agreement with you, and because they are bound by agreements or laws that protect your information similarly. By signing up as a sponsor, you agree to this.

7. How long we keep it

Unfinished sign-ups (you didn’t pay): marked abandoned after 7 days; after 30 days your name, email and phone number are deleted.
Payment records (amount, date, reference): 5 years, as tax and accounting law requires.
Coin purchase records (section 2, “Buying coins”): 5 years, as tax and accounting law requires (if you delete your account sooner, we keep them without your account number).
Copies of Paystack messages: the content is deleted after 90 days; a short log entry stays about 400 days.
Contact information of former sponsors: at most 24 months after your advert ended, or sooner on your request, except what we must keep for invoices.
Consent records: as long as your record exists, as proof of what you accepted.
Anonymous game counts (section 2): about 13 months, then deleted automatically.
Recordings of live Challenger Series matches (section 2): at most 7 days, then deleted automatically.
The daily leaderboard (section 2): 30 days, then deleted automatically.
Ons dorp’s Saturday rivers (section 2): six weeks, then deleted automatically. Your crew and player record: until you ask us to delete them.
The testers’ votes (section 2): until 8 November 2026, then all of them are deleted automatically.
Saved progress (section 2d, only if you sign in): until you delete it; deleted automatically after 2 years without use.
News notifications (section 2, only in the app if you allow them): the address works until you uninstall the app or turn notifications off; Google removes addresses that haven’t been used for about nine months.

8. How we protect it

All traffic goes over https. Card details never touch our server.
Messages from Paystack are verified with a cryptographic signature; false messages are refused.
Secret keys are not in the code but safely at Cloudflare. Only the owner has access to the admin page, with a long secret token.
We store as little as possible, and deleted information (section 7) is really removed, within 7 days also from our database’s restore copy at Cloudflare.
If a security breach affects your information, we inform you and the Information Regulator as POPIA requires.

9. Your rights

Under POPIA you may:

ask whether we have information about you, and get a copy (section 23);
ask that wrong information be corrected or unnecessary information be deleted (section 24);
object to the processing of your information, or withdraw your consent (section 11);
ask that your information not be used for direct marketing (we don’t do that);
complain to the Information Regulator (section 10).

Send your request by email to our Information Officer at lekkerlocal.apps@gmail.com. We answer within a reasonable time, usually within 30 days. We may first confirm your identity. Some records (such as payments) we must keep by law, even if you ask for deletion. You can also cancel your subscription at any time (the sponsorship terms will appear with the first sponsorships).

10. Complaints

Please contact us first; we’d like to put it right. If you’re not satisfied, you can complain to the Information Regulator (South Africa):

Website: https://inforegulator.org.za
Complaints (email): POPIAComplaints@inforegulator.org.za (with the prescribed complaint form, POPIA Form 5)
Phone: 010 023 5200
Address: JD House, 27 Stiemens Street, Braamfontein, Johannesburg, 2001

11. What is stored on your device

Stapel uses your browser’s storage, not cookies to follow you. This storage itself is not sent to us. What does leave is in section 2: the anonymous counts; for the daily leaderboard your nickname, the random player number from stapel.v1.board and the number of tries from stapel.v1.retry; and in a live match your nickname and player card (your looks and blocks from stapel.v1.econ and your rank from stapel.v1.ranks), and in a coin match how many coins each of you puts in.

stapel.v1: Your results, streak, best height, your Challenger Series nickname and record (and the kind of match and coins you last picked), and settings (sound, vibration, reduced motion, colour-blind mode, and which tips you’ve already seen: the first-game hints, “How do I play?” and the grey cement blocks). Stays until you clear your browser data.
stapel.v1.econ: Your coins (also those you put into a coin match, until its result), power-ups, looks (Challenger style), your tower’s style (Tower style: background, crane and blocks) and rank. Stays until you clear your browser data (if you are signed in, also in your saved progress: section 2d; a coin match’s stake stays on this device only).
stapel.v1.lang: The language you chose (Afrikaans or English).
stapel.v1.board: Your random player number for the daily leaderboard (it is sent with your result, section 2), whether you want to be hidden, the day this device took the tester gift (testers stay hidden), the last day whose result was sent, and whether a change still has to be sent. Stays until you clear your browser data.
stapel.v1.refill: How many times you used the Shop’s “Refill my coins” (today and in all), so it keeps to the day’s limit. Stays on your phone; none of it is sent (except in your saved progress if you are signed in: section 2d).
stapel.v1.ranks, stapel.v1.retry: Your rank in each Challenger Series mode, and the Daily Tower’s extra tries (the free tries and “One more try”). The rank goes on your player card to your opponent in a live match, and the number of tries with your result to the daily leaderboard (section 2). Stays until you clear your browser data.
stapel.v1.tries: How many free tries the Daily Tower has a day and from which day, as our server last said, so that the game also starts right without internet. Not sent. Replaced when the game asks again.
stapel.v1.signoffer: The day the game last offered to save your progress with Google, so it asks at most once every 60 days. Not sent.
stapel.v1.cloud: Only if you signed in with Google (section 2d): this device’s session code, a short reference to your account and the last copy of your progress that matched your account (so the game knows what is new on this device and counts nothing twice). The session code is deleted when you sign out; the rest when you delete your account.
stapel.v1.week: Your weekly chest: which day’s chest you opened last, how many streak shields you have and how many full weeks you played. Not sent. Stays until you clear your browser data.
stapel.v1.remind: Only in the Android app: the time of your daily reminder (or that you don’t want one). The reminder is planned on your phone itself as an Android notification; nothing about it is sent to us.
stapel.v1.score: Just a date and a height: remembers that today’s Daily Tower result has already been counted, so it isn’t sent again. Replaced every day.
stapel.v1.shopSeen: Which version’s Shop you’ve already opened, so the “New” dot only shows for new things. Not sent. Stays until you clear your browser data.
stapel.v1.chestSeen: Which day’s weekly chest you opened with a tap, so it doesn’t show closed again. Not sent. Replaced every day.
stapel.v1.updateSeen: Android app only: the version whose “New version!” card you’ve already seen, so it doesn’t show every time. Not sent. Stays until you clear the app’s data.
stapel.install.dismissed: Whether you closed the “Put Stapel on your home screen” tip, so that it doesn’t come back. Not sent. Stays until you clear your browser data.
stapel.sponsors.v1: The latest list of sponsors, so that the game starts quickly and also without internet. No longer used after 7 days and replaced with every update.
stapel.v1.lewende: Only for Die Lewende Toring in your towers: your tribe, your town’s record (the most people at once) and its title, who has moved in with you and how often, your golden people, and whether you’ve seen the first tip. Not sent. Stays until you clear your browser data.
stapel.v1.lewende.idees: Only for the preview of Die Lewende Toring’s ideas (in the Challenger Series): your preview rank and level, the tribe you chose last, which ideas you played, your vote and your random vote number (that one goes with your vote, section 2). The rest is not sent. Stays until you clear your browser data.
stapel.v1.span: Only for Ons dorp: your Weekly Tower’s floors (shape, colour, where each stands, how it landed, the style of whoever built it and how many people live in it), your build turns, which days you finished the Daily Tower and how high (for your Saturday ticket and bombs), whether you’ve ridden down the river today, your town’s people and a few past weeks’ towers, plus your player number and its secret code. What Ons dorp sends is in section 2 (Ons dorp). Stays until you clear your browser data.
stapel.v1.rvTaught: Only for the Afgly: which river lessons (jump, duck and Hanswors’s cream pie) you’ve already seen on this phone, so the game doesn’t slow down to show them every time. Not sent. Stays until you clear your browser data.
stapel.v1.rvTold: Only for the Afgly: how many rides each river word (like “Rapids!” or “Hanswors!”) has already been shown in on this phone, so after two it stays quiet. Not sent. Stays until you clear your browser data.
stapel.v1.hengel: Only for Hengel: every fish you caught on this phone (the kind, the weight, the date), your fish book and which tips you’ve seen. Not sent. Stays until you clear your browser data.
stapel.v1.rvtimer: Only if you put ?rvtimer=1 in the address (a developer test): the load time, memory and stutter counts of your last 8 Glybaan rides and whether the small test box is on. Not sent. Stays until you clear your browser data.
stapel.rideHeal: Only for this visit, and only if the Glybaan ride would not open: a mark that the game has already loaded itself fresh once, so it does not reload again and again. Not sent. Gone when you close the tab.
stapel.v1.katrolStyle: Only for Hengel in Toetsmodus: whether you fish with the new reel (slide) or the old one (circle). Not sent. Stays until you clear your browser data.
stapel.v1.rvGrind: Only for the Afgly: whether you’ve already ridden the log at a fork, so the tip “Tap ⟵ ⟶ to keep your balance” doesn’t show every time. Not sent. Stays until you clear your browser data.
stapel.v1.rvRail: Only for the Afgly: whether you’ve already hopped off a log in the river yourself, so the tip “Swipe up: hop off and keep your coins!” doesn’t show every time. Not sent. Stays until you clear your browser data.
stapel.v1.rvGrindOk: Only for the Afgly: whether you’ve already balanced all the way along a log once, so the balance coach’s arrows don’t show every time. Not sent. Stays until you clear your browser data.
stapel.v1.rvSpace: Only for the Afgly: whether you’ve already steered the rocket in space, so the tip “Drag your finger to fly” doesn’t show every time. Not sent. Stays until you clear your browser data.
stapel.v1.slag: Only for the Fruit Battle: your fruit basket (bananas, juice boxes and watermelons from your Daily Towers), your trophies, and how many battles you won and lost. Not sent. Stays until you clear your browser data.
stapel.v1.kasteel, stapel.v1.kasteeldae: Only for the Castle Series (preview): how your last seven Daily Towers stood (each block’s shape, place, tilt and whether it was Perfect, Good or Skew) so they become the towers of your castle, your defence plan (which day’s tower is your keep and where your defenders, oil, ballista and spikes stand), your trophies, how many battles you played and won, coins you won until Stapel puts them in your wallet, and which tips you’ve seen. Where the server knows Your town, your castle (the towers and your plan) is sent so your neighbours can attack it (section 2, The Castle Series); the rest is not sent. Stays until you clear your browser data.
stapel.v1.botsing: Only for Block Clash: whether you’ve seen its first tip, how many battles you’ve played and won, and coins still on their way to your wallet. Not sent. Stays until you clear your browser data.
stapel.v1.gly: Only for Slide: your best distance, the man you picked last, your level and missions, and coins still on their way to your wallet. Not sent. Stays until you clear your browser data.
stapel.v1.dorp: Only for Your town (Steal and Revenge, section 2): your town’s number, a secret key only this device has (the server keeps only a one-way fingerprint of it), what your towers earned for your town until the server has it, the day of your last wall, and the server’s last answer (your town, your neighbours and the news). Stays until you clear your browser data.
lt.profile, lt.mode, lt.tribe, lt.played, lt.vote, lt.voter: Only on the preview page Die Lewende Toring: your preview rank and level, the idea and tribe you chose last, which ideas you played, your vote, and your random vote number (that one goes with your vote, section 2). The rest is not sent. Stays until you clear your browser data.
Service worker cache: The game’s files, so that it works without internet. Stays until a new version replaces it.
stapel.launch: Only in the Android app: the challenge link the app was last opened with, and when, so that the same link doesn’t open again when you return to the app later.
stapel.klop: The tab’s session memory: the height and date from a friend’s challenge link, so that the menu and the Daily Tower can show “beat … m!” that day. Not sent. Disappears when you close the tab.
stapel.tab, stapel.adverteer.draft, stapel.adverteer.pending: The tab’s session memory: a random code that remembers which tab has the game open, and on the advertising page your half-filled form and a payment still in progress. Disappears when you close the tab.

12. Changes and contact

We may change this policy. The version date is at the top of the page. If a change is material, we email our current sponsors. You can direct questions about your information to lekkerlocal.apps@gmail.com or to our Information Officer.