Essential cookies

Always active — no consent required

These are strictly necessary for the platform to function, and we set them without asking because the service cannot work without them. They include the authentication session token, where to take you back to after you sign up, the neighbourhood you are browsing, your data-saver setting, the install-prompt counter, an offline copy of the app, and the identifier we use to record what you chose on this banner.

Examples: sb-*-auth-token (Supabase session) · onboarding_next (the page you were heading to when you signed up, so we can take you there afterwards — set by our server, not readable by scripts on the page, and deleted after 30 minutes or once used) · selectedSuburbs and homeSuburbId (which neighbourhoods your feed shows) · nbhd_suburbs (a cookie holding those same neighbourhoods, so our server can show your feed on the first load — it expires after a year) · naartjie:browse-area (an area you are looking around in — kept only until you close the tab) · naartjie:data-saver (image quality) · pwaDismissed, pwaSnoozedUntil, pwaVisitCount (so the “add to home screen” prompt does not keep reappearing) · naartjie_pwa_installed_seen (so opening the app from your home screen is counted as an install only once on this device — it holds no identifier) · naartjie:pushSnoozedUntil (so we do not ask about notifications again for 30 days after you say “Not now”) · naartjie:consentId and naartjie:cookieConsent and naartjie:cookieConsentVersion (your choice on this banner, the proof of it, and which version of this notice you were shown — if we change the notice we ask you again) · naartjie:consentLinked (once you are signed in, a note that this choice has been attached to your account, so we do not send it again — kept only until you close the tab)

Offline copy: naartjie-v5 (the app's files, the first page of your feed and the last 20 listings you opened, kept in your browser's cache storage so Naartjie still opens when you lose signal. Signed-in pages such as your settings and chats are never kept, and logging out clears the saved pages. It stays on your device and is never sent to us; it is replaced when a new version of the app ships, and clearing this site's data removes it.)

The consent identifier is used for nothing except storing and evidencing this choice — it is never joined to any other record. We keep it for 3 years so we can show what you agreed to.

Drafts and history kept on your device

Always active — no consent required

These hold work you have started and things you have already looked at, so you can carry on where you left off. They stay in your browser, and clearing your browser data removes them.

If you are signed in, your recent searches and the listings you opened are also saved to your account so they follow you to your other devices. We keep them for 90 days, and you can remove them one at a time or all at once.

Examples: naartjie_post_wizard (an unfinished listing) · biz_register (an unfinished business registration) · naartjie_recently_viewed and naartjie_recently_viewed_ids (listings you opened) · recentSearches (your recent searches) · naartjie_community_seen and naartjie:community-areas (which community posts you have already seen, and which neighbourhoods your community feed shows) · safety-tips-chat-{conversation} (you closed the safety tips in that chat)

Analytics cookies

Activated with your consent

We use Google Analytics and Vercel Analytics to understand how users interact with Naartjie (pages viewed, features used, errors encountered). Both load only after you accept analytics cookies, and we enable IP anonymisation on Google Analytics, which sets the _ga and _ga_* cookies. When you withdraw, both stop straight away and we delete those cookies.

We also record our own product events (which screens are opened, where people stop during posting). If you are not signed in, those carry a random analytics id (naartjie:anonId) only while your consent stands, and no id at all without it. If you are signed in, they are also linked to your account whatever you choose here — our Privacy Policy explains this under legitimate interests. Withdraw consent and the analytics id is deleted from your device, and the events already recorded with it are anonymised straight away. This data is used in aggregate to improve the service and is not used to identify you individually.

If you reached Naartjie from a link, a flyer or a QR code that carries a ?src= tag, we keep that tag (naartjie:src) so we can tell which of those brought you here. It records the channel, not you — there is no identifier in it. It is stored on your device only after you accept analytics cookies; before you choose, it is held in memory for that page only and never written to your device. Decline or withdraw and it is deleted.