Sign in

Keep your suya stall in the cloud. No password.

Your email is used only to send sign-in codes. See Privacy.

Enter the 6-digit code

Change email

Choose which progress to keep

This account already has a stall in the cloud, and this browser has a stall too.

Sign in a bit later

You can sign in after you finish the challenge.

Privacy policy

In short: no account is needed to play, and your stall (your progress) is kept in your own browser. Some things do go to our server on Cloudflare: a random id for your browser with the days you played, a replay of every night you finish (your taps, without your name), the share codes and poster records your shares make, one-way hashes of your network address to stop abuse, a rating if you send one and, only if you sign in, your email and a copy of your stall. Google Analytics counts visits with cookies, and Google AdSense may show ads on the information pages. If your browser sends Global Privacy Control, none of our own counting, replays or share codes are sent, and Google Analytics and AdSense are not loaded.

Last updated:

Data stored on your device

The game uses your browser’s local storage to keep your stall (your progress, stock and upgrades), your settings such as sound and text size, and your daily-challenge runs (which dates you played and your result). Unless you save with your email, your stall itself is not kept on any server; a night’s replay carries the stall as that night opened, without its name (see Replays). Delete it at any time by clearing site data in your browser.

Saving your stall with email (optional)

Only if you sign in with your email (the “Sign in” button) does our server on Cloudflare keep: your email (to send 6-digit sign-in codes, never for ads or newsletters), a sign-in session cookie (HttpOnly, for 180 days), your saved stall (your night, cash, stock, upgrades, titles and stall name) and the history of your nights (for each night: its number, the place, the events, how many you served, missed and burnt, the money in and out, the profit, the stars, the night’s title, and when it ended). The sign-in code and the session are stored only as hashes. To stop mass code requests the server keeps a one-way hash of your IP address, used only to limit code requests, and removes it in the next automatic clean-up. The email carrying your code is sent through our email provider. When this browser and your account hold different stalls, the game asks which one to keep. Accounts not used for 24 months are deleted in the next automatic clean-up; to delete yours sooner, with its saved stall, its history and its replays, use Delete account on the Account page (or write to the address below). Deleting keeps nothing tied to you: ratings and daily scores stay only as anonymous numbers.

Save codes

The game can show your stall as a save code (it starts with MS1-) so you can move it to another phone or browser yourself. The code holds your stall and its last two weeks of nights; it is made in your browser and is never sent to our server. Anyone who has your code can load a copy of your stall, so share it only with yourself.

Ratings

If you rate the game (1–5 stars), your browser keeps a random id and your score, and sends the id, score and language to our server on Cloudflare to compute the average. To stop abuse, the server also keeps a one-way hash of your IP address, never the address itself. If you are not signed in, no name, email or account is linked to a rating. If you are signed in, the rating is tied to your account so you rate once on every device. You can change your score any time.

Counting players

So we know how many people play and where they found the game, the game keeps a random id in your browser (not linked to your name or device) and sends it to our server on Cloudflare when the game opens (once a day), when you finish a night, and the first time you reach certain moments (for example your first skewer, your first night finished, the daily challenge, a sign-in). With the first of these it sends the address of the first page you landed on and the page that linked there, including any campaign tags in that address (utm_source and the like); internal links never add them. The server keeps the dates you played, the nights finished, the highest night, those first moments and that first landing, plus a one-way hash of your IP address for about a day to limit abuse. Records not seen for 13 months are deleted. If you sign in, the record is tied to your account so you count once on every device. If your browser sends Global Privacy Control, none of this is sent or kept, and the game sends no analytics events either.

Replays

When you finish a night (or leave it by starting over), the game sends a replay of it to our server on Cloudflare, under your browser’s random id and, if you are signed in, your account. A replay holds your taps and when you made them, the stall as the night opened (its stall name left out) and the night’s seed: enough to play the night again, never your name or email. Until the server has it, it waits in your browser’s storage. You can watch your own nights from Your nights. A replay is shared only when you turn on “Include the replay” in the share sheet and then actually send or save the link or picture: from then on it is public to anyone with its link, and it is kept for as long as it is shared. To stop the link, turn “Include the replay” off again in that share sheet, delete your account (signed in), or write to the address below. A replay you never share is deleted after 60 days (a daily challenge run on the board is not deleted then: it stays with its board row, see below). To stop abuse the server keeps a one-way hash of your IP address with each replay and clears it after about a day. If your browser sends Global Privacy Control, no replay is sent or kept.

The daily challenge board

Your first run of each day’s challenge is sent to our server on Cloudflare with its replay, under your browser’s random id and, if you are signed in, your account. The server plays the replay again to work out the profit, then keeps for the board: the date, the profit and how many you served, when it arrived, and the replay. Anyone can see the board: each run’s place, profit and serves, and a name, which is “Guest stall” unless you are signed in, when it is the initials of your stall name. Your browser id, account and email are never shown. Board rows are deleted after 400 days; deleting your account removes its replays and leaves its scores on the board as “Guest stall”, tied to no account. If your browser sends Global Privacy Control, nothing is sent and the run stays on your device.

Share cards and thank-you posters

Share cards and the thank-you posters you get at milestone nights are pictures drawn in your browser and never uploaded. When you save, copy or share a thank-you poster, the game tells our server which milestone it was (night 1, 5, 10 and so on) under your browser’s random id, never your name, so we can count the posters taken; the record goes with that id. A link you share carries where you shared it (for example WhatsApp or TikTok) so we can count which places bring players. Global Privacy Control turns the poster record off.

Friend rewards

When you share your invite link (from the Account page, or a share from the game), it carries a short share code made by our server on Cloudflare for your browser’s random id and, if you are signed in, your account. A new browser that opens the game from that link keeps the code and sends it with its first visit; when it has played its first minute of night 1, the server records one reward of ₦2,000 of stall cash in the game for you and one for the friend (game money only, never real money). The reward row holds the code, the friend’s random browser id (and account, if signed in), the amount and the time: never a name or email, and your friends are shown to you only as “Friend 1, 2, …” with the time they played. To keep rewards fair, the server compares one-way hashes of the network addresses of the sharer (kept with the code, from the last time it was used) and the friend (from the request), and pays nothing when they are the same network or the same person; the hashes are never the addresses themselves. Codes not used for 13 months and their rewards are deleted. If your browser sends Global Privacy Control, no code is made, kept or sent and no rewards are paid.

Who can see these records

The site’s owner can open a statistics page, signed in with an address on the owner’s list, that shows the counts above and, for one browser’s random id, its record: the first page it landed on and the page that linked there (with any campaign tags), the dates it played, its first moments, its share codes and rewards, its replays (which the owner can watch) and, if it is signed in, its nights. A signed-in player’s email shows only masked (its first two letters and the domain); no name is ever shown. Nobody else can open the page.

Hosting and logs

The site is served through Cloudflare. Like any web host, Cloudflare may process IP addresses and technical request data to deliver content and prevent abuse.

Visit statistics

The site uses Google Analytics to count visits and understand how the site is used (which pages are viewed, device type, country, and game events such as a night finished or a share card made, each with the campaign tags of your first landing). Google Analytics sets cookies in your browser and processes your IP address and technical request data; we only look at aggregated reports. The page address it receives leaves out the share codes a link may carry (?ref= and ?replay=). If your browser sends Global Privacy Control, the site does not load Google Analytics at all: no page views and no game events are sent. You can also block it with a content blocker, the Google Analytics Opt-out add-on, or by clearing cookies in your browser.

Advertising

The site may use Google AdSense to show ads on its information pages, never on the game itself or on your Account, Settings and History pages. Google and its partners use cookies to serve ads based on your visits to this and other websites. If your browser sends Global Privacy Control, the site does not load AdSense. You can also turn off personalised ads in Google’s Ad Settings (adssettings.google.com) or block them with a content blocker.

The billboard in the game

Once your stall has a signboard, a small billboard stands beside it: an advertiser’s picture and link, or our own “Your brand here” notice. It is a plain picture served from this site, so the advertiser learns nothing about you unless you tap it. Our own count notes, with your browser’s random id, the first time the billboard was on screen during a night and the first time it was tapped (no advertiser’s name). Google Analytics gets each view and tap with the advertiser’s name. Never your name. Global Privacy Control turns both off.

Fonts

The site’s font is served from this site itself, so your browser makes no request to Google Fonts or any other outside server to fetch it.

Children

The game is suitable for all ages and requires no one to give personal information; saving with email is optional.

Changes

If this policy changes, the date at the top of the page will change too.

Contact us

If you have a privacy question or a request about your data (such as deleting your email and saved stall), email us at [email protected].

Play now