TERMS OF USE

Local compute guidelines.

Last updated: June 2, 2026. These terms govern how the Hellomens OS runs agents and compute on your hardware.

1. Acceptance of terms

By installing or running Hellomens on local hardware you accept these guidelines. If you operate Hellomens on behalf of an organisation, you confirm you have authority to bind that organisation to these terms.

2. Local compute principles

Hellomens is designed local-first. Agent execution, indexing, and memory persistence default to your device. Three principles govern this model:

  • Residency. Your operational data and knowledge graph remain on local storage unless you explicitly enable a remote engine.
  • Boundedness. Each agent runs inside a declared context window and resource budget. The system will not exceed the compute ceiling you configure.
  • Transparency. Every agent invocation is logged locally so you can audit what ran, when, and against which model.

3. Acceptable resource use

You are responsible for the hardware Hellomens runs on. You agree not to configure agent loops that knowingly damage your device, exhaust shared infrastructure you are not authorised to use, or circumvent the resource ceilings the OS enforces.

4. Remote engines & model providers

When you opt into a remote engine (for example, a hosted model API), data required to fulfil that request leaves your device under that provider's terms. Hellomens surfaces the engine binding before execution. Disabling remote engines keeps the system fully local.

5. Acceptable use of agents

You agree not to deploy Hellomens agents to generate unlawful content, target systems without authorisation, or evade safety controls. Bounded autonomy is a feature, not a loophole.

6. No warranty

Hellomens Build 0.1 is provided "as is" during early access. We make no warranty that agent output is accurate, complete, or fit for any particular purpose. You remain responsible for reviewing agent actions before relying on them.

7. Limitation of liability

To the fullest extent permitted by law, Hellomens is not liable for indirect, incidental, or consequential damages arising from local compute execution, including data loss caused by misconfigured agent loops.

8. Changes to these terms

We may update these guidelines as the local compute model evolves. Material changes will be announced in-product and dated at the top of this page. Continued use after an update constitutes acceptance.