The ozjam.com website

Cookie Policy

The short answer: this site sets no cookies. This page explains what that means, the single small entry it keeps on your device instead, the one request that leaves for Google’s font servers, and how to clear all of it in under a minute.

Effective date Applies to the ozjam.com website

The short version

This site sets no cookies at all: none for analytics, none for advertising, not even a session cookie. There is nothing to accept, nothing to reject and no preference centre to wade through, because there is no tracking here to switch off.

One small entry is written to your browser’s local storage, and only so the site behaves sensibly: it remembers whether you are reading in Turkish or English. It stays on your device and is never sent to our server. It is listed in full below.

One request does leave your browser for somebody else: the two typefaces this site uses are loaded from Google Fonts. That has its own section below, along with how to stop it.

A cookie is a small piece of text a site asks your browser to keep and then hand back with every request to that site. That round trip is what makes cookies useful — it is how a shop remembers your basket and how a site keeps you logged in — and it is also what makes them a tracking tool, because the same mechanism lets a third party recognise your browser from page to page, and from site to site.

ozjam.com needs none of it. There is no account to log into, nothing to buy and no basket to remember. The site is a set of plain HTML files sitting on ordinary shared hosting; no application framework is running, so there is no session to keep alive and therefore no session cookie. We run no analytics, so there is no analytics cookie. We sell no advertising on the website, so there is no ad network here to drop one. Even the contact form posts to a small script that e-mails us the message: it starts no session and writes nothing.

So the honest version of a cookie banner for this site would read: there is nothing here to consent to. We would rather write that down than talk around it.

The one entry kept on your device

Local storage is a different mechanism to a cookie. It is a small key-and-value area that belongs to one site, is readable only by pages on that site, and — the part that matters — is never attached to a request by the browser. Nothing in it travels to our server. The site writes exactly one entry:

Key What it holds What it is for How long it stays
oz-lang Two letters: tr or en. Remembers the language you picked with the TR/EN switch in the menu, so other pages and your next visit open in it. Until you clear it. There is no expiry date.

That is the whole list. No session storage, no IndexedDB, no service worker, no offline cache, no fingerprinting script. The site does not even need JavaScript to be readable: the English text is written into the HTML itself, and the Turkish is swapped in afterwards.

If local storage is blocked outright — a private window in some browsers, or storage switched off in your settings — the site notices and carries on: it takes the language from your browser.

Google Fonts — the one outside request

This site uses two typefaces — Plus Jakarta Sans and Inter — and loads both from Google Fonts. Your browser therefore makes requests that do not go to our server: the stylesheet comes from fonts.googleapis.com and the font files themselves from fonts.gstatic.com.

Like any web request, those carry the information a server needs in order to answer them, which means Google receives:

  • your IP address;
  • your browser, its version and your operating system (the user agent);
  • the address of the page asking for the font, plus your language and font-format preferences.

Google states that the Fonts API sets no cookies and that the font files are served from a separate, cookie-free domain; the detail is in the Google Fonts privacy note. Nothing comes back to us from those requests: no visitor counts, no addresses, no report. But the request happens, so we write it here rather than leave it out.

If you would rather it did not, block it: a content blocker, a tracker-blocking browser, or an extension that stops third-party requests will all prevent the download. The site then falls back to the closest system font on your device — Segoe UI on Windows, San Francisco on Apple platforms — and everything else looks and works exactly the same.

What this site does not do

For completeness, here are the things a modern site is assumed to do that this one does not.

  • No analytics of any kind — no Google Analytics, no Plausible, no Matomo, and no counter of our own.
  • No advertising, retargeting or conversion pixels. The website carries no ads.
  • No social buttons, embedded videos, comment widgets, chat bubbles or map frames; each of those would mean another company’s script.
  • No A/B testing, heatmaps or session recording. Nobody is watching your mouse move.
  • No fingerprinting, and no attempt to recognise you between visits.
  • No newsletter pop-up, and no mailing list to add you to.

The whole site is static files. Apart from the fonts, everything it loads — the stylesheet, the two small scripts, the images — comes from ozjam.com.

Server logs and the contact form

Two things happen on the server side that are not cookies but are worth knowing about. A cookie policy that skipped them would be technically true and practically useless.

Access logs. Like every web server, the machine hosting ozjam.com writes a line for each request: IP address, timestamp, the address requested, the response code, the referring page and the browser identification. This is standard hosting-provider behaviour, it is kept for security and troubleshooting, it is deleted on the provider’s own schedule, and it is not combined with anything else to build a profile of you.

The contact form. When you send it, the message goes to a small script that forwards it to us as e-mail. Nothing is written to a database, no session is started and no cookie is set. What we are left holding is an ordinary e-mail, which we delete once the matter is closed. The detail is in the website privacy policy.

Seeing and clearing what is stored

Everything on this page lives in your own browser, which means you can look at it and delete it yourself, without asking us.

From your browser settings

  • Safari on iPhone and iPad: Settings › Safari (on recent iOS versions, Settings › Apps › Safari) › Advanced › Website Data, then swipe the ozjam.com row to delete it — or use “Clear History and Website Data” to clear everything.
  • Safari on a Mac: Safari › Settings › Privacy › Manage Website Data, search for ozjam.com and remove it.
  • Chrome or Edge: the icon at the left of the address bar › Site settings › Delete data. To clear everything at once, Settings › Privacy and security › Delete browsing data.
  • Firefox: Settings › Privacy & Security › Cookies and Site Data › Manage Data, select ozjam.com and remove it.

If you want to look first

On a computer, open your browser’s developer tools (F12, or Cmd-Option-I on a Mac), go to the Application or Storage panel, and expand Local Storage › https://ozjam.com. You will see the two entries above with their values, and nothing else.

What changes afterwards

Very little. The site forgets which language you chose and falls back to your browser’s language on the next page you open, and the notice at the bottom introduces itself once more. Nothing else is lost, because nothing else was stored.

If you want a particular language without storing anything at all, add ?lang=tr or ?lang=en to any address on this site. That wins over everything else for that visit, and it is what makes a link you share open in the language you were reading.

In a private window, all of it is discarded the moment you close the window anyway.

The Warry app is a different matter

This page covers the website. Warry, our iOS app, is not a web page and uses no cookies either — but it does show a single banner ad through Google AdMob, and ad networks identify devices with an advertising identifier rather than with cookies. Different mechanism, different page.

How that works, what Google may process, and where the iOS App Tracking Transparency prompt fits in is set out in the Warry privacy policy. Everything else Warry holds — items, photos, receipts, prices and notes — stays in the app’s own storage on your device and never reaches us.

Changes to this page

If the site ever starts setting a cookie, gains an analytics tool, or picks up another third-party script, this page changes first and the effective date at the top moves with it. We would rather lose the boast than quietly break the promise.

There is no notification list to join, for the reason this whole page describes: we do not know who you are. The date at the top is the record.

Contact

If you have a question about anything here, or think we have got something wrong, write to support@ozjam.com. One person reads it and replies, usually within a day, in Turkish or English.

What the site does with the rest of your data is in the website privacy policy, and the legal basis under Turkish law is set out in full in the KVKK disclosure.


This page is provided for information; it is not legal advice and has not been certified by a lawyer. The Turkish and English versions are kept in step; if they ever differ, the Turkish text prevails for users in Türkiye.