Privacy in Tukuk-OS: Why There Are No Tracking Cookies

From Tukuk-OS Wiki, the free knowledge base.

Why Tukuk-OS was designed without user tracking: what is not collected, what is stored, and how we keep search quality without profiling anyone.

When you use most search engines you are the product. Your search history builds a profile that is later sold to advertisers. Tukuk-OS was built on the opposite belief: you are a user, not a product — and its privacy design reflects that decision from the very first line of code.

What Tukuk-OS Does Not Collect

To be explicit:

• No tracking cookies. No analytics cookies, no cross-session user identifiers, no third-party trackers measuring you.

• No user profiles. No accounts, no search history tied to you.

• No data sales. No data sold to anyone because no personal data is collected to sell.

• No targeted remarketing. The ads you see are not based on you — they are based on the page you are reading.

You can verify this yourself: robots.txt, the page source, and privacy.html all explain the same thing openly.

What Is Stored (And Why)

Absolute purity is impractical for running a web service. Tukuk-OS does store:

• Standard server logs — IP address, path, time, and response code. These are needed for security (detecting abuse), maintenance (diagnosing errors), and enforcing rate limits. Logs are rotated regularly so no long history is kept.

• Search result caches — stored per query, not per person, and without session identifiers.

• Theme preferences — stored in your browser (localStorage), never sent to the server.

The key difference: nothing stored can be used to build a profile about who you are, because no identifier links your session to any other session.

How Search Quality Works Without User Data

This is the question I receive most. The answer: search quality depends on content and the index, not on your habits. Tukuk-OS's relevance score is computed from page structure — titles, headings, phrase matches — not from who you are.

There is no personalised "filter bubble" where you only see what you already believe. Everyone sees the same results for the same query, and that should be the default behaviour of any search engine.

Performance Impact (Actually Positive)

A common assumption is that privacy hurts performance — that without tracking you lose optimisation ability. My experience shows the opposite.

With fewer third-party scripts, Tukuk-OS pages load faster and jank less while being read. No analytics script runs while content is being displayed, no tracker waits on the network during the first paint. When you remove all of that the page becomes light in a way users feel immediately.

On the server side, because no session identifiers need to be built and maintained for each user, every request is stateless — no session to store, no session to refresh. This makes the server design simpler and easier to scale.

The same applies to caching: because results do not vary by user, the same search result can be shared by everyone. One popular query is served once from cache and shown to a hundred searchers — savings that would be impossible if every user saw their own version.

Advertising Without Tracking

Tukuk-OS displays ads through a standard advertising network to cover operating costs. The important part: ad impressions are not targeted at you based on your history, because that history does not exist on our side. If you see an ad it is because of the page you are reading, not because of you.

If you do not want to see ads at all, your ad blocker works here like anywhere else — we do not block it and we do not ask you to turn it off.

Privacy Is Not an Add-On

The biggest lesson from this work is that privacy cannot be bolted on at the end of a project. If you build a system that collects user identifiers from day one, "removing" them later means rebuilding half the system — and the already-collected history still exists somewhere.

Instead, if you start with the assumption that no personal data needs to be stored, every design decision afterwards becomes easy: no session manager, no identifier encryption, no data deletion process (because there is nothing to delete), and no awkward answers when someone asks "what do you keep about me?".

The answer is short, honest, and easy to understand — and that posture itself becomes a product advantage. People are increasingly aware of who tracks them, and the ability to answer honestly is something bigger services find increasingly hard to match.

See also

• Tukuk-OS Is Alive: Reflections From Broken Laptop to Working Search Engine
• What Is Tukuk-OS? What This Search Engine Actually Does
• Tukuk-OS Complete Feature Tour: From Web Search to Space Data
• Image and Video Search in Tukuk-OS: How It Actually Works
• The Tukuk-OS Blogging System: How Content Is Written, Stored and Served
• Tukuk-OS Automation: Backups, Watchdogs and Self-Monitoring