OpenHome

Cookies

Last updated 20 September 2026

OpenHome sets two cookies and uses three values in your browser's local storage. That is the whole list. There is no advertising cookie, no remarketing tag and no third-party analytics on this site.

1. Everything we set

openhome_session
Cookie. Set when you log in, and only then. Keeps you logged in. Contains a random token and nothing else, no name, no identifier you could read. httpOnly (JavaScript cannot read it), SameSite=Lax, Secure in production, 60 days. Strictly necessary: without it there is no logged-in state. Logging out removes it.
openhome_locale
Cookie. Set only when you switch language. Holds "ka" or "en" so the server renders the right one. SameSite=Lax, one year. Without it we fall back to your browser’s Accept-Language.
openhome_currency
Local storage, not a cookie. Holds the currency you chose to see prices in. Never sent to the server, the conversion happens in your browser.
openhome_theme
Local storage. Holds "light" or "dark" if you overrode your system setting, so the page does not flash the wrong theme before it paints.
openhome_cookie_choice
Local storage. Records that you answered the cookie notice, so it stops appearing. That is all it does.

2. What we deliberately do not set

This is unusual enough to be worth spelling out, and it is one of the reasons this platform exists:

  • No advertising or remarketing cookies. There is no advertising on the platform, so there is nothing to target. You will not see a flat you looked at here following you around other websites.
  • No third-party analytics. No Google Analytics, no Meta pixel, no session-recording tool, no heatmap script, no A/B testing vendor. Which flats you look at is not a fact we hand to anyone.
  • No social login buttons that track you before you press them and no embedded like-and-share widgets.
  • We do count usage, how often a listing is viewed, whether a search returned nothing, but the counting is first-party, lands in our own database, and is tied to a rotating salted identifier rather than to you. See the privacy policy.

3. What a third party can still see

Two things load in your browser from someone else's servers, so those servers see your IP address. We would rather say so than let you find out from a network tab.

  1. 3.1

    The map. When a page with a map opens, the map provider's script loads from the provider and may set its own cookies in your browser under its own domain. We cannot read them. Pages without a map do not load it at all.

  2. 3.2

    Web fonts. The Georgian and Latin fonts are currently loaded from Google Fonts, which means your IP address reaches Google when a page first renders. Self-hosting those two font files removes this entirely, and it is on the list.

  3. 3.3

    Push notifications, if you enable them, are delivered through your own browser vendor's push service.

4. Staying in control

  1. 4.1

    The notice at the bottom of the page defaults to essential only, and declining is the same single tap as accepting. Because we set nothing non-essential, accepting currently changes nothing at all, we would rather tell you that than pretend the button matters.

  2. 4.2

    Logging out removes the session cookie. Clearing site data in your browser removes everything on this page, including your language and currency preferences.

  3. 4.3

    Blocking cookies entirely leaves the site usable for browsing and searching. You will not be able to stay logged in, which means no publishing, no messages and no favourites.

Cookies · OpenHome