General Terms and Conditions (GTC)
These terms govern Jarvis Worker packages, related Discord-routed operator access, lifecycle and waitlist behavior, reward-credit mechanics, and sponsor-led Jarvis Unique alliance contracts.
Last updated: 25 May 2026
1. Service provider and contract route
The contracting service provider is the seller/operator identified in the Whop checkout, payment page, and invoice. If the checkout or invoice displays more specific legal entity, address, tax, VAT, or support details, those details control for the purchased package.
Jarvis support and operational communication take place primarily through Discord and the Jarvis support ticket page.
2. What the buyer purchases
The buyer purchases time-limited access to a Jarvis digital service lane and the related Discord-routed operator surface. Depending on package type, that may include setup handling, activation guidance, claim-code or claim-token handling, Discord reports, reward-wallet visibility, and automated operation according to the purchased scope.
Public Worker packages cover Farm, NPC, and Celebration operation. Builder, multi-account, Syndicate, launch-night, and alliance-level coverage are custom-managed and require a consultation-gated Jarvis Unique contract before pricing or scheduling is agreed.
3. Packages, period, and scope
- 8 Hour Trial: one fixed 8-hour Worker trial window with Great-tier cadence.
- Jarvis Small: weekly Worker access with an approximately 18-22 minute cadence.
- Jarvis Great: weekly Worker access with an approximately 5-8 minute cadence.
- Jarvis Unique: consultation-gated custom or alliance-scale scope, including packages such as Alliance Vanguard and Elite Striker Pack.
Package names, prices, VAT handling, period length, and checkout availability are shown on the public package page and/or in Whop checkout. Prices shown on the public page are net prices unless stated otherwise.
Public product copy, Whop plan labels, and invoice references may present the same package in shorter commercial language. The package shown in checkout or on the invoice controls the purchased scope.
4. Capacity tiers, overlays, and waitlist
Jarvis Worker capacity is managed through active service lanes. Public weekly capacity is commercially segmented into Founder, Pioneer, and standard weekly intake. Founder and Pioneer are pricing or waitlist-priority overlays, not separate execution engines.
- Founder: discount and priority rights only; the Founder customer does not reserve an inactive lane between paid periods.
- Pioneer: discount and priority rights only; Pioneer pricing survives only while continuity remains unbroken.
- Standard weekly: weekly intake may remain open after Founder and Pioneer pricing rights are exhausted if lane capacity still exists.
A waitlist opens when the active public lane pool is full. Jarvis may use ranked waitlist offers, reserved promotion windows, and offer expiry handling instead of immediate first-come admission when capacity reopens.
5. Jarvis Unique alliance contracts
Jarvis Unique contracts are sponsor-led arrangements funded through one billing anchor and distributed internally by the sponsor through claim codes or claim tokens. These contracts do not follow the normal public self-serve weekly lane funnel and may be gated by consultation, inventory readiness, operator approval, or explicit availability controls.
Alliance Vanguard currently refers to a mixed-core package built from 20 Jarvis Small base entitlements and 8 Jarvis Great bonus entitlements for the first 14 days. Elite Striker Pack currently refers to a 20 Jarvis Great base layer for 14 days plus an 8 Jarvis Great introductory bonus layer for 28 days. Public copy may summarize these packages, but the invoice, contract, or operator confirmation controls the exact contract scope.
Claim codes or claim tokens are access instruments, not money. They may expire, become unusable after claim, be revoked for fraud, security, scope mismatch, or duplicate issuance, or be replaced through an auditable support process. The sponsor is responsible for internal distribution and for protecting alliance-distributed claim codes before redemption.
Continuous Elite Striker renewals may extend the base 20 Great entitlements and may add sponsor reward-wallet promo credits instead of repeatedly issuing raw bonus bundles. Promo credits are subject to hard-cap and expiry rules set by the active contract or public policy, currently including a 24.0 active-credit cap and a 60-day expiry window for renewal-generated promo credits unless the applicable contract states otherwise.
6. Automatic start after checkout or contract activation
By ordering a Jarvis package or accepting a Jarvis Unique contract activation flow, the buyer expressly requests immediate performance. The related digital service lane, Discord route, claim-inventory issue flow, or operator setup work may start automatically after checkout or contract confirmation, before the end of any statutory withdrawal period.
Activation still depends on customer-provided setup details, Discord availability, and the customer inviting the assigned Jarvis lobby account to the relevant game account where that access model applies. Delays caused by missing or incorrect customer information, missing sponsor distribution, or missing alliance-side coordination do not pause the purchased access period unless Jarvis explicitly agrees otherwise in writing.
7. Withdrawal acknowledgement
Because the buyer requests immediate start, the buyer acknowledges that the 14-day withdrawal right is lost to the extent permitted by applicable consumer law once the digital service has begun and, for fixed short access periods or immediately claimable contract inventory, once the purchased period or claimable digital inventory has been fully or materially performed.
If mandatory consumer law requires proportional treatment before full performance of a longer service period, the buyer must pay for the setup, operator handling, claim-inventory issue, Discord access, and digital service already provided up to the withdrawal or termination time.
Checkout should request this immediate-start and withdrawal acknowledgement with an explicit checkbox or equivalent required confirmation before payment.
8. Customer and sponsor obligations
The customer must provide accurate setup details, including server URL, account name, Discord user ID, and any other checkout or support information needed for the selected scope. The customer must join the Jarvis Discord and invite the assigned Jarvis lobby account where required for operation.
For Unique alliance contracts, the sponsor must also provide accurate sponsor and contract context, distribute claim inventory responsibly, and avoid sharing claim codes publicly or outside the intended alliance scope.
Jarvis may pause, delay, refuse, revoke, or re-scope operation if the target account, server, Discord route, claim flow, lobby invitation, payment state, or package scope cannot be verified.
9. Renewals, continuity, and lifecycle labels
Renewal, recurring billing, scheduled cancellation, payment-method handling, and membership state are governed first by the Whop checkout or invoice route and then by Jarvis lifecycle policy. Customer-facing labels such as Auto-renew on, Auto-renew off, Cancels at period end, Founder locked, Pioneer continuity active, or Standard return after lapse describe the current service state but do not create rights beyond the underlying paid entitlement.
Founder pricing may survive lapse as a customer-level commercial right. Pioneer pricing may be lost after any meaningful continuity break. For waitlisted customers, Jarvis may issue time-limited promotion offers; those offers can expire if not acknowledged, used, or completed in time.
Continuous Unique-contract renewal is determined by the contract and provider lifecycle state, not by guesswork. Short provider or webhook jitter does not automatically break continuity if the paid contract state remains materially uninterrupted.
10. Reward credits, promo wallet balance, and claimable value
Jarvis may issue non-cash reward credits, including referral credits or alliance-promo wallet credits. These credits are redeemable only according to active Jarvis commercial rules. They are not withdrawable cash, do not earn interest, and cannot be exchanged for money unless mandatory law requires otherwise.
Referral rewards may depend on qualifying weekly subscriptions, redemption rules, and continuity requirements shown in the customer portal or support flow. Alliance-promo credits may be subject to per-wallet hard caps, expiry windows, contract-cycle restrictions, and void rules when the cap would otherwise be exceeded. Jarvis may record attempted, applied, and voided promo deposits for audit and support handling.
Reward credits, promo-wallet balances, claim codes, and claim tokens remain part of the purchased service system and may be expired, refused, revoked, or corrected if they were created through duplicate processing, abuse, fraud, pricing error, or scope mismatch.
11. Operational boundaries and risk
Jarvis is an operator and automation service. It does not guarantee game results, resource output, ranking, uninterrupted operation, account safety, ban immunity, bypass of platform enforcement, or availability of third-party services.
The customer remains responsible for the game account, third-party platform rules, customer decisions, account access, alliance context, and any consequences of using automation or operator assistance.
12. Payment, VAT, invoices, and renewal amounts
Payments are handled through Whop or the payment route shown at checkout. VAT, sales tax, or similar taxes may be added according to the invoicing location and payment provider logic. The invoice and checkout page control the final payable amount.
Any renewal, recurring billing, cancellation, or payment-method management follows the Whop checkout and membership settings shown to the buyer unless a Unique contract, operator confirmation, or invoice explicitly states otherwise.
Unique-contract renewal amounts, including current Elite Striker renewal pricing such as 960 EUR per continuous renewal cycle where offered, are controlled by the issued contract or invoice rather than by generalized public copy.
13. Service availability, platform changes, and remedy
Jarvis depends on third-party environments, including browser-game pages and flows, Discord, Whop, payment providers, network providers, browser/session providers, and the customer's account access state. Third-party maintenance, layout changes, anti-abuse challenges, lobby changes, account restrictions, rate limits, server lag, or rule changes may temporarily block or reduce automated operation.
When a third-party platform change or outage materially affects operation, Jarvis may pause affected actions, investigate, patch selectors or flows, adjust cadence, restart sessions, or move the case to operator review. The buyer agrees that reasonable remediation time is part of the service model. For public Worker packages, a remediation window of up to 24 hours after Jarvis becomes aware of a material platform change is normally treated as reasonable.
The primary automated commercial remedy for a confirmed Sentinel-side outage is time credit, not an automatic cash refund. The canonical Jarvis remedy formula is currently: added service time = confirmed outage duration × 2. Remedy normally applies to Sentinel-side outages and does not automatically apply to official game outages, third-party maintenance, or upstream platform incidents unless Jarvis explicitly classifies the effective impact as Sentinel-owned.
The purchased service is not a promise of a fixed number of clicks, farm list launches, NPC trades, celebrations, resource gain, ranking movement, or uninterrupted uptime. The purchased service is time-limited Discord operator access and the related Jarvis operation lane, subject to the guardrails, third-party availability, and customer setup requirements in these terms.
14. Refunds, extensions, and service credits
Unless mandatory law, Whop rules, payment network rules, or a written Jarvis Unique agreement require otherwise, the primary remedy for a confirmed Jarvis-side service interruption is remediation, continued access, a service-time extension, or a credit toward a future Jarvis period, not an immediate cash refund.
For 8 Hour Trial access, if Jarvis cannot provide a meaningful trial window because of a confirmed Jarvis-side blocker, Jarvis may re-run or extend the trial window before considering a cash refund. For paid Worker or Unique service periods, Jarvis may prefer remediation, replay, extension, or the 2x Remedy time-credit model over an immediate refund whenever that path can restore meaningful service.
Refunds are not owed for customer-side blockers, including incorrect checkout details, failure to join Discord, failure to invite or keep the assigned lobby account, failure to protect or properly distribute claim codes, removing access, changing account state without notice, platform bans/restrictions, customer account loss, chargeback abuse, or requests outside the purchased scope.
Cash refunds are reserved for duplicate charges, clearly wrong package billing, cases where Jarvis cannot provision any purchased Discord/operator access and cannot remedy it within a reasonable time, or situations where applicable law, Whop, a payment provider, or a card network requires a refund.
The standalone Refund Policy is part of these GTC and should be read together with this section.
15. Support-first dispute process
If the buyer believes the purchased service is not being provided, the buyer should submit a Jarvis support ticket or use the Whop Resolution Center before opening a bank dispute where reasonably possible. This does not limit mandatory consumer rights, but it gives Jarvis a fair chance to verify the account, restore service, extend time, issue credit, or correct billing.
Jarvis may keep and submit dispute evidence, including checkout fields, immediate-start acknowledgement, GTC/Refund Policy acceptance evidence, Discord channel creation records, access activity, action reports, support tickets, remediation notes, and customer communications.
16. Support, reports, notices, and tickets
Jarvis reports performed, skipped, and blocked actions through Discord where configured. Support tickets can be submitted through the public support page. Jarvis may also send lifecycle notices such as expiry reminders, renewal-state reminders, waitlist promotion offers, claim-code readiness notices, contract-created notices, sponsor bonus notices, or remedy notices through Discord or another configured customer channel.
Jarvis may use ticket and Discord context to identify the relevant customer, sponsor, server, package, contract, claim flow, run, and operator action.
17. Third-party platforms
Jarvis relies on third-party platforms such as Whop, Discord, payment providers, network providers, and browser-game-related services. Jarvis is not responsible for outages, rule changes, account actions, payment holds, API changes, or access restrictions caused by those platforms.
18. Changes and contact
Jarvis may update these terms when packages, checkout, Discord handling, or service scope changes, including updates to capacity overlays, waitlist policy, Unique alliance packages, claim-code handling, reward-credit logic, or remedy policy. Material changes do not shorten paid access already purchased unless required by law, a payment provider, or a third-party platform. For questions, submit a ticket or use the contact route shown in checkout, Discord, or on the invoice.