Without your choice, we only set cookies that the site needs to work, and one short note when you create an account (see below). Advertising cookies from Meta and Google are set only if you choose Accept in the cookie banner on our website (see Advertising cookies). The other parts of the site that involve other companies are signing in with Google, Microsoft or Apple and connecting another service such as Jira or Slack, if you choose to (see Cookies we set), the property map (see Google Maps and Street map pictures below), the check against automated scripts on our forms (see Cloudflare Turnstile) and visit counting, which sets no cookie (see Counting visits).
Cookies we set
- Keeping you signed in. One cookie remembers that you're signed in, so you don't have to sign in on every page. It is strictly necessary, sent only over a secure connection on the live site, and can't be read by the page's scripts. You stay signed in until you sign out: each time you use the site, the cookie is renewed. A browser keeps a cookie for at most 400 days, so if you don't use the site in that browser for that long, you sign in again. Changing or resetting your password, or signing out of all your devices, also ends it. Accounts of NEMZION staff are signed out after 12 hours, or 30 minutes without use.
- Connecting another service. While you connect an integration (for example Jira or Slack), a short-lived cookie checks that the reply comes from the request you started. It is strictly necessary, can't be read by the page's scripts, and expires after 10 minutes.
- Signing in with Google, Microsoft or Apple. While you use one of these, short-lived cookies keep the sign-in together: one checks that the reply comes from the sign-in you started (10 minutes); one carries Apple's reply back to our page (2 minutes); one holds a new account's sign-in while you finish signing up (20 minutes); and one shows that you have just confirmed it's you, when you use the provider to confirm a change to your account (5 minutes). Each is removed when the step ends or expires after that time. They are strictly necessary, sent only over a secure connection on the live site, and can't be read by the page's scripts.
- Pages opened from the NEMZION app. When the app opens one of our web pages, one cookie remembers that the page is shown inside the app, so it looks like the app and shows no prices. It holds only that fact. It is strictly necessary for that, can't be read by the page's scripts, and ends when the in-app browser is closed; when the app signs you in to the website, it lasts 2 hours on Android and up to 400 days on iPhone and iPad (where the app's browser keeps its own cookies, apart from Safari's).
- A new account on our website. When you create an account on our website, one cookie notes just that: it holds no name, email address or account number. If you choose Accept, Meta and Google are told that an account was created, once, and the cookie goes. If you choose Reject, or have already, it goes unsent. Otherwise it ends after 7 days.
Advertising cookies (Meta and Google)
We advertise NEMZION on Meta (Facebook and Instagram) and Google (YouTube, Discover, Gmail and Search). To see which ads bring people to our website, we use the Meta Pixel and the Google Ads tag on our public pages. They load only after you choose Accept in the cookie banner. If you choose Reject, or don't choose, they don't load and none of these cookies are set. If your browser sends Global Privacy Control, we treat that as Reject unless you choose Accept.
After you accept, your browser sends Meta and Google the pages you view on our public website, and these moments: an account was created on our website, a free trial started, a plan was bought on our website, a one-time visit was bought on our website (with its price), or the free property checklist was requested (never the email address you gave for it). They are sent from a page of our own that holds nothing but the moment, so the address of the page you were on in your account isn't sent. We never send them your name, email address, phone number, your property records or anything you store with us. Meta and Google also receive your IP address and the usual browser details, and use this information under their own terms to measure and improve our ads, to show you our ads on other sites and apps, and to personalize the ads you see (Meta's privacy policy, Google's privacy policy). The cookies they set on our site:
| Cookie | Provider | What for | How long |
|---|---|---|---|
| _fbp | Meta | Tells Meta it's the same browser across visits, to measure our ads | 90 days |
| _fbc | Meta | Keeps the ID of the Meta ad you clicked to reach us | 90 days |
| _gcl_au | Links an action on our site, such as creating an account, to the Google ad that brought you | 90 days | |
| _gcl_aw, _gcl_gb and similar | Keeps the ID of the Google ad you clicked to reach us | 90 days |
Meta and Google may also set or read their own cookies on their own sites when these tags run, under their own policies.
Changing your choice. Choose Cookie settings or Your Privacy Choices at the bottom of any page of our website to open the banner again, then Accept or Reject. If you change to Reject, the tags stop sending and we delete their cookies on our site. You can also delete cookies in your browser's settings, which brings the banner back.
Cloudflare Turnstile
Our sign-in, sign-up, waitlist and other public forms ask Cloudflare Turnstile whether the person filling them in is a person or an automated script. It runs in your browser when one of those forms opens, sends Cloudflare your IP address and signals from your browser, and may store an item that Cloudflare needs for the check. It is used only to protect the forms, never for advertising or to follow you across sites, under Cloudflare's privacy policy. Pages without those forms don't load it.
Google Maps
The property map, place search and address lookup in your account use Google Maps Platform. When a page with the map opens, your browser loads Google's map scripts and map images from Google's servers. That sends Google your IP address and the usual browser details, along with what you type in the search box and the part of the map you look at. Google may set or read its own cookies when this happens, under Google's privacy policy. Pages without a map don't load anything from Google.
Street map pictures
The street map under the property map is made of small pictures that come from OpenStreetMap's servers, or from another map picture server we name in the privacy policy. When a page with the map opens, your browser asks that server for the pictures that cover the part of the map you look at. That sends it your IP address, the usual browser details, the address of this site and the part of the map you look at. We send it nothing else. Pages without a map don't ask it for anything.
Counting visits
We count visits to our public pages with Vercel Web Analytics. It uses no cookies, doesn't follow you across sites, and we only see totals (pages, countries, where visitors came from, device type). We also count how often a few buttons and links are used, such as the sign-up button, Talk to us and the app store buttons, and which topic a call-back request was about. These counts carry no name, email, phone number or account details. Visit counting uses no cookies; the only cookies for measuring anything are the advertising cookies above, and only if you accept them.
Stored in your browser (not cookies)
- Your Ask NEMZION conversation, in this tab only, until you close the tab, start over or sign out.
- Whether Ask NEMZION is available right now, in this tab only, so the page doesn't check again on every view.
- Support requests you wrote while offline, until they're sent or you sign out.
- The last few support codes the site showed you, so a new support request can include them, until you sign out.
None of this holds your password or anything that signs you in.
The NEMZION phone app
The app doesn't use cookies. It keeps its sign-in in your phone's secure storage. You stay signed in until you sign out, however long it is since you last opened the app. Changing or resetting your password, or signing out of all your devices, also signs the app out. Web pages the app opens use the cookies above, including the cookie for pages opened from the app.
Product statistics are counted on our own servers without cookies and without your name or email.