[ RETURN TO HUB ]

REFUND // PROTOCOLS

LAST REVISION: JUNE 2026

Due to the irreversible nature of cryptographic key exchanges and digital microtransactions on the Evantics network, our refund policies are strictly enforced. Please read the following protocols carefully before initiating any breach sequences.

1. TRANSACTION FINALITY

All transactions, including entry fees, token purchases, and node breach costs, are considered final upon execution. Once you attempt a breach sequence on a premium node, the system allocates server resources and locks in your attempt. We do not offer refunds for failed decryption attempts. If you hit the Architect's Crack Limit and are locked out, your entry fee is forfeited.

2. NODE DEPLETION

Many nodes on the Evantics Hub utilize a Global Claim Limit. It is entirely possible for a node to become "DEPLETED" while you are actively attempting to decrypt it. If another Observer extracts the payload before you complete the final stage, the node will lock. We do not provide refunds for lost races. Speed is a requirement of the system.

3. ARCHITECT PAYOUTS

Evantics operates on a split-payment routing system. When an Observer pays to breach a node, the majority of those funds are routed directly to the Architect's connected payout account. Because Evantics does not hold these funds, we cannot forcibly claw back money for completed transactions.

4. EXCEPTIONS & SYSTEM FAILURES

We will issue manual refunds exclusively under the following conditions:

  • Severe Node Corruption: If an Architect uploads a payload that is demonstrably broken, corrupted, or violates our Terms of Service (e.g., promising a $50 gift card but delivering a blank text file).
  • Network Outages: If the Evantics Firebase database experiences a documented downtime event that causes your terminal decryption to fail despite a correct checksum.

5. DISPUTE INITIATION

If you believe your transaction qualifies for a system failure refund, you must contact our support node within 48 hours of the anomaly. Include your User UID, the target Node ID, and a detailed log of the error. False disputes or unauthorized chargebacks will result in an immediate, permanent IP and UID ban from the network.