Cookies
None. Not one. Here is what is kept instead and why no banner stands in your way.
Last updated 23 October 2026
In short
This site sets no cookies. Open the storage panel in your browser's developer tools and the cookie list is empty.
Two items sit in local storage: the pixel ecosystem's state, so the swarms are not strangers every time you arrive, and the visit count's item, so the site counts each person once a day and each visit once.
No banner: neither item identifies you or leaves your device, and neither is used to advertise or to follow you.
Cookies
There are none. Not a functional one, not an analytics one, and certainly not an advertising one.
Nothing on this page can follow you to another site.
What is kept in local storage
tabbara.eco, written by the background engine. It holds:
- a version number for the record's own shape,
- a visit count for this browser,
- the swarms' energy and affinities,
- which rare shapes have already been shown,
- one flag for whether a particular creature has been provoked.
It never leaves your device. If storage is unavailable, blocked or full, the engine carries on without it and the ecosystem simply starts fresh on each visit. Every read and write is guarded, so a browser that refuses is not a browser that breaks.
va, written by the visit count: the day this browser was last counted, with a random code for that day (a new one every day), and the visit in progress (when it started, where it came from, the pages opened, the time spent and the links tapped), so each counts once. It holds nothing about who you are; the day's code goes to tabbara.moe only, once a day.
How visits are counted
The site counts its own visits and keeps only totals for each day: how many people came and how many visits, the pages opened, the site or app a visit came from (its name only, such as Google or Instagram, and the campaign word if the link carried one), the country, the kind of device, the browser, system and language, how long the page stayed on screen, which links were tapped, and how fast the page showed. A visit sends two short messages to tabbara.moe, one as it starts and one as you leave, and nothing about the visit itself is kept once its numbers are added in. No cookie is set and the site keeps no network address and no identifier: to count a browser once a day it keeps a scrambled key made from the address, the browser and the day's random code in va, and deletes it two days later. With Do Not Track switched on, the page sends nothing at all.
Cloudflare, which serves the site, also adds its Web Analytics beacon. It is cookieless: it counts page views and sets nothing on your device.
Why there is no banner
Consent is what a site needs before storing something on your device for its own purposes, and above all before advertising or cross site tracking. Neither happens here.
The ecosystem's record exists to make the thing you are looking at behave the way it was designed to, and the visitor mark only stops the site counting you twice. Neither identifies you. A banner in front of that would be a click in your way and nothing more.
What a page loads from somewhere else
Almost nothing. The stylesheet, the engine, the icons, the card thumbnails, the 5x7 typeface and the visit count all come from tabbara.moe. The one exception is the Web Analytics beacon Cloudflare adds to the page, described above.
There is no typeface from Google, no library from a public network, no embedded video and no social widget. The face you are reading was drawn for this site and is served from it.
Clearing it
Your browser's Clear browsing data control removes both items, after which your next visit is counted once more. A private window never keeps them in the first place.
A content blocker may stop the analytics beacon. The page works the same either way.