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.
1.1. Filexa is available through @FilexaAIBot and related interfaces (the Service).
1.2. The Service is owned by Nikita Andreevich Andrianov, Russian taxpayer identification number 773001849734, an individual applying the Russian Professional Income Tax regime (the Developer).
1.3. The Service is for legally capable individuals aged 18 or older for personal, non-commercial use. Commercial use requires a separate written agreement.
1.4. Starting to use the Service after receiving a link to this Agreement confirms that the User has reviewed it. Where personal-data consent is required, the User gives it through a separate affirmative action after receiving the applicable text; the Service records its version, date, method and technical evidence.
2.1. Filexa may process files, text, images, audio and video, create AI-assisted material and provide other functions shown in the interface. Models, formats, limits and processing times may change for technical, legal or product reasons.
2.2. Some functions are technically performed by external AI and API providers. Necessary prompts and attachments may be transmitted to them and processed under their own rules. The Developer does not control their uninterrupted availability, response time or output quality.
2.3. Filexa is not storage or a backup service. Users must save important source material and results themselves.
2.4. Local generation and connector sharing. A local-connector owner may voluntarily give another User an attachment code or link. That User's prompts, links, files, references and results technically pass through the owner's computer. A warning is shown before attachment; the attaching User must choose only a trusted host, and the owner must keep any accessible processing lawful and confidential. Attachment transfers no account, plan or Lex.
3.1. The main account identifier is the Telegram ID. A username or profile name may change and is not reliable identity proof.
3.2. The User must protect the Telegram account, device, sessions and two-factor authentication. Actions from the authorised account are treated as the User's until compromise is reported and reasonable protective measures can be applied.
3.3. Access to an account, plan or allowance must not be sold, leased or transferred to another person.
4.1. Filexa may share plan and balance accounting with other Developer products. Linking is voluntary and requires proof of control of both accounts; matching contact details alone is insufficient.
4.2. Linking does not transfer or add balances. Billing automatically selects one active financial profile by the effective plan and its priority rules; suppressed funds are not fallback funds. Operations through linked interfaces reduce that profile under the applicable product rules. No product receives another product's password or full authentication data.
4.3. Linking or unlinking may be temporarily blocked by an active reservation or conflicting financial state. Unlinking affects future operations only and does not reverse completed requests, deductions, payments or credits or move funds from their home profile. A subscription must be cancelled separately through its purchase channel.
AI output may be inaccurate, incomplete, fabricated, outdated or unexpected. It is not medical, legal, financial or other professional advice. The User must independently verify important information and consult an appropriate professional before decisions affecting health, safety, rights or money. The Developer does not guarantee uniqueness, exclusive rights, registrability or fitness for a purpose. Subjective dissatisfaction with style or content is not by itself a technical defect.
6.1. The User retains rights in submitted material and grants the Developer a limited, non-exclusive, royalty-free technical licence to copy, transform and send it to engaged providers only to perform the operation, provide security and support.
6.2. The User confirms that all necessary rights, permissions and prior consents exist for submitted text, files, images, voice, correspondence and other material. Prompt content may be processed transiently by Filexa and providers; no persistent content-based User profile is created. The Developer does not acquire a right to publish User material or use it in advertising without a separate basis.
6.3. Automatic masking may replace fragments resembling personal data with synthetic values before external transmission. It reduces risk but is not guaranteed to identify every item and does not permit prohibited data.
The User must not:
In a group, channel discussion or shared chat, a request and result may become visible to participants. The invoking User is responsible for the audience, rights and appropriateness. Private material should be processed in a private chat.
The Developer may reject a request, pause an operation or restrict access on reasonable evidence of a breach, security risk, legal requirement or provider/platform demand. Serious or repeated violations may result in termination. A User may request review where safe and lawful. A restriction does not remove obligations for a paid but unperformed part or non-waivable rights.
10.1. The Service is supplied “as is” and “as available.” Interruptions, queues, provider limits and changes in external model quality may occur.
10.2. Free functions, models, interfaces and technical limits may change. A paid amount is not materially reduced retroactively except where law, security or provider discontinuation requires it; a reasonable replacement or remedy for the unperformed part is then considered.
10.3. The Developer is not responsible for failures of Telegram, User connectivity or devices, AI/API and payment providers, mandatory government restrictions or blocking, distribution platforms or hosting, but takes reasonable measures to restore the Developer-controlled part. This does not remove obligations for a paid but unperformed part.
The Service code, design, names, documents and infrastructure belong to the Developer or relevant owners. No exclusive rights in the Service or third-party models are transferred. Rights in an AI result depend on its nature, User contribution and applicable law; exclusivity or registrability is not promised. A rightsholder may email thismailnotbad@gmail.com identifying the disputed request or output, evidence of rights, the alleged infringement and contact details. The Developer records and reviews the complaint, may temporarily restrict access while checking it, considers the User's counter-notice, and communicates the decision. Knowingly false complaints are prohibited.
Data categories, purposes, retention and processing are described in the Privacy Policy. Required consent is given separately and its version, date, method and technical evidence are recorded.
The User is responsible for lawful prompts, material, third-party rights and further use of output. To the extent permitted by law, the User compensates documented losses and expenses directly caused by their breach. No clause excludes liability or remedies that mandatory law does not allow the parties to exclude. The Developer is not responsible for indirect consequences of decisions based on AI output unless mandatory law says otherwise.
The current version is linked from the Service. Changes apply to future use; material changes affecting paid functions are communicated by an available method. The User may stop using Filexa at any time, but stopping use does not automatically cancel a subscription.
Russian law governs, subject to non-waivable consumer protections applicable in the User's country of residence. Requests: thismailnotbad@gmail.com. Official page: tnick.cc. Invalidity of one clause does not affect the others.
Previous editions: