Contents
1. Scope and status
These V1 terms apply to Tessen Node and authorized local or distributed workloads only where separately released and made available. They supplement the applicable personal, developer or business agreement. They are not a release announcement, an employment offer or a promise of revenue.
Node is intended to provide local/private/distributed compute participation with user controls. The meaning and operation of each mode must be documented for the released version. A setting label is not, by itself, a data-security or residency guarantee.
2. Device authority and prerequisites
Install and run Node only on equipment and network resources you own or are authorized to use. Comply with organization rules, network agreements, device licenses and applicable law. Do not install Node covertly or enroll another person’s resources without informed permission.
You are responsible for selecting suitable hardware, maintaining your operating environment and protecting credentials. Node terms apply only to the separately released installer and supported environment identified in its release documentation. Installation requires authority over the device and a disclosure of its actual permissions, update and signature-verification process. Publication of these terms does not establish a supported operating system or availability of a public binary.
3. Local and private processing
Local execution can still require account services, downloads, telemetry or remote requests. Private mode must be defined by its actual workload and data-flow behavior. Do not assume that “private” means every record stays on-device or that no provider receives data.
Local, Private and Earn describe only the behavior disclosed and implemented for the installed release. Local execution can still involve remote account, update or telemetry services; the actual file/network permissions and isolation limits must be disclosed before activation. Product disclosures should make the relevant limits understandable before mode activation. Authorization for one task should not expand into unrestricted access to local content.
4. Distributed workloads and access boundaries
Distributed participation must be opt-in according to implemented controls. Workloads should execute only within the granted resource and permission scope. Participants must not inspect, retain, disclose or tamper with another user’s workload data beyond what authorized execution requires.
Do not bypass isolation, use workload access to probe other systems or repurpose data for model training or unrelated analysis. Task assignment is not authorization to contact an external recipient or access additional files. Any handling of personal data requires an appropriate legal role and contractual arrangement before deployment.
5. Resources, costs and operational risks
Node may use CPU, GPU, memory, storage, network bandwidth and electricity. Resource use can affect performance, heat, battery life and network costs. Review settings and use available pause/limit controls. Software errors or provider conditions may interrupt work.
The released product must explain actual limits and cancellation behavior. These terms do not guarantee a resource cap, zero hardware wear or uninterrupted operation. Tessen remains responsible for obligations it accepts, and users’ awareness of resource use is not a waiver of non-excludable rights.
6. Credits and participation incentives
Any incentive must be described by verified program rules before participation. Credits, if issued, are not automatically cash, securities, transferable property or a wage. Do not claim work that was not performed, manipulate execution receipts or exploit metering defects.
Participation compensation or incentives exist only under a separately approved program stating eligibility, verification, calculation, reversals, redemption, expiry and tax treatment. These terms do not offer an earnings rate or cash-out right. No earnings rate or cash-out promise is inserted. Where a program is linked to Project Zero, its preview limitations and capacity conditions also apply.
7. Privacy, confidentiality and customer processing
Account and operational information may be processed under the Privacy Notice. Workload content may be governed by a customer agreement and DPA. Participants’ roles and access to personal data must be assessed rather than presumed to be covered by an ordinary consumer account.
Distributed processing of customer workloads requires the applicable participant confidentiality and data-processing obligations and approved workload eligibility. Sensitive or regulated workloads are not admitted merely because a privacy setting is selected. Do not send regulated or sensitive customer workloads to an unverified participation pool. A privacy setting cannot substitute for the legal and technical controls the workload requires.
8. Updates, pausing and withdrawal
Use supported updates and do not disable security checks in ways that compromise workloads or other participants. Changes to Node behavior must be disclosed consistently with the underlying agreement. The released product must explain whether a pause stops new assignments, active tasks or both.
You may stop participation through the available controls. Completed external effects and records lawfully required for accounting or security may remain. The released Node product must expose its actual stop, uninstall and credential-revocation controls and explain active-work cancellation and local-data treatment. Stopping future work does not undo completed external effects.
9. Misuse, termination and liability
Tessen may suspend participation where resources are misrepresented, workloads are tampered with, security is at risk or law requires action. Provide notice and review where appropriate. Ending participation does not automatically terminate separately contracted services or authorize forfeiture of valid benefits contrary to agreed terms.
Warranty, liability and dispute provisions follow the applicable underlying agreement and mandatory law. Related documents are Project Zero, Developer Terms, Service Terms and Acceptable Use. Questions may be sent to hello@tessen.ai.