How this site approaches cookies, analytics, and browser-side storage.
Ergo Workspace is maintained as a focused ergonomic decision site rather than a profile-building platform. The goal of this policy is to explain, in direct language, how cookies or similar browser-side technologies may be used, what role they serve, and what kind of restraint the site is meant to follow. A cookie policy matters here because visitors should not have to guess whether a small tool site is quietly doing much more tracking than its visible product purpose would suggest.
The default trust standard is simple: use as little browser-side storage as necessary to keep the site working, explain what that storage is for, and avoid inflating light technical behaviour into something it is not.
Basic site delivery may involve short-lived technical behaviours related to security, caching, load balancing, or abuse prevention. These functions can exist without turning the site into an advertising profile machine. Their role is to keep the site available, stable, and safer to operate. When such behaviours are present, they should be limited to what is reasonably necessary for site delivery and protection.
Examples can include temporary identifiers related to caching layers, bot protection, or request validation. These are not presented as personalised ergonomic features; they are part of normal static-site operation.
If the site uses privacy-conscious analytics, traffic measurement, or other basic performance tools, their purpose should be limited to understanding whether pages load, whether tools are used, and whether maintenance problems are occurring. The purpose should not drift into building a rich behavioural dossier unrelated to workstation guidance.
A visitor should be able to understand the difference between lightweight site measurement and broader ad-tech style tracking. This policy exists in part to keep that difference visible.
Some third-party resources, such as fonts, infrastructure services, or future analytics tools, may introduce their own technical requests or browser interactions. When they do, the site operator should review whether they are necessary, whether they fit the trust standard of the site, and whether they are worth the added complexity. A small ergonomic site should not casually accumulate third-party scripts that make its privacy posture harder to understand.
If a future change introduces a more meaningful third-party cookie or tracking relationship, this page should be updated in plain language rather than left vague.
Most browsers allow users to review, clear, or restrict cookies and related site data. Visitors who prefer a more restrictive browser posture can use those controls directly. Doing so may change how some technical site features behave, especially where caching or protection layers are involved, but the site should remain readable and broadly usable without forcing an intrusive relationship.
The point is not to corner the visitor into maximum tracking. The point is to keep the site transparent enough that the visitor can make an informed choice.
This cookie policy should be reviewed whenever the site changes its hosting layer, adds analytics, embeds more third-party resources, or begins using advertising-related scripts that materially affect the browser-side data posture. If the operating model becomes more complex, the explanation should become more specific. A good cookie policy should grow with reality, not trail behind it as a vague leftover from an earlier stage.
Questions about this policy or the site’s data posture can be directed through the public contact route listed on the contact page. The goal is a policy that helps users, reviewers, and advertising systems understand the site honestly, not a thin page that exists only to tick a box.
If the site later introduces advertising scripts, consent tooling, audience measurement changes, or other browser-side technologies that materially change the tracking or storage posture, this page should be revised to describe those changes in specific and reviewable language. A cookie policy should not stay frozen while the real technical posture shifts underneath it.
That matters particularly for trust and advertising review. A thin policy that lags behind reality is worse than a modest policy that remains accurate.
This cookie policy should be read alongside the privacy policy, not as a replacement for it. The privacy page explains the broader data posture of the site, while this page focuses more narrowly on browser-side technologies, technical storage, and related operational behaviour. Together they help describe how the site works without asking visitors to infer technical meaning from silence.
The purpose is clarity. Users, reviewers, and advertisers should be able to see what kind of site this is and what kind of tracking posture it is trying to avoid.
If the site’s browser-side behaviour changes materially in the future, this page should be expanded before the old explanation becomes misleading. That includes changes involving analytics, advertising scripts, consent interfaces, or third-party resources with more significant tracking implications. A reviewer should not have to discover that shift by accident.
The policy is meant to evolve with the site, not to remain a frozen shell from an earlier stage of the project.
