🕒Timezone and language follow your proxy

A clock that disagrees with the address is the loudest mismatch there is. A browser claiming to be in Toronto while its clock says Berlin is a contradiction a site can check in one line of JavaScript, and a rotating mobile proxy creates that mismatch by itself every time the address moves.

So LoginDeck decides the timezone from the proxy, not from your computer.

🕒 The clock#

The profile editor's Timezone tab has two positions:

• Match the exit IP (the default). At every launch, LoginDeck asks through the proxy where that exit is and starts the browser in that zone. You never set it, and it keeps up with a proxy that moves.
• Set manually — type a zone such as America/Toronto. Use this only when you know the exit's real location and the lookup gets it wrong.

The zone is handed to the browser as its own clock, so Date and the internationalisation APIs agree with each other. Overriding one and not the other is a classic mismatch that detectors look for.

When the lookup can't answer#

If the proxy does not answer the lookup, the profile still opens — on its last known zone — and a red message appears: "{profile} opened on its stored clock ({zone}) — the exit lookup through the proxy did not decide it: {reason}. If the proxy exits elsewhere, checkers will flag the time zone."

That is worth reading rather than dismissing. Common reasons are a proxy that rejected its credentials, a proxy that timed out, or no internet connection on this computer at all. Fix the proxy (A proxy won't connect) and launch again.

A profile bound to a phone that is in the middle of changing its IP is a special case: the tunnel is down, so the exit is not asked at all and the stored zone is used. The next launch picks the new zone up.

🗣️ The language#

Language lives on the editor's Overview tab and offers eight values: en-US, en-GB, en-CA, fr-CA, fr-FR, de-DE, es-ES, pt-BR.

LoginDeck sets it for you when you confirm a proxy inside the editor:

1. Open the profile's Proxy tab.
2. Pick a Saved proxy, or type a One-off proxy URL, and let the check run (it runs by itself when you pick a saved proxy or leave the URL field, or you can press Check / Check proxy).
3. On success a message appears: "Matched to {city}, {country} — {language}, {timezone}". The Language dropdown and the timezone now match the exit.

Picking a Phone on the Proxy tab does the same thing, using the country from the phone's last IP check.

The country-to-language map:

It is a starting point, not a lock — the dropdown still works, and a Québec exit that should be fr-CA is a one-click change afterwards.

🌍 Location permission#

LoginDeck matches the timezone and the language. It does not hand the browser a set of GPS coordinates — if a site asks for your location, the browser asks you, the same way any Chrome does. Denying it is the safe answer; a granted location that disagrees with your exit address is worse than no location at all.

✅ Checking it landed#

Run the fingerprint check on the profile. Under Location it reports:

• Exit address — the address the browser really came out on.
• Browser timezone — the zone the browser is running in.
• Timezone vs exit IP — the row that matters. It fails when the clock and the address disagree.
• Clock matches its own zone — catches an override applied to one clock API and not the other.

ℹ️ Good to know#

• Changing Language rebuilds the profile's machine from the same seed, so the graphics card, screen and cores stay as they were and only the locale changes.
• The profile reports a full language list (en-CA, en, for example), because a real browser never reports the bare region tag on its own.
• Chrome ships no Canadian-English interface, so an en-CA profile runs the US English interface with a Canadian locale — which is exactly what a real Canadian machine shows.
• A manual timezone that contradicts the exit is a contradiction you have chosen. If you set one, check that the proxy really exits where you think it does: Check proxies and see where they exit.