Search results by country

A result page is assembled for whoever asked for it. The address it came from, the clock in the browser, the language list and the history behind them all feed that answer.

So your own browser tells you what your own browser gets. It cannot tell you what a stranger in Madrid gets.

Two people in the same city can get different pages too. What a profile gives you is a clean look from one country, not the only look there is.

Choose the country a profile leaves through and its clock and language list follow. The table behind that covers 114 countries, and a German profile gets Berlin time with de-DE, de and en.

The link works both ways. Set the language by hand and the clock moves to that country, so nobody ends up reading German results on Moscow time.

The country is not a field you fill in. It is read from the address the profile actually leaves through, and that reading is what decides the clock.

Four providers are asked over an encrypted connection and the first usable answer is kept on the profile. One refusal during a bulk launch must not be left to decide who a profile is.

The start page of a profile carries a row of five checkers. They open inside the same profile, so they read it through its own proxy.

City and provider on that banner come from free public lookups. Those two fields are an estimate, and they are sometimes empty and sometimes wrong.

• BrowserScan

  Address and fingerprint in one report.

• BrowserLeaks

  One interface at a time: canvas, WebGL, fonts, WebRTC.

• CreepJS

  Looks for values that contradict each other.

• Pixelscan

  Looks for the signs of a substituted browser.

• IP2Location

  Where an address database places this exit.

A profile made five minutes ago has no cookies, no history and no cache. That emptiness is read as easily as anything else about the visitor.

The cookie robot spends time on ordinary public sites inside the profile first. Launch nine profiles into one run and you get nine different lists in nine different orders.

A saved flow opens an address, reads a piece of the page into a variable and takes a picture of the window. The picture is a PNG file on this computer.

A schedule repeats it daily, on chosen weekdays, or every 1 to 24 hours. A slot still fires if the app sees it within 30 minutes of its time.

1. 1

   Give the profile its own opening address

   A profile opens on the query you watch rather than on the scenario's site.

2. 2

   Add the three steps

   Go to the address, read the piece you care about, take the picture.

3. 3

   Set the repeat

   Daily, chosen weekdays, or an interval of whole hours.

4. 4

   Read the run afterwards

   The log survives a restart of the app and names the step that failed.

Tick the profiles and launch them together. The queue waits a random 3 to 14 seconds before every opening after the first, so ten countries do not all arrive in the same minute.

Each profile keeps its own cookie jar and its own folder on disk. Ten of them sit open beside each other without one learning anything about another.

How many browsers stay open at once is decided by the memory in your machine. Reaching that ceiling is not a failure: the queue waits for room and carries on.