Sign in

Keep your stall and sales history 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 leave the room or finish the challenge.

Privacy policy

In short: no account is required and your progress stays in your own browser. Our server keeps only an anonymous play count (a random id, the dates you played, days traded and your highest day, and a public share code for friend rewards), a rating you choose to send and, if you choose to save your progress with your email, that email with your saved copy and day-by-day history. We use Google Analytics for anonymous visit statistics and Google AdSense to show ads.

Last updated:

Data stored on your device

The game uses your browser’s local storage to keep your progress (day, money, stock, upgrades), a ledger of your recent trading days and your sound preference. Unless you save with your email, this progress is never sent to any server (only the anonymous play count below). Delete it at any time with “Start over” or by clearing site data in your browser.

Saving your progress with email (optional)

Only if you sign in with your email (the “Sign in” or “Save progress” button) does our server on Cloudflare keep: your email (to send 6-digit sign-in codes, never for ads or newsletters), your saved progress, your day-by-day history (customers, revenue, tips, profit, place, weather, event, morning shift, delivery orders and drinks; for days with friends, the room code and the other players’ names — the Sales history page shows these same days back to you) and a sign-in session cookie. Sign-in codes and sessions 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; records older than an hour are removed in the next automatic clean-up. The email carrying your code is sent through our email provider. Data is kept until you delete it: the Account page → “Delete account” removes your account, saved copy and history from the server at once; accounts not used for 24 months are deleted in the next automatic clean-up.

Counting players (anonymous)

To know how many people play, when the game opens (once a day) and after every trading day your browser sends our server on Cloudflare: a random id made in your browser, the language, the in-game day and whether the game opened or a day was finished. The server keeps the first and latest date you played, how many days you traded and your highest day. For a new stall in a browser that had no saved stall when the game first opened there, it also records once, with the time, the steps of that first session (the title screen, a new stall, the morning, day 1 opening, the first piece dropped, the first piece taken out, the first correct order, day 1 finished or abandoned, day 2 opening), to see where new players stop. The first time the game opens in that browser, it also sends once where you came from: the full address of the first page you opened on cavienchien.net (with parameters such as utm_source) and the page before it as your browser reports it (usually only the other site’s domain, like google.com), to learn how new players find the game. It keeps no IP address (only a one-way hash to stop abuse) and no device details; a day’s numbers and your stall’s names are sent only for the leaderboards (below). The game’s operations account can look at one browser’s count, steps and replays to understand how the game is played; it sees the random id and, for a signed-in player, only a masked email (like ab•••@gmail.com). If you sign in, the count is tied to your account so one player on several devices counts once; deleting the account unties it. Counts with no activity for 13 months are deleted. If your browser sends the Global Privacy Control signal, the game sends nothing.

Replays of your trading days

So you can watch a played day back, after every trading day at your own stall (quit days too) your browser sends our server on Cloudflare a replay: your stall as the day opened (money, stock, upgrades, menu, stall and owner name, story progress) and each tap you made that day with its moment; no pictures, no video. A replay is tied to your browser’s random id (as for the player count) and, signed in, to your account; when you sign in, this browser’s replays move to the account so they open on your other devices. A one-way IP hash is used only to limit uploads. Replays are kept for good; only you and the game’s operations account (to understand how the game is played and to fix problems) can watch them unless you share the link (the result card or “Share replay”): then anyone with the link can watch that day, with your stall’s name. Deleting the account deletes all of its replays. If your browser sends Global Privacy Control and you are not signed in, replays stay on this device only. The result card picture is drawn on your device and never uploaded; the room invite’s QR code is made on your device too.

Thank-you posters at milestone days

When your stall finishes day 1, 5, 10, 20, 30, 50 or 100, the game draws a thank-you poster on your device (your stall’s name and numbers, the QR code of your link); the picture is never uploaded. Our server on Cloudflare records only, under your browser’s random id, which milestone’s poster was shown, had its gift collected or was shared, with the time, to know whether posters help; and when a new friend opens the game from a poster’s QR code, their play count notes that it came from a poster. This is kept and deleted like the player count. If your browser sends Global Privacy Control, nothing is sent.

Ranking after each day

To show how your trading day compares with others, each time a new version of the game is released we count the profit and day number of the finished days already stored (from replays and the history of signed-in players) into a table of numbers that ships inside the game. The table holds numbers only: no id, name or account; test browsers and suspect traffic are left out. The comparison happens on your device.

Leaderboards

Since version 1.41.0, after each finished trading day (solo or co-op; challenges do not count) your browser sends, with the play count: the day’s profit, the customers served, the day’s stars, whether it was a co-op day, whether you are signed in, and your stall’s name and sign colour as you set them in the game (the owner’s name is not sent). Our server on Cloudflare adds these up under your browser’s random id (or your account, if you were signed in when the day ended) into all-time totals and totals per day (Vietnam time; daily totals are kept 8 days), with the country Cloudflare reports for the connection (no IP address is kept). The Leaderboard pages show publicly, to everyone: the stall name, country flag, the day reached and those numbers; each row carries a one-way hash, never your browser’s or account’s id. Friends invited are counted from friend rewards (below). At launch the all-time board was filled from the finished days already stored in replays and in signed-in players’ history, with the stall names of that time (no owner names). To change your name on the board, rename your stall in the game and finish a day; to have your stall removed, write to us through the Contact page. Deleting your account deletes its rows from the boards; a stall not played for 13 months leaves them too. Test browsers and suspect traffic never appear. If your browser sends Global Privacy Control, nothing is sent and your stall is not listed. Since 1.42.0, the pictures and videos for sharing a rank are drawn on your device and never uploaded; they leave it only when you share or save them yourself.

Rewards when friends play from your link

Every browser that has played (and, signed in, every account) has a public 8-character share code, added to the end of the links you share (?ref=…). It is not your browser’s private random id used for counting players; that id never appears in a link. Our server on Cloudflare keeps: the share code, the random id of the browser that made it (and the account, if any), a one-way hash of the IP address of your last game open (so friends on your own network are not counted) and the time. When a new browser opens the game from a link with a code, the server keeps that code with that browser’s play count; when that person has played a minute (their own first day, a day in a shared room, or a challenge), the server keeps a pending reward (the share code, the friend browser’s random id, the amount, the date) until your game adds it to your stall. No name, email or location of your friend is kept or shown to you: you only see when each friend came and whether they played a minute (“Friend 1”, “Friend 2”… no names), and how many friends and how much cash. The game’s operations account can see which browser came by which browser’s link, to understand how players invite friends; it sees the random ids and, for a signed-in player, only a masked email. This is kept and deleted like the player count (13 months after last use); deleting your account unties the code and its links from the account. If your browser sends Global Privacy Control, no code is made or sent, the links you share carry none and there are no rewards.

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 with your email, the rating is tied to your account so you rate once on every device; if you delete the account, the rating stays in the average but is no longer tied to anyone. You can change your score any time.

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). Google Analytics sets cookies in your browser and processes your IP address and technical request data; we only look at aggregated reports. You can block it with a content blocker, the Google Analytics Opt-out add-on, or by clearing cookies in your browser.

Advertising

The site uses Google AdSense to show ads. Google and its partners use cookies to serve ads based on your visits to this and other websites. You can turn off personalised ads in Google’s Ad Settings (adssettings.google.com) or block them with a content blocker.

Fonts

The Be Vietnam Pro 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 progress), email us at [email protected].

Play now