Jarvis
  • Packages
  • Activation
  • Technical details
  • Submit a ticket
  • GTC
  • Cookie Policy
Start Jarvis
Jarvis legal

Refund Policy

This policy explains how Jarvis handles platform changes, service interruptions, remedy credits, refunds, and payment disputes for Jarvis Worker packages and Unique alliance contracts.

Last updated: 25 May 2026

Principle Platform changes Remedies No refund cases Cash refunds Disputes

Refund principle

The buyer purchases time-limited access to a Jarvis digital operation lane and related support or Discord-routed operator surface. The service is not sold as guaranteed game progress, guaranteed uptime, or a fixed number of actions. Once access starts, the primary remedy for a service issue is remediation, service-time extension, or non-cash credit unless mandatory law or payment-platform rules require a cash refund.

Platform changes and outages

browser-game-related pages, Discord, Whop, payment providers, network providers, and browser/session providers are third-party systems. A third-party layout change, rule change, maintenance window, access restriction, server lag, anti-abuse challenge, or outage may temporarily stop or reduce Jarvis operation.

If a third-party platform change materially affects Jarvis, the service may pause while operators investigate and adapt the affected flow. A remediation window of up to 24 hours after Jarvis becomes aware of a material platform change is normally treated as reasonable for public Worker packages.

Extensions and credits first

For an 8 Hour Trial, if a confirmed Jarvis-side blocker prevents a meaningful trial, Jarvis may re-run or extend the trial window before considering a cash refund.

For paid Worker or Unique service periods, the primary automatic commercial remedy for a confirmed Sentinel-side outage is currently the Jarvis 2x Remedy formula: added service time equals confirmed outage duration multiplied by two.

Remedy normally applies to Sentinel-side outages. Official game outages, third-party maintenance, or upstream platform incidents are not automatically remedy-eligible unless Jarvis explicitly classifies the effective impact as Sentinel-owned.

No refund cases

Refunds are not owed for customer-side blockers: incorrect checkout details, missing Discord membership, missing or revoked lobby invitation, removed account access, changed customer account state, careless or unauthorized claim-code distribution, customer platform bans/restrictions, third-party account loss, or requests outside the purchased package scope.

When cash refunds may apply

Cash refunds may apply 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.

Support before chargeback

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 remove mandatory consumer rights, but it lets Jarvis verify the issue, restore operation, extend access, issue credit, or correct billing before a chargeback escalates.

Jarvis may submit checkout, access, Discord, action report, support ticket, policy acceptance, and remediation records as dispute evidence.

Jarvis Ops Platform Refund Policy ยท Service availability
GTC Refund Policy Cookie Policy Support