> For the complete documentation index, see [llms.txt](https://spread-hunter.gitbook.io/spread-hunter-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spread-hunter.gitbook.io/spread-hunter-docs/english/refunds.md). # Refund Policy **Version:** 1 · **Effective from:** June 17, 2026 This Policy explains the terms of payment and refunds for **Spread Hunter** (`spreadhunter.app`). It forms part of the [User Agreement](/spread-hunter-docs/english/terms.md); terms are used with the meaning defined in the Agreement. *** ## 1. Nature of the service The Subscription provides **immediate digital access** to the paid features ("My Bots", "P\&L"). The provision of the service is deemed to have **begun at the moment of automatic activation of the Subscription** following confirmation of the transfer on the blockchain. Payment is made in the cryptocurrency **USDT (BEP20 / BNB Smart Chain)**. ## 2. General rule — payments are non-refundable 2.1. Given the nature of crypto payments (irreversible on-chain transfers) and the immediate provision of digital access, **funds paid for the Subscription are, as a general rule, non-refundable**. This rule applies subject to section 3 (exceptions) and to mandatory consumer rights, in particular the right of withdrawal **before the start** of the provision of access. 2.2. **Consent to immediate provision and waiver of the right of withdrawal.** By placing your payment, you: (a) **give your express prior consent** to the immediate commencement of the service before the expiry of the 14-day withdrawal period; and (b) **acknowledge that you thereby lose your right of withdrawal (a refund)** in respect of the digital access provided during that period. We send confirmation of your consent to your email. Until the moment the Subscription is activated, you have the right of withdrawal; after the provision of access begins, the right of withdrawal does not apply to the extent of the access already provided. ## 3. Exceptions where a refund is possible A refund (full or partial) may be considered if: * you **overpaid** — the excess is **credited** to your balance/Subscription or **refunded** to your address at your choice, less actual network fees; * a **technical failure occurred on our side**: if the paid features were unavailable through our fault for an extended period and access was not restored within **7 days** — the Subscription is extended proportionally or refunded for the unused period; * **the Operator itself discontinues the Service** through no fault of the user — the proportional cost of the unused days of the Subscription is refunded; * a refund is **required by mandatory rules** of the consumer-protection legislation of your jurisdiction. ## 4. Payments that are not credited automatically 4.1. If you sent an **inexact amount** — the payment may not be credited automatically and may go into the manual review queue; we credit or refund the funds in accordance with the procedure of this Policy. 4.2. If you sent funds **to the correct address but in a different network or with a different token**, such funds **technically arrive at our address** and will be processed manually: credited to the Subscription at the current rate or refunded to the address you specify **less actual network fees** (processing — up to **5 business days**). 4.3. By contrast, funds sent **to a wrong address** (not to the one generated for the invoice) fall **beyond our control** — we cannot recover them and bear no liability for this. **Carefully check the network, address, and amount before transferring.** ## 5. Inapplicability of chargeback Payment in cryptocurrency is **final and irreversible at the blockchain level**; the payment-dispute mechanism (**chargeback**) available for bank cards **does not apply** to crypto payments. Any refunds are made solely in accordance with the procedure of this Policy, in USDT BEP20 to the address from which the payment was received, or to another agreed address. ## 6. Expiry and renewal of the Subscription 6.1. The Subscription is valid for the period paid for. Days purchased are **added** to the current expiry date (nothing is "burned" when an active Subscription is renewed). 6.2. On expiry, a **Grace period (24 hours)** in view mode applies, after which the open positions of the Bots may be **automatically closed at market prices** (possibly unfavorable ones), and the paid features disabled. Non-renewal of the Subscription **is not** grounds for a refund for the period already provided. ## 7. Referral payouts 7.1. The referral balance **is not** a payment for a service and has its own terms (minimum payout amount, manual processing, holding period) — see the [User Agreement](/spread-hunter-docs/english/terms.md), section 9. 7.2. In the event of a **refund to the payer**, the corresponding referral accruals are **reversed**. We may withhold or cancel referral accruals on the grounds set out in section 9.5 of the User Agreement (fraud, self-referral, fictitious, disputed, or cancelled payments, abuse). ## 8. How to request a refund Send a request to **** stating the account email, the date and amount of the payment, and (if available) the **txid** of the transaction. We **confirm receipt within 2 business days** and provide a substantive response within **14 days**; an agreed refund is carried out within **14 days** of the agreement. Requests are accepted in Ukrainian and English. ## 9. Changes to the Policy We may update this Policy; the current version is always available at `spreadhunter.app/refunds` (or in the corresponding GitBook publication), with the date and version number. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://spread-hunter.gitbook.io/spread-hunter-docs/english/refunds.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.