Privacy policy
Website dardargames.club · Last updated: October 19, 2026
This policy is for the website. Using the DarDar Games app for iPhone or Android? See the app privacy policy.
On dardargames.club you can play the DarDar Games learning mini games in any browser and read about each game. The website has no accounts and no sign-in, no advertising, no cookies, and no third-party analytics or tracking.
What stays in your browser
Player names and heroes, scores and records, likes and saved games, play time, screen time and sound settings are saved in your browser's storage for this website on this device. They are never sent to us and do not move to other devices or browsers. To delete them: FOR GROWN-UPS → Reset everything, or clear the website data of dardargames.club in your browser settings. In a private window they disappear when the window is closed.
The browser also keeps a copy of the counts, so that they show up without the internet, the dates when the feed was last opened, so that each visitor is counted once a day, the day each game was first played here, so that we know who comes back to it (see below), and how many minutes each player played each game in the last four weeks, so that the feed shows their favorite game first.
On Android and computers the website also installs a small service worker in the browser: browsers ask for one before a website can offer its own button to add it to the home screen. It does not save pages or any data, and pages always load from our server.
What we receive
When a game is started, when a like or a save is added or removed, and when a game's link is shared, the website sends an anonymous event to our server: the name of the game, the kind of event and the kind of device it comes from: iPhone, iPad, Android phone or tablet, or computer. The event also carries a random number made up for that one event, so that if it is sent again, for example after a lost connection, our server does not count it twice. The number is different for every event, says nothing about the device, and our server keeps it for no more than two days.
To put the most enjoyed games nearer the top of the feed, the website also sends the same kind of anonymous event, without the random number, when a game's card has been on the screen for a moment, when PLAY is pressed on it and when the game reaches its second level, at most once per card each time the feed is opened, and, while a game is being played, how many seconds it was really played: only while it is on the screen and the screen was touched in the last minute, together with how smoothly the game ran (frames per second and how many of those seconds were slow), so that we can find games that are slow on some phones. These events also say where the card stood in the feed (first, second and so on) and why it was there: a popular game, a new game, one of the most enjoyed games shown first to someone who has not played yet, this player's favorite game, a game opened by a link or a game picked in the list of games or in the profile. While a game is being played, the website also tells how many hearts were lost and on which level, when a game ended because the hearts ran out, and whether PLAY was then pressed on the same game, on another game or not at all. The event about PLAY also says whether this is the first game on this device today, whether this game is played on this device for the first time or, the first time the device comes back to it on a later day, how many days have passed, and, the first time it is played on a day, how many days have passed since it was first played on this device. The order of the feed is worked out on the device itself, from the counts and from how long this player has played each game and which games they liked or saved; that part never leaves the device.
When the feed is opened, the website also sends an event that it was opened. Besides where it comes from, it says only whether this is the first time on this device today, this week, this month or ever, and, the first time the device comes back on a later day, how many days have passed since its first time. Once a day, the website also tells whether the first screen appeared after loading and whether the feed with the games was reached. The device keeps those dates itself, and we receive only yes or no and that one number. This is how we count how many people use DarDar Games, how many of them get to the games and how many come back, without knowing who they are.
These events contain no name, no account, no device or advertising identifier, no precise location and no scores. Our server notes only the country each event comes from: Cloudflare determines it from the IP address, and we keep just the country, never the address. We add the events up into counts per game, per day and hour, per kind of device and per country. You see them as likes, saves, shares, popular games and the order of the feed; we also see how many people used the app and the website, and from which countries. While the feed is on screen, the website stays connected to our server to receive new counts right away; the connection only tells whether it is the app or the website and the kind of device, and our server notes its country the same way, which shows us how many feeds are open right now and where. The counts cannot be linked to you or to your child.
When the website is opened, it also tells our server where the visit came from: only the name of the site with the link, for example youtube.com, or a tag in our own link. It never sends the address of that page or anything you searched for.
After a level is passed, the website may offer to get the app: on iPhone, a button to the App Store; on Android, a button to add the website to the home screen. It tells our server, with the same kind of anonymous event, whether the offer was shown, pressed or closed, whether the browser allowed adding the website to the home screen (at most once a day), whether it was added, and whether the website was opened from its home screen icon (once a day).
Service providers
Our server runs on Cloudflare. Like any website, Cloudflare processes the IP address of your device to deliver the files, to protect the service from abuse, for example too many events from one address, and to tell our server the country. We do not store IP addresses and do not keep logs of visits. Cloudflare's privacy policy: cloudflare.com/privacypolicy.
Links to other services
DARDAR ON YOUTUBE opens our channel on YouTube, and the App Store badge opens Apple's App Store. There YouTube's and Apple's privacy policies apply. SHARE uses the share menu of your device or copies the link: we do not see where you share it.
Children
The games are made for young children and their families. We do not ask children for personal information and do not collect it. A player name can be any nickname, and it never leaves the device.
If you write to us
When you email us, we receive your email address and your message. We use them only to answer you and delete the conversation when it is no longer needed. Mail to our address is forwarded by Cloudflare Email Routing. To have your emails deleted sooner, just ask.
Changes
If this policy changes, we update this page and the date at the top.