AqylTap Site Refund Policy

Last updated: 2026-06-26

1. Scope

This Refund Policy applies to paid AqylTap site plans purchased through the website flow, including recurring training subscriptions such as Premium and Grandmaster.

2. General Rule

A refund is not automatic just because a subscription was canceled, a user changed their mind, a user did not use the full paid period, or a user did not use all available PGN lookups.

Cancelling a subscription disables future renewals but normally leaves already paid access active until the end of the current billing period.

3. When a Refund May Be Considered

A refund may be considered when the paid service was not actually rendered because of a technical fault attributable to the platform or its payment flow.

Examples include a successful charge without the paid plan being applied, a duplicate or unknown charge caused by the platform or payment flow, or a verified internal technical failure that prevented delivery of the purchased access.

4. Cases That Are Normally Not Refundable

Refunds are normally not issued when requested games or materials are not available in open or connected sources, incorrect FIDE data was entered, the service was actually rendered, the user chose not to use the service, multiple FIDE IDs prevent reliable matching, or the subscription was canceled after the paid period had already begun.

5. Subscription Cancellation and Refunds

Subscription cancellation and refunds are different actions. When a user cancels, future recurring charges are turned off, already paid access remains until the current paid period ends, and the cancellation itself does not create a right to an immediate refund.

6. Failed Payments and Repeated Charges

If a payment fails, the user should first confirm that no successful charge was posted before trying again. If a payment succeeded but the plan did not update, the user should avoid creating a second payment immediately and should contact support if the issue persists.

7. How to Request Review

Refund-related requests should be submitted through the site support ticket flow. The request should include the account identifier or email used for the purchase, payment date, charged amount and currency, selected plan, reason for the request, and any visible payment or checkout error text.

If support requests card details for identification, provide only the last four digits through a protected support channel. Never send the full card number, CVV/CVC, one-time bank codes, or account passwords.

8. How Requests Are Handled

Refund requests are reviewed manually based on whether the service was actually delivered, whether a verified technical fault occurred, whether the issue came from missing external chess data rather than platform failure, and the billing and account state recorded in the platform.

9. Operational Notes for the Team

Before publishing this policy externally, the team should confirm the final legal entity name, whether provider-specific refund timing language should be added, and whether a formal review timeframe should be published.