Version dated 28 August 2026
Russian original. This English text is a translation for convenience. If the texts differ, the Russian original prevails to the extent permitted by mandatory law.
This Policy forms part of the Filexa Public Offer. Platform rules also apply where the platform independently decides a refund.
1.1. Filexa supplies subscriptions, one-time Lex packages and individual digital operations. Lex is an internal conditional accounting unit for services, not currency, electronic money, a security or independent payment instrument. It cannot be transferred between users or exchanged by the Provider for money except when calculating a lawful refund against the original payment.
1.2. Crediting Lex confirms activation but does not remove mandatory rights concerning an unperformed part. Lex spent on a technically completed operation is not refundable merely because the AI output is subjectively unsatisfactory.
A full refund of the relevant payment may be available where:
3.1. A User may refuse the unperformed part. The refund calculation may deduct completed operations, the actually used part of a paid period, and documented direct expenses attributable to that contract and refund where law permits.
3.2. Free, welcome, promotional and compensatory Lex has no cash value.
3.3. Lex is spent from the monthly plan allowance first and the one-time additional balance second. A failed-operation restoration returns Lex to its original source: the plan part only while its plan period remains active, and the additional part to the additional balance.
3.4. An expired billing period is normally not refunded where access was available and no objective defect was established.
4.1. A failed operation that delivers no result must not consume Lex. If it did, Filexa first restores the corresponding amount after verification and records the restoration in operation history.
4.2. If restoration does not remedy the breach or Filexa cannot continue the paid service, the User may request a money refund for the unperformed part.
4.3. Examples include a successful deduction with no result, a corrupted or unavailable output file, duplicate deduction for one operation, or a confirmed Filexa fault.
4.4. Subjective dissatisfaction, an inadequate prompt, a lawful safety refusal, violation of published file requirements, or a User-side device or connection problem is not by itself a technical failure. This limitation does not apply where the result objectively fails the described function or mandatory law provides another remedy.
Cancelling renewal stops future charges and does not automatically refund the current period. A current-period request is assessed by actual use, availability and applicable law. Deleting Telegram, blocking the Bot or ceasing use does not itself cancel renewal.
Email thismailnotbad@gmail.com and provide the Telegram or account ID, payment date, amount and currency, receipt or payment ID, failed-operation ID where relevant, reason and a contact method. Never send a full card number, CVC/CVV, password or banking code. The Provider may request proportionate evidence needed to match the payment and prevent fraud.
A monetary claim is reviewed within the period required by law; the target response time is up to 10 calendar days from receipt of the claim. Requesting missing information does not restart that period. An approved refund goes through the original payment method unless law or the provider requires otherwise. Bank or platform processing time may apply. The Provider adjusts the Russian Professional Income Tax receipt where required.
8.1. A Telegram Stars request may need to be submitted through the platform under the Telegram terms for virtual goods. Filexa supplies available transaction information but cannot replace a decision controlled by Telegram.
8.2. For a rouble payment through Robokassa, send the request to the Provider under section 6. Robokassa's Privacy Policy covers payment processing. An approved refund is made through the original channel unless law or provider rules require otherwise.
8.3. If an Apple/Google purchase becomes available in a linked mobile interface, cancellation and refund follow the relevant store procedure. RevenueCat carries technical purchase events and does not replace the store decision.
A refusal of a voluntary refund does not prevent the User from using remedies available under Russian law, including court or the Russian consumer authority. Nothing in this Policy limits rights that cannot lawfully be waived.
Previous editions: