Cookie Policy

The browser-side footprint should stay as small as the product promise.

A small sourdough decision tool should not quietly grow a broad tracking posture. This page explains the intention to keep technical behavior proportionate and reviewable.

Essential technical behavior

Like many websites, limited browser-side or infrastructure behavior may still exist for security, caching, or performance. That does not automatically change the character of the product, but it does mean the technical layer should remain visible and explainable.

What should stay small

If the site uses measurement or analytics, they should stay proportionate to a narrow fermentation tool. The product should not drift into heavier ad-tech style tracking without making that change visible and revising the public explanation.

Why this page belongs here

A serious review should not have to guess how a small baking tool handles browser-side behavior simply because the site is not large. Trust still needs visible explanation even when the product itself is focused and modest.

The smaller and narrower the product is, the easier it should be to justify a restrained technical posture. That is the principle this page is meant to defend.

How policy and behavior should stay aligned

If the site later gains heavier analytics, ad scripts, or more persistent storage behavior, this policy needs to expand with the real technical posture instead of staying frozen in an older state.