Refund Policy — EASY Bots

2.1. Digital Goods are intangible products delivered by providing access (link, account, License Key); they cannot be "returned" physically. Delivery is deemed completed when access is granted (issuance/activation of a License Key and/or provision of a download link).

2.2. Refund availability depends on the payment method chosen at checkout: Card Payments are covered by the 30-day money-back guarantee (Section 4), refunded to the original card; Crypto Payments are final sale (Section 5.1) because blockchain transactions are irreversible, which is disclosed before payment.

2.3. The completion of delivery under Section 2.1 does not limit the 30-day guarantee for Card Payments: the guarantee applies after delivery, during the evaluation window, on the conditions set out in Section 4.

3.1. This Policy applies only to EASY Bots Digital Goods purchased directly on the Website from the Operator.

3.2. This Policy does not apply to third-party goods/services purchased via links, from partners, marketplaces, resellers, or otherwise outside the Website, unless the Operator expressly confirms otherwise in writing.

3.3. This Policy is the sole and exclusive policy governing refunds for Paid Licenses, as referenced in the Terms of Service. In the event of any conflict between this Policy and other Operator documents regarding refunds, this Policy governs.

3.4. Nothing in this Policy limits any non-waivable rights the User holds under the mandatory consumer protection law of the User's country of residence.

4.1. If you paid for a Purchase by Card Payment, you may request a full refund within 30 (thirty) calendar days of the Purchase date if you are not satisfied with the product. You do not need to prove a software defect: dissatisfaction with the product within the window is a sufficient reason.

4.2. The guarantee applies subject to the following conditions:

• 4.2.1. The Purchase was paid by Card Payment via the payment tools available on the Website.
• 4.2.2. The request is submitted within 30 (thirty) calendar days from the Purchase date (date and time are determined by the Operator's/payment provider's system records).
• 4.2.3. Before the refund is finalized, the User completes one support interaction (Section 6.2) so the Operator has an opportunity to resolve the issue. The User is not required to accept a proposed resolution.
• 4.2.4. It is the User's first refunded Purchase: the guarantee covers one (1) refunded Purchase per customer (Section 12.2).
• 4.2.5. No abuse grounds under Section 12.3 apply.

4.3. Purchases made with a discount, promo code, or during a sale are covered on the same terms when paid by Card Payment; the refund amount equals the amount actually paid.

4.4. The refund equals the full amount you paid for the Purchase; the Operator does not deduct its own additional fees from it.

5.1. Cryptocurrency — final sale: Refunds do not apply to Crypto Payments. Blockchain transactions are irreversible by design: once a payment is confirmed on-chain, neither the Operator nor the payment processor can reverse it, and exchange-rate volatility makes an equivalent return impossible to guarantee. This is disclosed on the checkout screen before you confirm a Crypto Payment; if you want the protection of the 30-day guarantee, choose the Card Payment option.

5.2. Exception for non-delivery: If you paid with cryptocurrency and did not receive access to the purchased Digital Goods (no License Key issued and no download access granted), contact support (Section 14). The Operator will deliver the product or, where delivery is impossible, credit the paid amount to your User Wallet.

5.3. Requests outside the time limit: A request submitted after 30 days from the Purchase date is not eligible. The request date is the date your first refund message is received (Section 7).

5.4. Free Licenses: Free Licenses (including licenses granted through the Partner Broker Program) involve no purchase price, so there is nothing to refund; they are governed by Section 8 of the Terms of Service.

5.5. License violations and abuse: Refunds may be refused where there is objective evidence of:

• (a) sharing the License Key with third parties;
• (b) reverse engineering, modification, decompilation;
• (c) bypassing license restrictions;
• (d) payment fraud or use of stolen payment credentials;
• (e) creating multiple accounts or repeated purchase/refund patterns to claim multiple refunds (see Section 12).

5.6. Parallel disputes/chargebacks: Please contact the Operator under this Policy before initiating a chargeback — a direct request is faster and lets the issue be resolved properly. If a chargeback is initiated for the same transaction while a request is under review, the Operator may pause the review until the card network's process resolves the dispute, to avoid a double refund of the same payment.

6.1. Reasons. For Card Payments within the 30-day window, dissatisfaction with the product is a sufficient reason (Section 4.1) — you do not need to prove a defect. Describing what did not meet your expectations helps us improve the product and often lets support fix the issue in hours, but a detailed technical justification is not a condition of the guarantee.

6.2. Support-first step. As part of processing your request, the support team responds once with either a resolution attempt (for example, a configuration fix, an update, or a replacement version) or confirmation of the refund. You are not required to accept a proposed resolution; if you still want the refund after this single interaction, it proceeds under Section 8. This step exists because most reported issues are configuration-related.

6.3. Trading results. A losing period is not a software defect: trading outcomes depend on market conditions, execution, broker conditions, latency, risk settings, and other factors beyond the Operator's control. That is exactly why the guarantee is framed around satisfaction rather than defects — for a Card Payment inside the 30-day window you may request the refund regardless of the cause of your dissatisfaction. Outside the window, trading losses are not a refund ground.

6.4. Helpful evidence (optional). If your reason involves a technical malfunction, attaching a description of the issue, screenshots, platform logs, and your settings speeds up both the fix attempt and the review; support may request them, but for a request under the 30-day guarantee they are not mandatory.

7.1. Recommended submission method: via the Operator's Telegram bot: https://telegram.me/forexroboteasybot

Command to initiate the process: /refund

7.2. The User should provide:

• (a) Website account details (email/ID);
• (b) Purchase details (product name, date, amount, payment method);
• (c) a brief description of the refund reason;
• (d) optionally, any technical evidence under Section 6.4.

7.3. Refund requests may also be submitted by email to [email protected] from the email address associated with the account.

7.4. If required information under Section 7.2(a)–(b) is missing, the Operator will ask for it once; the review period (Section 8) runs from when the complete information is received. The request date for the purposes of the 30-day window is the date of your first refund message.

8.1. The Operator reviews refund requests and issues a decision within 10 (ten) business days from the date a complete request (Section 7.2) is received.

8.2. Following review, the Operator will take one of the following actions:

• (a) approve the Refund;
• (b) refuse the Refund, stating the specific reason with reference to the relevant section of this Policy (for example: outside the 30-day window, Crypto Payment, or a Section 12 abuse case);
• (c) offer a fix/alternative solution as the single support-first step (Section 6.2) — after which, if the User still wants the refund, action (a) follows for eligible requests.

8.3. After approval, the time for funds to reach the card depends on the bank and card network — typically 3 (three) to 10 (ten) business days after the Operator initiates the transfer.

9.1. Approved refunds for Card Payments are returned to the original bank card used for the Purchase.

9.2. Optionally, at the User's explicit request, a refund may instead be credited to the User Wallet (for example, if the User plans to purchase a different product). This is the User's choice: the Operator does not substitute a wallet credit for a card refund without the User's consent.

9.3. Where a return to the original card is technically impossible (card closed, processor limitation), the Operator will agree an alternative lawful refund method with the User.

9.4. Funds credited to the User Wallet at the User's choice may be used to purchase other Digital Goods or withdrawn where the withdrawal function is available, subject to security checks; withdrawals may be paused while a dispute/chargeback on the original transaction is open, to avoid a double refund.

10.1. Upon approval of a Refund, the User's right to use the relevant Digital Goods terminates. The license terminates and the License Key (and/or product access) will be revoked/disabled by the Operator.

10.2. The User must cease using the Digital Goods, delete all copies (including installation files, libraries, settings, derivative files, where applicable) from devices, VPS, and other media, and must not transfer the Digital Goods to any third party.

10.3. Any use of the Digital Goods after a Refund constitutes a material violation of the Operator's rights and may result in protective measures including account suspension, refusal of service, recovery of damages, and/or other remedies permitted by applicable law.

11.1. EASY Bots Digital Goods are automation tools. The Operator is not a broker, dealer, asset manager, and does not provide personalized investment advice.

11.2. The Operator does not guarantee profitability, absence of losses, achievement of specific financial results, the User's expected returns/drawdowns/trade frequency, or uninterrupted operation under a specific broker/account/market.

11.3. The User acknowledges that trading outcomes depend on market conditions, execution quality, infrastructure, risk settings, deposit size, broker limitations, and other factors. These circumstances are not a software defect; within the 30-day guarantee window for Card Payments they nevertheless do not prevent a refund, because the guarantee is satisfaction-based (Section 6.3).

12.1. The money-back guarantee exists to let genuine customers evaluate the product at limited risk. The protections below keep it sustainable.

12.2. One refunded Purchase per customer. The guarantee covers one (1) refunded Purchase per customer. A repeat Purchase of the same product after a refund of that product is final.

12.3. Abuse. The Operator may refuse a refund where there is objective evidence of abuse: payment fraud or stolen payment credentials; EULA violations (for example, sharing or reselling License Keys); creating multiple accounts to claim multiple refunds; or patterns of purchasing and refunding products across accounts.

12.4. Chargebacks. Please contact the Operator before initiating a chargeback — a direct request under this Policy is faster and resolves the matter properly. If a chargeback is filed for a transaction that has already been refunded, the Operator will respond to the chargeback with the refund evidence, and may pause the account until the card network's process resolves the dispute, to prevent a double refund of the same payment.

13.1. The Operator may amend this Policy unilaterally. The new version becomes effective upon publication on the Website unless another effective date is stated.

13.2. The version of the Policy effective on the Purchase date applies to that Purchase unless applicable law requires otherwise. Changes do not retroactively reduce the refund rights attached to Purchases already made.

14.1. Recommended channel to submit Refund requests: Telegram bot https://telegram.me/forexroboteasybot, command /refund.

14.2. Additional support channels may be listed on the Website. The Operator may conduct communications and make decisions based on communications via official channels.

15.1. This Policy applies to the maximum extent permitted by applicable law. If any provision is held invalid, the remaining provisions remain in effect.

15.2. No action by the Operator (including reviewing a request, requesting data, offering alternatives) constitutes an admission of defect or an unconditional obligation to issue a Refund unless expressly confirmed by the Operator.

15.3. By continuing to use the Website and/or making a Purchase, the User confirms that they have read, understood, and agreed to this Policy.