What this site is trying to do
Sourdough Start is built to help users make better next-step decisions around starter health, fermentation timing, loaf troubleshooting, hydration interpretation, and schedule fit. That product promise is intentionally narrow. Because the promise is narrow, the data posture should be narrow too.
In ordinary use, the site only needs small process inputs such as room temperature, starter behavior, dough timing, hydration numbers, or loaf symptoms. Those are not identity-building signals. They are part of the visible decision flow of the tools themselves.
What normal use should involve
Normal use should involve the smallest amount of information required to make a tool result useful. A baker enters signals about the process, receives an interpretation, and decides what to do next. That relationship does not require a large personal profile, broad behavior tracking, or hidden collection layers unrelated to the stated product purpose.
Technical data and infrastructure
Like most websites, limited technical request data may still exist for hosting, caching, abuse prevention, diagnostics, or performance stability. Those technical layers are part of normal delivery, but they should remain operational and restrained rather than becoming a quiet expansion of tracking scope.
What the site should avoid
The site should avoid collecting expansive identity data, quietly growing a broad behavioral profile, or creating a hidden account model just to make a baking tool appear more sophisticated than it is. If the visible product promise stays narrow, the invisible technical posture should stay narrow too.
Why this page matters
A privacy page should help a normal visitor understand what kind of relationship the site is trying to create. If it becomes too vague, too decorative, or too detached from the real product model, it stops supporting trust. On this site, privacy is part of the public maintenance posture, not a box to tick and forget.