Privacy Policy

Short, because the site collects very little. Everything below describes what the software actually does.

Last updated October 2026

There is no account

Jumpcade has no sign-up, no sign-in and no password. We never ask for your name, your email address, your phone number or your payment details, and there is nowhere on the site to enter them.

Your favorites, history and streak

The first time you save a game, start one or open your profile page, our server issues a random identifier and stores it in a cookie called jc_uid. Browsing the catalog does not create it. It is httpOnly, which means page scripts cannot read it, and it identifies a browser rather than a person.

Against that identifier we store:

  • The games you marked as favorites.
  • The games you opened, and when. Each launch is recorded together with the analytics identifiers of the visit and your country, as described under Analytics below.
  • Your daily streak: its current length, its longest, and the last day you played.

That is the complete list. We do not store your IP address against it, we do not build a profile from it, and we do not sell, rent or share it.

Games are third parties

Each game runs in a frame served by its publisher, not by us. Inside that frame the publisher and their advertising partners can set their own cookies and collect their own data, under their own policies — we have no visibility into it and no control over it. Currently games reach us through GameMonetize.

If that matters to you, the practical control is your browser: blocking third-party cookies leaves the catalog fully working and affects only what happens inside a game.

Server logs

Our servers keep ordinary request logs — the path requested, the response status, how long it took, and an identifier for the request — so that failures can be diagnosed. They are operational records, they are not joined to your cookie, and they are not used to profile anyone.

Analytics

We measure how the site is used with analytics of our own: a small part of the site's own code reports to our own server, at this same address. There is no third-party analytics service on these pages, and what our analytics records stays on our server.

For each page you open, it records:

  • The page's address, without anything you typed into search: of the query, only the page number and the sort order are kept.
  • Whether it was a “page not found”, and whether your browser had loaded it ahead of time, before you opened it.
  • The site you came from — we keep its domain only — and the campaign tags of the link that brought you (utm_source and the like), if it had any.
  • How long the page was in front of you, how far down you scrolled, and whether you left it by hiding the tab, by opening another page or by closing it.
  • When you press one of a few marked buttons: saving or removing a favorite, opening the daily challenge.
  • Your browser and operating system with their major versions, and your type of device — desktop, mobile or tablet — which our server works out from the user-agent string your browser sends. Our analytics keeps those, not the string, unless the string is an automated program's, such as a search engine's crawler.
  • Your country, and the time of each of these.

On the catalog and in search, it also records:

  • Which game cards were at least half on screen while the tab was in front of you: the games, in the order of the list they were in, at most 48 per list, sent when you leave the page or switch away from its tab.
  • When you click a game card, which list it was in and its place in that list; when you click a link to a category, the category and which part of the page the link was in.
  • When you open search, and when search shows results: how many characters your search had and how many games it found — never the words you typed. If you then pick a result, the game and its place in the results.
  • When you change the order of a list or go to another of its pages: the new order or the page number.

For each page, it also records how fast it loaded and how quickly it responded: the speed measurements your browser itself reports — Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift, First Contentful Paint and Time to First Byte — as numbers, and whether it was a full page load or a page opened inside the site without one.

Once per visit in a tab, it also records a few coarse facts about the browser:

  • The width of the window, as one of five size classes — under 360 pixels, under 640, under 1024, under 1440, or wider — not the size itself.
  • Whether the device has a touch screen.
  • The language your browser is set to, as its two- or three-letter code — “pt”, not “pt-BR”.
  • Whether cookies are enabled, and whether our analytics cookie was already there when the visit began.
  • Whether the browser says it is being controlled by automation software, which is how we tell automated visits from people's.

When you start a game, it records:

  • The press of the button that starts it, with a random identifier for that one launch.
  • When the game's frame was added to the page and when it finished loading — or that it had not loaded after 20 seconds.
  • While the game stays on the page and the tab is in front of you, a signal every five minutes.
  • When the frame goes away: whether it had loaded, how long it was on the page, and how long it was in front of you.
  • If our server could not record the launch, the status code of that failure.

When something on our pages fails — a script error, or a request to our server that gets no answer or a server error — it records what kind of failure it was, whether the script was ours or someone else's, the name of our file and the line, and, for a request, which of our routes it was (/api/v1/me, say) and the status code. In place of the error message it sends a short code computed from the error's type and those details, so the same fault is counted once. The message and the stack trace are never sent, and no more than five errors are recorded per page.

To tell visits apart, it sets one analytics cookie, jc_vid: a random identifier, not derived from anything about you or your device, which expires 390 days after it is set. For the visit in a single tab it also keeps a random session identifier, jc_sid, and a running count of the events it has sent, jc_seq, in your browser's session storage, where they disappear when the tab is closed; each page view also gets a random identifier of its own, kept only while the page is open. When you start a game, our server records the launch with the visit's identifiers and the launch's own alongside jc_uid — that is how a launch is tied to the visit that led to it.

Our analytics does not keep your IP address. Your country comes from a header that Cloudflare, the network our site is delivered through, adds to each request; we keep the country code, not the address.

Analytics events are deleted automatically: those of visits we recognise as automated programs after 30 days, all others after 13 months. Game launches are kept for 25 months.

There is no advertising network of our own on these pages — no tracking pixel, no tag manager, no fingerprinting. The browser facts above are coarse on purpose and are not used to recognise a browser: your screen, your fonts, your time zone and the like are not read at all. If any of that changes, this page changes with it before the code ships.

If you would rather not be counted, open your browser console on this site and run localStorage.setItem('jumpcade:analytics-opt-out', '1'). From then on our analytics stores nothing and sends nothing, and it removes jc_vid and its session values if they are already there. Game launches are still counted, because play counts rank the catalog, but they are no longer tied to a visit. The setting stays until you clear it: localStorage.removeItem('jumpcade:analytics-opt-out') turns counting back on.

What is kept in your browser

Everything our pages store in your browser, and what each item is for:

  • jc_uid — a cookie set by our server: the identifier behind your favorites, history and streak.
  • jc_vid — a cookie set by our analytics: a random visitor identifier, kept for 390 days.
  • jc_sid — session storage: a random identifier for the visit in one tab, gone when the tab is closed.
  • jc_utm — session storage, only when the link that started the visit carried campaign tags: those tags, gone when the tab is closed.
  • jc_seq — session storage: how many analytics events this tab has sent, so that one lost on the way shows as a gap; gone when the tab is closed.
  • jumpcade:recent-searches — local storage: your last five searches, so the search page can offer them again. The list itself is never sent to us.
  • jumpcade:analytics-opt-out — local storage, only if you set it: tells our analytics to stay off.

The cookie policy says what clearing each of them costs.

Erasing what we have

Clear cookies and site data for this site in your browser. The identifiers are gone: jc_uid, and with it every way we have of connecting the stored favorites, history and streak to you; and jc_vid with the session values, so your later visits are not connected to earlier ones. You can also write to the address published on our contact page and ask us to delete the favorites, history and streak record — send the request from the browser holding the cookie so we can tell which one to remove.

Children

The site is general audience and collects no personal information from anyone, including children. There is nothing here for a child to enter about themselves.

Changes

When this policy changes, the date at the top changes. We do not have your email address and so cannot notify you — checking this page is the only mechanism, which is a good reason for us to keep the policy this short.