Games
- Topics / pages opened
- —
- Button clicks
- —
- Approximate active time
- —
These buttons were clicked:
- Explore a puzzle: —
- Build a world: —
An experiment · No background knowledge needed
Explore what clicks reveal using three example pages on this site. Separate observations from guesses, without an anonymity score.
This tab still contains experiment data. A new round replaces it. Example mode leaves it unchanged.
Open a topic that makes you curious right now.
Perhaps you were curious. Perhaps you were just following the instructions. The demo does not know your reason.
A website can save something in the browser and read it again later. That recognizes stored data first, not a person.
Your actual experiment data is in this website’s tab storage (sessionStorage). Reloading does not remove it. Browsers, profiles and other websites do not simply share this storage.
Now an illustrated story: the fictional person Hugo Müller signs in with the same provider. What could the provider connect?
In the example, the provider links identifier A7 to Hugo’s account. Hugo supplied the name himself when signing in.
A7 and Hugo Müller are fictional. We have neither discovered nor asked for your name. This login does not automatically reveal the name to other websites.
A regular website sees the Tor exit’s IP instead of your connection’s IP. This does not make an account or information you provide disappear.
Where you sign in and what you provide also matter. Tor Browser limits further recognition, but does not prevent every form of tracking.
Choosing another topic does not delete existing experiment data. Only “Delete experiment data” removes this experiment.
Without JavaScript, the text and example pages remain readable. Collection and results are then inactive.
Optional: fuller explanations and the original example pages.
A cookie is a small stored piece of information. The browser can send it with matching requests to a website, allowing a server to see an identifier again.
sessionStorage is a note for a website in this tab. The website can read it. It is not automatically sent with requests. This is the storage the experiment uses.
localStorage is another type of website storage in the browser. It can last beyond a single session. These four steps do not use it.
Your data from this box and the three example pages. Only the additional example pages measure active-window time; it proves neither reading nor attention.
No observations yet. Start the experiment and visit an example page.
Only after you start does this box save your topic choices in this browser tab’s session storage. On the three additionally linked example pages, we then count visits, explore-button clicks and time in the active window. The box runs no timer. No other browsing history. No server profile.
The experiment lasts at most 30 minutes. Expired data is removed at the next check on a demo page. “Delete experiment data” lets you clear it sooner. There is no background deletion while the page is closed.
The experiment data is in your browser’s session storage for this tab. That is not a cookie and is not automatically sent with server requests. “Delete experiment data” removes only this experiment.
These values come only from your visits within this exercise. Opening a page again also counts as a visit. Time is a cautious estimate, not measured attention.
We do not know your name. But someone could guess possible interests from the topics you visited. You might simply have been curious, testing things or looking for someone else. The guess can be wrong.
Consider this: you click Travel because you want to compare an image. The demo guesses an interest in travel. The click was observed; your motive was not measured. That gap between data and interpretation is the main lesson of the experiment.
Imagine three independent websites. Each includes the same outside service, perhaps for advertising. That service may connect observations if the browser allows it. It is often called a tracker.
Browser protections can make that connection harder or prevent it. The diagram is only a fictional explanation: our three exercise pages belong to the same website and load no outside tracker.
When you visit a regular website through Tor, it sees the Tor exit’s IP address instead of your own connection’s IP. An IP is an address for a connection. Tor removes that clue to your connection from the website’s view.
Logging in still tells the website which account is yours. Cookies or other saved identifiers may recognise a browser. Tor Browser separates website data and limits other identifying features, but Tor does not prevent every kind of tracking.
Even through Tor, this exercise could observe the buttons clicked here if you start it. Tor does not make actions on the page you are visiting invisible.
A single detail is not a profile. In this fictional example, the provider links identifier A7 to several page visits.
Later, the fictional person Hugo Müller signs in with the same provider and gives their name there. The provider could link the earlier identifier to that account.
A large provider may also connect several of its own services through one shared account. Other websites do not automatically get to see names or cookies. A shared embedded service may connect observations only under suitable conditions. An IP alone does not prove identity.
Tor protects the route and hides your connection’s IP from regular websites. A VPN works differently and is not an equivalent replacement for Tor.
The pages you visit, where you sign in and the details you share also matter. Good technology and thoughtful handling of your own information belong together.
Last updated on 2026-10-13