Helpwo product terms

Scope and common rules

This annex applies to the relevant Helpwo functions together with the Platform Terms, Privacy Policy, Data Use Notice and Billing and Refund Policy. It supplements or overrides general terms only on its stated product matters. Mandatory law and valid individually negotiated agreements take priority. The version expressly provided and validly accepted at purchase or use applies; a web update does not automatically change existing orders.

Runtime modes and data locations

Browser databases, desktop workspaces, machines connected by Kernel or CLI and selected cloud storage are different locations. Default local browser storage does not make AI, search, remote tools or sync local. Files, command output, context or runtime views may be transmitted to the gateway, peers, models and authorised contractors. Peer connections may require relaying; relay architecture is not a guarantee that every component is unable to read content.

Files, terminals and execution authority

Choose workspaces, machines and accounts you may manage and review read, write, execution, network and publication permissions. A task instruction, one tool approval, run-scoped approval and standing authority have different scopes. Revoke access, disconnect the runtime or stop the task to end subsequent actions. Commands, uploads, deletion, installs and external transactions already issued may be irreversible; disconnection does not prove a remote process stopped. File controls and approvals do not replace OS isolation or backups, without removing Laintas’s own security duties.

Plugins, Skills, MCP and connections

Extensions and connections may contain third-party code, tools and independent processors. Review source, permissions and licences before enabling them. Review, signatures and hashes establish their particular checks, not a guarantee of safe behaviour or suitability. Third-party charges follow their agreements. Permission for one extension does not authorise every extension. Uninstalling, disconnecting and revoking external credentials may require separate actions.

Multiple agents and Issues contractors

Collaboration may start concurrent model and tool calls, each metered and subject to authority. Hiring through Issues exposes selected context and tool capabilities to the chosen contractor and invokes the Issues confidentiality, deliverable, acceptance and fee rules. Select the shared material carefully. Selection does not confer unlimited access; scope, prohibited paths and approvals still apply.

Storage, experience, backup and exit

GitHub or Laintas Storage creates separate cloud copies. Workspace experience may be held by the gateway for continuity within the account and is distinct from training. A CLI training opt-in does not automatically opt Helpwo calls in. Manage experience and cloud content as described in the Data Use Notice. Over-capacity or expired access may restrict new writes. Stopping or uninstalling neither deletes every local, cloud or third-party copy nor cancels membership renewal.

Approvals, automatic execution and revocation

For each connection check readable paths, writes, terminal, network and external accounts. Approving a command, directory or task does not become permanent authority over every machine and future task. Broad or automatic modes reduce prompts and accelerate permitted operations; users and organisations should choose appropriate limits. Revocation, disconnection and agent stop ordinarily affect future actions; running programs, writes and external sends may need separate termination or recovery. Actual permission checks, rather than prompt promises alone, must enforce supported restrictions.

Pages, project files and prompt injection

Pages, READMEs, dependencies, image text, external messages and tool results can contain instructions seeking to redirect work, obtain secrets or enlarge authority. Asking an agent to analyse them does not approve their execution. Check targets and scope before uploading logs, pasting commands, installing dependencies or opening links; dedicated credential settings are distinct from ordinary context. Contractors and plugins must not use embedded instructions to bypass host approval, organisation policy or explicit refusals. Stop work, revoke connections and preserve necessary evidence when anomalies occur.

Connected machines, running processes and backups

You must be entitled to connect the machine and project and must not disclose connection credentials to unauthorised people. Kernels, desktop hosts and terminals can perform real system operations affected by directory, branch, permissions and network state. Ending chat or closing a workspace does not guarantee every process, port, rental or sync has stopped. Check their state and funding separately. Production data, migrations and irreversible changes need proportionate backup or recovery arrangements, without waiving Laintas’s own permission, security and delivery duties.

Collaboration participants and context disclosure

Multiple agents, remote peers and human contractors can receive the context actually supplied, possibly through different models and connections. Share necessary excerpts and tool results, distinguishing same-account automation from independent contractors. Before selection, define goals, authority, budget and deliverable use. Do not send confidential work through ordinary public questions. Administrator visibility and review depend on deployment; complete recordings, stepwise undo and legal privilege are not promised for all collaboration.