Privacy policy
Effective date: 22 October 2026. Last updated: 13 November 2026.
Pocketvale is a free browser game for children of about 4 to 8. This page explains, in plain words, what happens to information when someone plays it at https://www.pocketvale.com.
The short version
- The game is saved in your browser, on your device. It is never uploaded to us.
- There are no accounts and no chat.
- We never ask a child for an email, an address or any way to contact them. A grown-up writing to us through the contact form may add an email for a reply.
- We count visits and play with Google Analytics. We never send a name or anything typed.
- The game's page sets no cookie and keeps no number that could mark one player from another.
- There are no ads.
Where the game is saved
The game keeps its save in your browser's local storage (localStorage), on the device being played. That includes the first name a grown-up may type to label a child's game, which is optional. The save stays on the device. We cannot see it, and we never receive it.
To delete it, clear this site's data in your browser's settings. That removes the game for good, so only do it when you mean to.
What we count, and how
On https://www.pocketvale.com only, the pages load Google Tag Manager, which runs Google Analytics 4. We use it to learn how many people visit and play, so we know whether the game is worth improving.
On the game's page
The game's page is where children are, so it is counted without anything that could mark a player. Before Google's script loads, the page sets Google's consent setting for analytics storage to "denied". In that mode Google Analytics is documented not to set or read cookies, so it holds no number that follows a browser from one visit to the next. Each time the game is opened, it is counted as a visit by somebody, not as the same player coming back. Nothing you answer on the other pages can switch this on for the game.
The only thing the game's page keeps in your browser is the game itself: the save and its settings, under names that begin pet-sims. in local storage. An automated check on the game fails if its page holds a cookie or any key that is not the game's own.
What is sent from the game's page is that it was opened, the device and browser type, roughly where in the world (country or city level), and these events:
- new player (
new_player): a new game was started on this device. - play day (
play_day): the game was played today, with a rough count of days played (one, two, three, four to seven, and so on). Sent with it:days_played. - milestone (
milestone): a step reached in the game, named by a short code. Sent with it:milestone_id. - stuck (
stuck): how many seconds the game waited on a goal with nothing pressed, and which goal and screen, by short codes. Sent with it:goal_id,scene,idle_s. - dead tap (
dead_tap): a button, named by a short code, that was pressed and did nothing, or said "not yet". Sent with it:target,scene,refused. - goal done (
goal_done): a goal reached, by a short code, and roughly how many minutes or days it took. Sent with it:goal_id,minutes,days. - scene loop (
scene_loop): a screen opened and left again with nothing done, and how many seconds it was open. Sent with it:scene,seconds. - quit at (
quit_at): the screen and goal the game was on when the page was closed or put away, and the minutes played. Sent with it:scene,goal_id,minutes. - load time (
pv_boot_ms): how long the game took to open, in one of four rough ranges. Sent with it:boot_bucket. - error (
pv_error): the game broke, with the screen it was on, a short code made from the fault (never its words), the place in our code, and the version of the game. Sent with it:scene,hash,at,phase,build. - install (
pv_install): the game was put on a home screen or desktop, or the grown-up was shown how, with one short word for which: accepted, dismissed, installed or steps. Sent with it:how.
The words in grey boxes are the exact names that are sent. Stuck, dead tap, goal done, scene loop and quit at show us where children get stuck, so we can make those places clearer. Load time and error tell us when the game is slow to open or breaks. Each is sent only a few times per visit.
Because no number marks a player, we cannot see that the same child came back. What we see is the rough count of days played that the save itself holds, sent with play day.
On the other pages
The home page, the guides and the wiki are for grown-ups. There Google Analytics records visits in the usual way: pages viewed, roughly where in the world (country or city level), device and browser type, and how long the page was open. Those pages also send:
- play click (
pv_play_click): the Play link was pressed, and which part of the page it was on (the top bar, the big button, a picture or the end of the page). Sent with it:area. - wiki click (
pv_wiki_click): the wiki link was pressed, and which part of the page it was on. Sent with it:area. - share click (
pv_share_click): the share button was pressed on the home page, which a phone shows under Play.
On those pages Google Analytics can store its own cookies in your browser, named _ga and _ga_ followed by a code. They hold a random number so that a return visit can be counted as the same browser. A cookie set there is not used on the game's page.
In the European Economic Area, the United Kingdom and Switzerland we ask first. A bar at the bottom of the page asks whether we may use the cookie, and it is not set unless you press Yes. We tell where you are from your device's clock zone, without looking anything up, and Google's script is also told to leave the cookie off for visitors it places in those countries. Elsewhere the cookie is set unless you say no.
The site's pages keep at most these keys in your browser's local storage:
pv-consent: your answer, yes or no, to whether we may count your visits to the site with a cookie.pv-ab: one letter, A or B, picked by chance so two versions of a page can be compared fairly; it says nothing about you, and is kept only where we may use the cookie.pv-team: a switch on the maker's own devices that turns all counting off, so that we do not count ourselves.
The game never writes them. Its page reads only your answer and the maker's switch, to know when not to count at all. The letter A or B is sent with the events above, and when you press Play it rides along in the link, so the game does not have to read it from your browser.
What is never sent
None of this carries a name, anything typed, or anything chosen in the game, such as which wish is being saved for. We cannot tell who a player is.
We turn advertising off. Advertising storage, advertising user data and ad personalisation are set to "denied" on every page, and Google signals is off. None of the game's data is used for advertising.
Google keeps the data it collects under Google's privacy policy.
How to stop the counting
Press this, then press "No, thanks" on the bar that appears. It works anywhere in the world, and you can change your answer the same way.
After a No, this browser is not counted at all, on the site or in the game: Google's script is not loaded.
Other ways:
- Block cookies or tracking for this site in your browser's settings, or use a content blocker.
- Install Google's Analytics opt-out add-on.
- Clear this site's data in your browser. This also deletes the saved game, and your answer.
The game plays the same either way.
Children
Pocketvale is made for children of about 4 to 8, playing on a grown-up's device. We do not collect personal information from children. The optional first name stays in the save on the device, and the game has no way to send it to us.
The counting above is used only to understand and improve the game, never to build a profile of a child or to show ads. On the game's page it uses no cookie.
If you are a parent or carer and want to ask about anything here, write to us and we will help.
When you write to us
The contact form is for grown-ups. It sends what you write, what it is about (a bug, an idea or a hello) and, only if you add one, your email address, so we can reply. A bug report sent from inside the game also carries three facts that help us find the bug: the game's version, the screen it was sent from, and how many days the game has been played. It never carries the child's name or anything else in the save.
Every message also carries, to help us find a bug, the browser and its version, the kind of device system, the screen and window size, and the language the browser is set to; the form lists them above its Send button. You can add up to three pictures, such as a screenshot. They are made smaller in your browser before they are sent, which also removes any location hidden in a photo, and they are kept beside the message in the same private place.
The message goes to a private issue tracker that only we can read, hosted by GitHub, and GitHub emails us a copy. We use it only to read and answer you, and we delete it when you ask. You can also simply email pocketvalegame@gmail.com.
Hosting
The site is hosted by Vercel. Like every web server, theirs keep short-lived logs of requests, such as IP addresses and browser types, to run and protect the service.
Changes to this policy
If this policy changes, we will update this page and the date at the top.
Contact
Pocketvale is made by Zdenek Vecek. Write to us through the contact form, or by email at pocketvalegame@gmail.com, with any question or request.
Pocketvale