Contacts
Contacts
This page provides the main contact channels for Feanor LAW and is intended
for user requests, support questions, clarifications, complaints, and formal notices.
Working entry points
How to enter the system right now
Website: trust, quick first analysis, and scenario orientation
Mini App: current case, documents, deadlines, and next step
Telegram bot: fast entry, follow-up, and return into the right route
Public publication
What the site will not fake
Exact operator details, formal notice channels, and public contact requisites
are published only where a confirmed legal publication exists.
This page does not imitate them with invented legal depth.
1. User requests
What users may contact us about
The listed channels may be used for:
— questions about the website, Telegram bot, and Mini App;
— requests related to calculations, legal scenarios, and document functions;
— error reports and technical issues;
— questions about privacy, terms, and the trust layer;
— requests about cooperation, access, support, or service use.
2. Message format
How to send a useful request
To speed up handling, it is recommended to include:
— a short summary of the issue;
— a return contact channel;
— if the issue is technical, the page, approximate time, and short scenario description;
— if the issue is about a document or calculation, the minimum necessary context for review.
3. Attachments and materials
What may be provided
Where necessary, the user may provide documents, screenshots, PDF files,
images, voice messages, and other materials required to review the request or prepare a response.
Users are encouraged not to send excessive data if it is not required for the конкретный вопрос.
4. Response timing
How requests are handled
Requests are handled within a reasonable period depending on the type of issue,
the volume of materials, technical workload, and the priority of the relevant channel.
If a request requires additional review, document preparation, factual verification,
or separate coordination, the response period may be longer.
5. Formal notices
Separate route for formal communications
If a user needs to send a complaint, formal notice, data-processing request,
privacy-related message, or other legally significant communication,
a dedicated contact channel and address should be specified by the operator.
Legally significant notices should be sent only to the separately published operator route
once such a route is explicitly disclosed in the public legal pages of the service.
6. Honest page status
What this page already does
This page defines the public communication role of the website and points to the real launch surfaces.
It does not invent contact usernames, requisites, or notice addresses that are not present in the source of truth.
To start working, use the live product routes:
— /en/case-types.html for a quick first-pass analysis on the site;
— /tma to enter the live Mini App command center;
— /tma?entry=calculators&topic=consumer as an example of a topic-aware Mini App handoff.
Next layer
Communication, trust, and legal structure
The site should explain public communication and launch rules honestly,
while the working user corridor continues in the Mini App without fake account depth.