Ergo Workspace

Privacy Policy

What this site collects, avoids, and how it handles limited technical data.

Privacy expectations

Ergo Workspace does not depend on accounts or aggressive data collection to work. The core tools operate on small, visible inputs related to symptoms, setup type, and constraints. The privacy posture is intentionally narrow because the site is focused on guiding workstation decisions, not on building a user profile or extracting unrelated personal data. From a trust and advertising-review standpoint, that means the site should avoid collecting more than it needs, explain what it does collect in plain language, and keep the contact and policy pages legible enough that a normal visitor can understand the operating posture without guesswork.

This page exists so the user can understand those expectations clearly rather than infer them from silence. Transparency here matters both for trust and for review quality.

Information this site is designed to avoid collecting

Ergo Workspace is built to avoid unnecessary collection as much as possible. The core tools do not require user accounts, social profiles, or expanded personal dossiers. In normal use, the site is meant to work with small contextual inputs about the workstation problem itself rather than broader personal identity data.

This matters because a focused workstation site should not quietly turn into a profile-building machine. The privacy standard here is restraint first, not retroactive explanation later.

Operational privacy expectations

Like most websites, the site may process limited technical information needed for hosting, security, performance, and basic traffic understanding. That does not change the core promise of the product: the site is maintained to support ergonomic decisions, not to extract unrelated personal value from visitors.

If this posture changes in the future, the policy should be updated in plain language rather than hidden behind silent expansion.

Policy maintenance and updates

This policy should be reviewed whenever the site changes how it handles forms, analytics, embedded services, or any other visitor-facing behavior that could affect privacy expectations. A narrow site should keep a narrow policy, and if the operating model expands, the written explanation should expand with it in plain language.

The point of a privacy policy is not just formal compliance. It is to make the site’s operating posture legible enough that a normal visitor can understand what kind of relationship they are entering.

What information can appear in normal use

In normal use, the site’s visible tools work from short, user-provided inputs such as symptom pattern, setup type, budget band, work duration, body height, desk height, or screen size. Those values are part of the product interaction itself rather than broad identity profiling. The intention is to keep the site’s logic tied to workstation decisions, not to unrelated personal data collection.

If future versions introduce any form submission, newsletter sign-up, or other direct communication layer, the purpose of that collection should be explained clearly at the point of collection rather than hidden inside vague legal language.

Data minimisation and retention posture

The privacy posture of Ergo Workspace is based on minimisation. A focused ergonomic decision site should not collect more than it needs to operate, maintain, secure, and improve the product. Where limited technical logs, infrastructure records, or abuse-prevention signals exist, they should be retained only for operational, security, or diagnostic reasons and not treated as a reason to expand tracking scope without explanation.

Retention periods may vary depending on hosting, security, analytics, or logging infrastructure, but the governing principle remains the same: keep only what supports legitimate operation and review, then avoid silent expansion.

Lawful purpose and transparency

The site is maintained as an informational workstation review product. Any limited processing related to hosting, analytics, security, caching, or contact handling should stay consistent with that purpose. This page is meant to make those purposes legible enough that a normal visitor can understand the operating posture without needing to decode generic legal jargon or infer site behaviour from silence.

That transparency standard matters for users, reviewers, and advertising systems alike. A privacy page should explain the site as it actually operates, not as a vague abstract service.

Contact, policy updates, and user questions

Questions about this privacy policy or the site’s data posture can be sent through the public contact route listed on the contact page, including the site email address currently provided there. If the site changes how it handles analytics, direct messages, forms, embedded services, cookies, or other visitor-facing behaviour, this page should be updated in plain language so that the privacy explanation stays aligned with reality.

A useful privacy page is not only a compliance gesture. It is part of the site’s trust model, and it should be maintained with the same care as the tools and content routes.

Hosting, infrastructure, and security layers

The site may rely on normal infrastructure services such as hosting providers, caching layers, traffic filtering, DNS services, or abuse-prevention tools. These services can process technical request data, such as IP-related information, browser request headers, timestamps, or security signals, for the purpose of safe and stable delivery. Those functions are part of ordinary site operation rather than hidden expansion into unrelated personal profiling.

Where such layers are used, the operator should still keep the overall data posture proportionate. A narrow ergonomic site should not quietly accumulate a broad surveillance footprint just because technical services make that possible.

Accuracy, restraint, and future changes

A privacy policy should remain aligned with the real site. If new features are introduced—such as forms, analytics changes, embedded media, account features, newsletters, or advertising scripts—the privacy explanation should be updated before or alongside those changes rather than after complaints appear. The site’s trust standard depends on the written policy keeping pace with reality.

That is especially important for a maintained informational product. Reviewers should be able to see that privacy language is being treated as part of site maintenance, not as decorative legal filler that no longer matches the operating model.

Practical reading guide for this policy

A normal visitor should be able to read this policy and understand four things: what the site is trying not to collect, what limited technical behaviour may still exist for delivery and security, where questions can be sent, and when the page should be updated. If any of those points become hard to identify, the policy is no longer doing its job clearly enough.

That is a useful standard for review. A privacy page should not require a privacy lawyer just to understand the broad posture of a small ergonomic site.