Privacy
Last updated 5 September 2026
You never give us anything. There is no account, no sign-up, no email box, no password and no payment. We could not identify you if we wanted to.
Your game progress stays in your browser. Best scores, badges, settings — they are written to your device and never sent anywhere.
We do count how many people play, and for how long. That goes to Google Analytics, and it is the only thing we collect.
This page is written from the code rather than from a template, so it is specific
about what actually happens. Everything below is checkable — the file that does
the measuring is analytics.js,
it is about three hundred lines, and it is the only place in this site that talks
to anyone.
Every game saves your progress with your browser's local storage. Best lap, badges earned, sound on or off, which view you prefer, how far through a puzzle you are. Thirty of the pages here use it.
None of it is ever transmitted. It sits on the device you played on, it does not follow you to another browser, and we cannot read it. Clearing your browser's site data deletes it, and the only thing you lose is your own progress.
One more key is written the same way: kreeda.played.<game>, a timestamp
of the last time you really played each game. It is what fills the "Jump back in" shelf on
the home page. That shelf is assembled in your browser, from your device, and the list of
what you have played is never sent to us.
The games where people type things about each other.
Circle Quiz, Group Blind Spots, Who Said That, Herd Mind, Impressions, Memory Lane, Time Capsule, Duo Quiz, Blind Spots, Share or Take, Life Auction and Deep Talk all ask players to type names, answers and predictions about their friends.
Not one of those twelve games makes a single network request. The names and the answers exist in the page you are looking at and nowhere else. We have never seen any of them, and there is no code that could send them.
Two things measure this site, and both run on every page.
Standard web analytics: a page view when you open a game, plus the session and engagement events Google records itself. Alongside those, this site sends a few of its own:
| What it records | What it means |
|---|---|
game_time | How many seconds of active play, reported every thirty. The clock only runs while the page is visible and you have touched something in the last few minutes — a tab left open on a second monitor overnight counts as almost nothing. |
played_30s | Once per page, when active play passes thirty seconds. This is the one number the whole site is judged on: did someone actually play, rather than merely arrive. |
game_start, game_end | A round began or finished, sometimes with its length or outcome. |
game_click | Which card you tapped on the home page. |
| Per-game events | A handful of small ones — a race started, a badge earned, a puzzle completed with its score. Numbers and short labels only. |
Every one of those carries the game's folder name and its title, so we can tell Drift from Carrom. No event carries anything you typed. The most personal thing in any of them is a score.
Google itself also receives what it receives from any site using Analytics: your approximate location from your IP address, your device and browser, the page you arrived from, and a random identifier stored in a cookie so that two page views can be recognised as one visit. We see this only as aggregate numbers.
We advertise Kreeda on X, and X's pixel — uwt.js — runs on every page so that
when we pay for a click, we can tell whether the person who clicked went on to play. It
records the page view and, if you play for thirty seconds, that fact. It sets its own
cookies, and X receives your IP address and device information as it does on any site
carrying it.
It exists so we can stop paying for advertising that does not work. If it is blocked, every game still runs perfectly — nothing here depends on it.
When we post about a game on X or Facebook, the link carries markers saying which post it came from. That is how we learn that a particular Tuesday post about Carrom brought people who actually played. The markers describe the post, not you.
Almost every game here is a single self-contained file that loads nothing from anyone. Three are exceptions, and a request to another company's server always reveals your IP address to them:
That is the complete list. No other page contacts anyone but Google Analytics and the X pixel described above.
Kreeda is a general-audience games site, and some of it — the daily chemistry and energy grids — is written with secondary-school students in mind. It is not directed at children under 13, we do not knowingly collect anything from them, and since we collect no names, no email addresses and no accounts from anyone, there is nothing here that could identify a child. If you are a parent and would like the analytics off, any content blocker will do it.
Kreeda has no server of its own and no database. The site is static files served from GitHub Pages. The measurements described above are held by Google and by X on their own infrastructure under their own policies, and we read them only as totals.
Questions, or a request to have something removed: patavardhan@gmail.com.
If this page and the code ever disagree, the code is the truth and this page is the bug — please tell us.
If what we measure changes, this page changes with it and the date at the top moves. The whole history of both this page and the code that it describes is public, so you can see exactly what changed and when.