gofundnode legal

GoFundNode — Customer (Tenant) Terms of Service

Superseded by ADR-046 (2026-06-03). This document reflects the prior crypto-first posture, which is no longer GA scope. See ADR-046.

TEMPLATE — REQUIRES RETAINED COUNSEL REVIEW BEFORE PRODUCTION USE. NOT LEGAL ADVICE.

Effective date: TBD upon counsel sign-off and execution.
Document owner: JuiceVendor Labs inc. (operating the GoFundNode service) (the "Platform", "we", "us").
Counterparty: the tenant entity using the v1 vendor API (the "Customer", "Tenant", "you").
Source-of-truth: docs/CREDIT-SYSTEM.md (pricing), docs/V1-API.md (API surface), CLAUDE.md (architecture), docs/legal/terms/DPA_TEMPLATE.md (data processing), docs/architecture/GOFUNDNODE_ADRS.md (architectural decisions).

1. Acceptance and capacity

1.1 By integrating against the GoFundNode v1 vendor API, configuring tenant credentials, or otherwise using the services described herein, the Customer accepts these Terms.

1.2 The individual accepting these Terms represents that they have legal authority to bind the Customer entity.

1.3 B2B-only. These Terms govern a business-to-business relationship between two commercial entities. They do not apply to consumers, individuals, or non-business users. The Platform does not provide a consumer-facing product. See ADR-041 (D-6) for the architectural basis of this allocation.

1.4 The Customer represents and warrants that the Customer is not located in, organized under the laws of, or owned/controlled by a person in a jurisdiction subject to OFAC comprehensive sanctions (Cuba, Iran, DPRK, Syria, Crimea / so-called DNR / so-called LNR, and any successor list maintained by OFAC), and that the Customer is not on the OFAC Specially Designated Nationals (SDN) list. The Customer agrees to immediately notify the Platform if any of these representations becomes untrue.

2. Description of services

2.1 The Platform is a typed-task residential execution platform. The Customer submits typed tasks (e.g., ats.application) through the v1 vendor API; the Platform schedules those tasks onto opt-in residential operator devices; results are returned via webhook and via the polling endpoints described in docs/V1-API.md.

2.2 The Platform does not provide:

2.3 The launch task type is ats.application. Future task types are made available via the manifest registry and require separate Customer onboarding per task type.

3. Credits and billing

3.1 Credit unit. The Platform's internal accounting unit is the credit. Pricing, the canonical pricing function, and rate cards are defined in docs/CREDIT-SYSTEM.md. Credits are denominated against an internal USD-equivalent value (currently $0.005 per credit) for accounting purposes only; credits are not currency, not a stored-value instrument, and not a security.

3.2 Non-transferable, consumptive prepaid units. Credits are non-transferable, consumed at task execution, prepaid, and have no cash value in the hands of the Customer except by way of the refund mechanics in §4. Credits cannot be assigned, pledged, gifted, sold, or otherwise transferred to a third party. See ADR-044 (D-9) for the architectural basis: credits are not securities or investment contracts under the Howey test.

3.3 Pre-quoted holds. Each submission is pre-quoted with estimated_credits and a hard max_credits hold against the Customer's pre-authorized credit block (see ADR-027). Actual consumption is reconciled at settlement; the unused remainder is refunded to the Customer's aggregate balance.

3.4 Solana mainnet rail. Credit purchases settle in USDC or SOL on Solana mainnet via Solana Pay. The Platform does not operate a fiat billing rail. See docs/SOLANA-PAY.md and docs/ADR/no-stripe.md.

3.5 Optional gift-card rail (conditional). The Platform may, in its discretion and only upon execution of a separate signed agreement with a regulated gift-card provider (ADR-045 / D-10), make available a consumer-side gift-card purchase rail in which a regulated provider acts as the issuer and money-services-business (MSB) bearer. Until such an agreement is signed and announced, the provisions of this §3.5 are inert and no such rail is available.

4. Refundability and credit expiry

4.1 Unconsumed credits are refundable to the original funding wallet, subject to (a) the technical limits of the Solana blockchain (refunds are net of network fees), (b) a 30-day refund-request window from purchase, and (c) verification that the requesting wallet is in fact the original purchaser. Refund processing is documented in docs/OPERATOR-PAYOUTS.md (operator payouts) and in the agent U / refund module.

4.2 Consumed credits are non-refundable. Once a task lease has reached its commit point as defined by the task type manifest (e.g., for ats.application, the moment the submit-button click POSTs to the ATS server per ADR-032), the side effect is irreversible and the consumed credits cannot be refunded. The Customer's recourse for service issues is the dispute path in §10.

4.3 No cash refund on crypto rail. Because the funding rail is irreversible on-chain settlement, there is no chargeback mechanism analogous to credit card disputes. Refunds, where due, are processed as USDC transfers back to the originating wallet, not as fiat reversals. The Customer acknowledges and accepts this asymmetry.

4.4 Credit-block expiry. Pre-authorized credit blocks expire per ADR-027. Residual (allocated − consumed) is refunded to the Customer's aggregate balance upon expiry by the reaper.

4.5 Aggregate balance dormancy. Customer aggregate balances follow docs/legal/terms/DORMANCY_POLICY.md: first notice at 12 months of inactivity, second at 15, final at 18; escheatment thereafter per the Customer's jurisdiction of organization. No silent forfeiture — see ADR-045 and §14.1 architectural basis.

5. Service levels and remedies

5.1 Stated QOS targets. The Platform targets the QOS levels defined in HANDOFF-NOTES.md §7: p95 dispatch-to-fill ≤ 4 minutes for personal-node tier; ≤ 20 minutes for community tier; ≥ 95% successful fill rate on Ashby (baseline at launch).

5.2 Capacity admission. When the Platform's admission ceiling is breached, the Platform returns at_capacity per the /v1/capacity semantics in docs/coordination/APPLYFUN_CTO_NOTES.md §C-NEW-2. Submission of a task during at_capacity is not a Platform service issue; the Customer is expected to consume the capacity signal and route easy/overflow jobs to its own fallback.

5.3 SLA remedies are service-credit-based. For documented missed SLA on a successfully dispatched task, the Customer's exclusive remedy is a service credit rebate against the actualCredits charged for the affected submission, calculated per the rebate matrix in §10.

5.4 Service-credit-only. The Customer acknowledges that the irreversibility of the Solana funding rail (§4.3) means that monetary refunds are not the remedy for service issues. The remedy is rebate against future submissions or as a USDC return to the Customer wallet if the Customer terminates per §11.

5.5 No consequential damages. The Platform's aggregate liability under these Terms is capped at the credits the Customer paid in to the Platform during the 12 months preceding the claim, save where caps are not enforceable by applicable law.

6. Prohibited use

6.1 The Customer shall not:

6.2 The Platform reserves the right to suspend or terminate Customer access on reasonable belief of breach of §6.1, with notice where feasible.

7. Prohibited jurisdictions

7.1 The Customer represents that the Customer is not organized under the laws of, principally located in, or operationally controlled from any of the following jurisdictions (the "Prohibited Jurisdictions"):

7.2 The Customer further represents that no person owning more than 25% of the Customer entity is on the OFAC SDN list or is a national of a Prohibited Jurisdiction.

7.3 The Platform may freeze the Customer's account and credit balance pending OFAC review if a sanctions hit is identified. Resolution is per docs/legal/terms/DORMANCY_POLICY.md and ADR-038.

8. Tax

8.1 Customer remits its own tax. The Customer is responsible for VAT, GST, sales tax, or analogous indirect tax in the Customer's jurisdiction.

8.2 EU VAT. Where the Customer is established in the European Union, the Platform applies B2B reverse-charge or EU OSS VAT mechanics as applicable. The Customer must provide a valid VAT number on request.

8.3 The Platform's prices are exclusive of any tax payable by the Customer.

9. Data, privacy, and confidentiality

9.1 Apply.fun applicant PII is processor data. Where the Customer is apply.fun and the Customer transmits applicant PII for the purpose of task execution, the parties' relationship for that data is Customer-controller / Platform-processor. The Data Processing Agreement at docs/legal/terms/DPA_TEMPLATE.md applies and is incorporated by reference. The allocation of applicant consent to the Customer is documented at ADR-042 (D-7).

9.2 Customer account data is controller data. The Platform processes the Customer's tenant account contacts and billing data as controller, per docs/legal/terms/PRIVACY_POLICY.md.

9.3 Confidentiality. Each party shall keep confidential the other's non-public business and technical information disclosed under these Terms. The HMAC and webhook secrets shared per docs/TENANT-ONBOARDING.md §1 are confidential.

9.4 No tenant-side PII handling outside the DPA. The Customer agrees not to use applicant PII received from the Platform for any purpose other than as instructed by the controller and as documented in the DPA.

10. Dispute resolution

10.1 Premise. The funding rail is on-chain and irreversible; dispute resolution is therefore service-credit-based, not refund-based, except where unconsumed credits are returned per §4. See docs/legal/terms/DISPUTE_PATH.md for the full workflow. Architectural basis: §14.7 of the Legal Handoff.

10.2 Levels.

10.3 Class waiver (jurisdiction-permitting). To the extent permitted by applicable law, claims may be brought only in the parties' individual capacities, not as a plaintiff or class member in any purported class or representative action.

10.4 No exclusion of equitable relief. Either party may seek injunctive relief in a court of competent jurisdiction to protect intellectual property, confidential information, or against ongoing unauthorized use.

11. Term and termination

11.1 These Terms commence on the Customer's first use of the API and continue until terminated.

11.2 Either party may terminate for material breach not cured within thirty (30) days of written notice.

11.3 The Platform may terminate immediately for sanctions-list determination (per §7) or for breach of §6.

11.4 Upon termination:

12. Miscellaneous

12.1 Entire agreement. These Terms, the DPA, the Privacy Policy, and the documents incorporated by reference constitute the entire agreement between the parties on the subject matter.

12.2 Amendment. Material amendments to these Terms require 30 days' notice to the Customer's primary contact on file.

12.3 Assignment. Neither party may assign these Terms without the other's consent, save assignment to an affiliate or in connection with a corporate reorganization, in which case the assigning party shall provide notice.

12.4 No waiver. No failure by either party to enforce a provision waives that provision.

12.5 Severability. If a provision is held unenforceable, the remainder shall remain in effect.

12.6 Governing law. These Terms are governed by the laws of Estonia, excluding conflict-of-law principles.

12.7 Notices. Notices to the Platform: notices@gofundnode.com (or a successor address published in the API documentation). Notices to the Customer: the primary contact on file at tenants.contact_email.

13. References

END — TEMPLATE — REQUIRES RETAINED COUNSEL REVIEW BEFORE PRODUCTION USE. NOT LEGAL ADVICE.