Mesh Participation Terms

These terms supplement the Terms of Service for people who connect a device to the Quantx mesh or submit work for supported network processing. "Node" means a participating device or computing instance. "Contribution" means making authorized computing resources available for eligible work. "Remote processing" means another node or provider processes information for your task.

1. Participation is an informed part of the service

The mesh is a core element of the Quantx model. Before a device contributes, we present a resource-use disclosure and require an affirmative enrollment action. The disclosure explains what participation does, when it runs, which resources it uses, and how to stop it. Simply browsing our website, entering a waiting list, or accepting unrelated marketing does not activate a node.

The general contractual authorization to contribute compute is separate from any permission required to access personal information, protected device resources, or third-party AI services. We request those permissions at the appropriate point. If you decline a permission essential to a particular mesh feature, that feature may be unavailable; unrelated optional permissions are not treated as mandatory.

2. You must control the device and network

Enroll only hardware and network connections you own or are authorized to administer. Obtain any employer, school, household administrator, or other required authorization. Your use must comply with applicable internet-provider, network, hardware, and platform rules. You may not enroll another person's device without authority or conceal participation from its owner.

3. Resources and operating conditions

Depending on supported hardware and the limits shown in the app, participation can use processor or accelerator capacity, memory, storage, network bandwidth, and electricity. It can affect battery life, temperature, fan noise, responsiveness, data usage, and component wear. Your electricity, connectivity, and hardware costs remain yours unless a separate offer expressly reimburses them.

The contribution limits and qualifying conditions for your device are set by Quantx based on device type, battery, charging state, network, and temperature, and shown in Settings. Background eligibility is determined by each operating system's background-task rules. Being plugged in does not guarantee that iOS, Android, macOS, or Windows permits continuous background operation. We do not authorize bypassing platform safeguards, thermal protection, power controls, or an administrator's restrictions.

Do not operate a device in an enclosure, covered location, or charging condition that conflicts with its manufacturer's safety instructions. If you observe abnormal heat, battery swelling, unusual noise, or another hazard, stop using it and follow the manufacturer's guidance. General risk disclosure does not excuse unsafe software design or waive mandatory product-liability rights.

4. Available controls and stopping participation

The actual controls are Settings, under Devices and Mesh, including pausing contribution, removing a device, and limiting contribution to charging and Wi-Fi. The interface must identify whether stopping means pausing new assignments, terminating active work, disconnecting a device, or disabling automatic restart. The handling of an active job is active work is stopped and its shard is reassigned to another device. Re-enrollment and restart behavior are contribution resumes only when you turn it back on.

You may disconnect a device or uninstall software. This stops future contribution from that installation, subject to an accurately disclosed and technically necessary shutdown interval. It does not promise erasure of completed outputs or lawfully retained account and security records. Any effect on service features, subscription benefits, or contribution-based access must be disclosed before enrollment; no undisclosed penalty applies merely for stopping for safety or exercising statutory rights.

5. What work a node can receive

Nodes receive only workloads within the enabled runtime and approved task classes described in the Quantx classification, extraction, and embedding task classes. Contribution does not authorize arbitrary remote control of your computer, use as a public proxy, access to unrelated files, cryptocurrency mining, or the sending of communications from your personal accounts. Additional features require separate scope and permissions.

We may validate a node's capabilities, software version, job completion, and integrity using the diagnostic information disclosed in the Privacy Policy. We may reject, quarantine, or disconnect a node that returns invalid results, fails security requirements, or behaves abusively. Validation is not a guarantee that every result is accurate or every node is trustworthy.

6. Your responsibilities when processing another person's work

Use received job information only to perform the authorized task. Do not inspect it for an unrelated purpose, attempt to identify a person, copy it outside the authorized runtime, build a dataset, train a model on it, sell it, disclose it, or retain it beyond the assigned retention rule. Do not attempt to reconstruct information from fragments, intermediate representations, embeddings, or metadata.

Keep the participating environment protected against unauthorized access and do not tamper with runtime controls, job accounting, deletion instructions, or updates required for security. Notify support@getquantx.com if you suspect exposure. These duties do not make an unrestricted community device a vetted enterprise processor or establish regulatory eligibility by themselves.

7. Sending your own work to other nodes

Remote execution can require disclosure of content or intermediate data to an executing device. The actual categories, operator visibility, processing locations, safeguards, and retention are described in the Privacy Policy and feature notice. Encryption in transit protects a connection; it does not necessarily hide information from the device performing computation.

Do not send confidential, personal, export-controlled, or specially regulated material to a route that has not been approved for it. The interface and contractual restrictions must identify permitted data classes. We will not describe data as anonymous merely because direct names are removed or a workload is divided. Required disclosure and permission remain necessary even if a peer operator is contractually forbidden to misuse information.

Where location-restricted, private-workspace, or local-only modes are offered, their boundaries are shown in the mode selector for each request. Failure to meet a boundary must not silently authorize a broader destination. Any retry, replica, or cloud fallback must stay within the scope disclosed and authorized for the task.

8. Security isolation and retention

The controls actually deployed for workload isolation, connection protection, access verification, temporary storage, and erasure are sandboxed task execution, TLS connections, per-device signing keys with result verification, and automatic deletion of temporary task data. We do not promise cryptographic confidential execution, hardware attestation, end-to-end secrecy from execution nodes, or verified erasure unless the applicable implementation has been established and accurately described.

Nodes must follow the temporary-data schedule deleted immediately after a task completes and in all cases within 24 hours. Quantx may send deletion or invalidation instructions and disconnect noncompliant nodes. We cannot reverse a malicious copy that has already escaped technical controls; our operational and contractual protections must be assessed against that risk before a route accepts personal data. This limitation does not waive our legal duties or remedies against misuse.

9. Availability and economics

Node counts, nominal accelerator operations, and aggregated memory do not establish usable capacity for every model or task. Network latency, bandwidth, model compatibility, availability, memory placement, and verification overhead affect performance. Participation does not guarantee faster answers, service without internet, pooled memory equivalent to a single accelerator, or continuous access.

There is no payment, cryptocurrency, ownership interest, investment return, or redemption right for contribution unless a separate written program expressly establishes it. Any future credits program will explain qualification, calculation, expiry, tax treatment, changes, and disputes before enrollment. Illustrative financial or environmental research does not create a payment or savings guarantee.

10. Updates incidents and termination

We may pause mesh operations, require a security update, revoke a credential, or change supported task classes for security, legal, or compatibility reasons. New material resource use or personal-data purposes require updated disclosures and permission where required. We may suspend unsafe or abusive nodes and provide the appeal process described in the Terms of Service where appropriate.

The Terms of Service govern liability and disputes, subject to mandatory rights. Report a node, privacy, or safety issue through support@getquantx.com, support@getquantx.com, or support@getquantx.com as appropriate. Your duty not to misuse received data continues after disconnection.