Public offer and privacy policy.
Current redaction of the WAM Agents service: offer agreement, personal-data processing policy, registration details and provider contacts.
Public Offer and Privacy Policy of the WAM Agents service
Provider: Individual Entrepreneur Silenkov Maxim Eduardovich
TIN: 711613398109
OGRNIP: 310715428100134
Address: 368600, Russia, Republic of Dagestan, Derbent, Avtovokzalnaya St., 10
Contact: we@magnet.tg
Service: WAM Agents
Entry point: Telegram bot @wamagentsbot · documentation https://docs.magnets.tg/
Effective date: April 13, 2026 Last updated: April 21, 2026
This is an unofficial English translation of the WAM Agents Public Offer and Privacy Policy. It is provided for the User’s convenience. In case of any discrepancy between this translation and the Russian text, the Russian version prevails as the authoritative published text.
Part A — Terms of Service (the Public Offer)
1. General provisions and acceptance
1.1. This document constitutes a public offer by Individual Entrepreneur Silenkov Maxim Eduardovich, TIN 711613398109, OGRNIP 310715428100134 (hereinafter — the “Provider”), within the meaning of Articles 435 and 437 of the Civil Code of the Russian Federation, and contains all essential terms of the contract for the paid provision of services granting access to the WAM Agents Service (hereinafter — the “Agreement”).
1.2. Acceptance of this offer, in accordance with Article 438 of the Civil Code of the Russian Federation, is effected by the User performing any of the following conclusive actions: (a) clicking the “I accept” button in the @wamagentsbot interface, (b) payment of the Subscription, or (c) use of the Service after the Effective date.
1.3. By accepting this offer, the User confirms that they have read its terms and the Privacy Policy (Part B of this document) and agree to them in full.
1.4. This offer may be amended by the Provider unilaterally in the manner set out in Section 15 of this Part.
2. Definitions
2.1. Service / WAM Agents — the Provider’s technology service that provisions, for each User, an isolated computing environment (the Container) connected to Telegram, enabling the operation of a personal AI agent powered by Anthropic’s Claude large-language models.
2.2. Agent — the AI assistant configured, instructed and operated by the User inside the Container.
2.3. Container — an isolated Docker environment allocated by the Provider to each User with hardened security settings (disabled privileges, read-only root filesystem, dropped Linux capabilities, dedicated writable volumes, non-root execution).
2.4. Bot Token — a Telegram Bot API token either provided by the User or generated on the User’s behalf using the Provider’s tooling. The token belongs to the User’s Telegram account.
2.5. OAuth Token — an Anthropic API access token issued for the User’s own account on claude.ai. The OAuth Token is used inside the Container to call the Anthropic API on the User’s behalf.
2.6. Subscription — the User’s right to use the Service during the paid period.
2.7. Output — any text, data, media, decision or action generated or performed by the Agent inside the User’s Container.
2.8. User — a natural person who has entered into this Agreement with the Provider by accepting this offer.
3. Description of the Service
3.1. WAM Agents is a Telegram-native personal agent service. On activation, the Provider allocates a dedicated Container to the User, connects it to the User’s Telegram account via the @wamagentsbot bot and/or a bot created on the User’s behalf, and provides access to the Agent inside Telegram.
3.2. The Agent’s computations are performed by Anthropic, PBC (USA) — a third-party large-language-model provider. The Service calls the Anthropic API using the User’s own OAuth Token. The fee for model inference is charged by Anthropic directly against the User’s Anthropic subscription, separately from the Subscription fee payable to the Provider. With respect to traffic to the Anthropic API performed via the User’s OAuth Token, the Provider does not determine the composition or content of the data transferred; the User is recognised as an independent data operator in relation to such transfer.
3.3. The Service includes: allocation of the Container and management of its lifecycle, baseline Agent configuration (policies, skills, tools), security monitoring, log rotation within operational limits, and user support via the /support command in @wamagentsbot.
3.4. The Service is a technology platform. The Provider does not provide legal, medical, financial, tax, human-resources or other regulated professional advice and bears no liability for the consequences of decisions taken by the User on the basis of the Agent’s Output.
4. Beta status
4.1. The Service is provided in public beta. Functionality, pricing plans, limits and integrations may be changed, added or disabled. A specific service level (availability, latency, support response time) is not guaranteed unless expressly agreed in writing.
4.2. The Provider shall give notice of material changes at least 30 days in advance in the manner set out in Section 15.
5. User capacity
5.1. The User represents that:
(a) they are at least 16 years old, or have reached the minimum age required in their jurisdiction;
(b) they have the legal capacity to enter into this Agreement;
(c) if using the Service on behalf of a legal entity, they are authorised to bind that legal entity by this Agreement;
(d) they hold, or will create, an Anthropic account with an active Claude subscription sufficient for Agent operation.
6. Account, Bot Token and OAuth Token
6.1. Bot Token. The User either provides the Provider with an existing Bot Token, or authorises the Provider to generate one on the User’s behalf via the Telegram BotFather tooling supplied by the Provider. The bot belongs to the User; the Bot Token authenticates the Agent within Telegram.
6.2. OAuth Token. The User either provides the Provider with their Anthropic OAuth Token, or authorises the Provider to obtain it on the User’s behalf via tooling that delegates authorisation through claude.ai. The OAuth Token authenticates the Agent with Anthropic on behalf of the User’s own subscription with Anthropic.
6.3. Storage and use. The Provider stores the said tokens in the billing ledger solely for the purpose of operating the Service for the User, applies access-control measures to them and does not use them for any other purpose.
6.4. Revocation. The User may revoke the Bot Token via BotFather and the OAuth Token via claude.ai at any time. Revocation renders the Service technically inoperable until replacement credentials are supplied.
6.5. Account security. The User is responsible for the security of their Telegram and Anthropic accounts. The User shall notify the Provider at we@magnet.tg without undue delay of any unauthorised access to either account.
7. The Agent, autonomy and human oversight
7.1. The User has sole control over the Agent’s configuration: prompts, policies, connected tools, skills and autonomy levels.
7.2. The Service supports configurable autonomy levels, including: (a) Automatic — the Agent acts and reports the result; (b) Confirmation required — the Agent proposes an action and waits for User approval; (c) Blocked — the action is never performed autonomously.
7.3. The User bears sole responsibility for all actions of their Agent, including actions performed under levels configured as Automatic. The User undertakes to exercise human oversight whenever an Agent action may entail material, legal, financial or irreversible consequences.
7.4. The User acknowledges the non-deterministic nature of LLM systems: the Output may be inaccurate, incomplete, outdated or unexpected; the User shall verify the Output independently before relying upon it.
7.5. The User shall comply with Anthropic’s Usage Policies (anthropic.com/legal) and Telegram’s Terms of Service (telegram.org/tos) in their current form.
8. Acceptable use
8.1. The User undertakes not to use the Service, and not to allow their Agent to be used, to:
(a) violate the applicable laws of the Russian Federation, including provisions on counter-extremism, information dissemination, and intellectual-property rights;
(b) commit fraud, deception, impersonation, or money laundering;
(c) distribute malware or gain unauthorised access to information systems;
(d) send spam, threats, insults, carry out mass mailings without the recipients’ consent, or incite violence;
(e) unlawfully collect, process or disclose the personal data of third parties;
(f) create or distribute materials containing child sexual abuse, materials facilitating the creation of weapons of mass destruction, or any other content prohibited by law or by Anthropic’s Usage Policies;
(g) infringe the intellectual-property or other rights of third parties;
(h) interfere with the security, integrity or performance of the Service;
(i) perform reverse engineering, automated data scraping or benchmark testing of the Service without the Provider’s prior written permission.
8.2. The Provider may investigate suspected violations, cooperate with lawful requests from state authorities, and apply the measures set out in Section 12.
9. User content and intellectual property
9.1. Provider’s intellectual property. The Provider retains all rights in the Service software, infrastructure, documentation, and in the designations “WAM Agents”, “We Are Magnets” and associated marks, to the extent such rights vest in the Provider.
9.2. User content. “User content” means the data, prompts, configurations, files and other content that the User places inside, or creates within, the Container. All rights in User content remain with the User. The User is responsible for holding the necessary rights and consents to place User content.
9.3. Licence to the Provider. The User grants the Provider a non-exclusive, royalty-free licence to host, process, transmit and technically adapt User content solely to the extent necessary to provide, protect, maintain and improve the Service for the User.
9.4. No training use. The Provider does not use User content to train artificial-intelligence models. Content transmitted through Anthropic is governed by the applicable Anthropic API terms.
9.5. Output. Output generated by the Agent belongs to the User — subject to the rights of third parties and to the conditions imposed by Anthropic and other upstream providers in respect of model-generated content.
10. Fees, payment order and fiscal documentation
10.1. Fee amount. The Service is provided on the basis of a Subscription. The current fee, charging frequency and supported payment methods are disclosed in @wamagentsbot at the point of subscribing. As of the Effective date, the tariff is 990 roubles per calendar month, with automatic renewal.
10.2. Tax regime. The Provider applies the simplified taxation system with the “income” object (USN “income”) and is not a payer of value-added tax pursuant to Article 346.11 of the Tax Code of the Russian Federation. The fee is stated exclusive of VAT.
10.3. Payment and acquiring. Payments are accepted in Russian roubles via acquiring provided by JSC “T-Bank” (TIN 7710140679). The full bank card numbers are not processed by the Provider.
10.4. Fiscal documents. At the moment of receiving payment, the Provider ensures that a cashier’s receipt is generated and sent to the User in accordance with Federal Law No. 54-FZ of 22 May 2003 “On the application of cash-register equipment…”. The receipt is sent to the email address indicated by the User during payment.
10.4.1. Fiscal agent. Generation of cashier’s receipts is performed via the fiscal service LLC “CLOUDKASSIR” (TIN 7725364512, legal address: 117342, Moscow, Butlerova St., 17B), acting as a payment agent within the meaning of clause 9, Article 2 of Federal Law No. 54-FZ of 22 May 2003. The cashier’s receipt may list LLC “CLOUDKASSIR” as the entity generating the receipt, and the Provider — IE Silenkov M. E. (TIN 711613398109) — as the Supplier. This technical fiscalisation arrangement does not alter the legal relationship between the User and the Provider: the supplier of the service and the sole party to this Public Offer Agreement is IE Silenkov M. E.
10.5. Auto-renewal. A paid Subscription is automatically renewed for subsequent periods at the tariff in effect at the moment of charge, on the calendar day corresponding to the day of the first successful charge. The User consents to recurring charges from the registered payment method until cancellation. On a failed charge, the Provider shall make up to 3 (three) retry attempts at 24-hour intervals; if retries are exhausted, the Subscription is cancelled and the Container is placed into a waiting state pending payment restoration.
10.6. Consumer User’s right to withdraw. In accordance with Article 32 of the Law of the Russian Federation No. 2300-1 of 7 February 1992 “On the Protection of Consumer Rights”, a User acting as a consumer may withdraw from this Agreement at any time, provided that they pay the Provider the costs actually incurred by the Provider in the performance of this Agreement. Withdrawal is effected via the /cancel or /support command in @wamagentsbot. A refund is issued pro rata — for the unused portion of the paid period — to the original payment method within 10 (ten) business days.
10.7. Auto-renewal cancellation. The User may cancel auto-renewal via the /cancel command in @wamagentsbot. Cancellation stops future charges; access to the Service is retained until the end of the paid period.
11. Personal data protection
11.1. The processing by the Provider of the User’s personal data is described in Part B of this document (Privacy Policy) and forms an integral part of this Agreement.
11.2. Pursuant to Federal Law No. 152-FZ “On Personal Data”, the Provider ensures that the recording, systematisation, accumulation and storage of personal data of Users who are citizens of the Russian Federation are performed in databases located on the territory of the Russian Federation.
11.3. By accepting this offer, the User consents to the Provider’s processing of personal data in the scope and for the purposes set out in Part B.
11.4. Consent to the cross-border transfer of personal data to the countries listed in Part B, Section 6, is given by the User separately — during onboarding in @wamagentsbot through an active confirmation. Without such consent, the Service cannot be provided technically.
12. Suspension and termination
12.1. The Provider may immediately suspend or terminate access where:
(a) the User materially breaches this Agreement or the Acceptable Use rules (Section 8); (b) the User’s use of the Service creates security, legal, reputational or abuse-related risk for the Provider or third parties; (c) required by law or by a lawful decision of a competent authority; (d) an auto-renewal attempt has failed (clause 10.5).
12.2. The User may terminate the Agreement at any time by:
(a) running the /cancel command in @wamagentsbot — disables auto-renewal; access is retained until the end of the paid period;
(b) running the /delete command in @wamagentsbot — deletes the Container, Agent configuration, tokens and related personal data, subject to the mandatory retention periods set out in Section 8 of Part B and under applicable law;
(c) filing a withdrawal notice in the manner of clause 10.6.
12.3. Post-termination. Within 30 days after termination, the User may request an export of stored User content via /support. After that period, the Provider deletes the User content, save for data whose retention is required by law.
12.4. Survival. The provisions allocating liability for Agent actions performed prior to termination, fiscal documentation, intellectual-property rights, and Sections 8, 13, 14 and 16 survive termination.
13. Liability
13.1. For failure to perform or improper performance of obligations under this Agreement, the Parties bear liability in accordance with the applicable law of the Russian Federation.
13.2. The Provider does not warrant the accuracy, fitness or completeness of the Agent’s Output. The Service is provided “as is” to the extent permitted by applicable law.
13.3. The Provider is not liable for Service malfunctions caused by the actions of third parties, including Anthropic, Telegram, payment services, cloud-infrastructure providers, nor for Service unavailability resulting from force majeure (Section 14).
13.4. Where the User uses the Service as a consumer, any provisions of this Agreement that limit consumer rights to a greater extent than permitted by the Russian Law “On the Protection of Consumer Rights” are null and void in the relevant part; imperative consumer rights cannot be restricted.
13.5. The User bears sole responsibility for their own actions, for the actions of the Agent, and for compliance with applicable law while using the Service (Section 7).
14. Force majeure
14.1. The Parties are released from liability for partial or total non-performance of obligations where such non-performance results from force-majeure circumstances that arose after the conclusion of the Agreement, in accordance with Article 401 of the Civil Code of the Russian Federation. Such circumstances include, in particular: natural disasters, war, terrorism, sanctions, acts of state authorities, pandemics, internet and telecommunications outages, outages of the third-party LLM provider (Anthropic), outages of Telegram, outages of payment services, cloud-infrastructure incidents, and electricity outages.
15. Amendments to the Agreement
15.1. The Provider may update this Agreement. Notice of material changes is given by the Provider via @wamagentsbot, by email addressed to the address supplied by the User for the receipt of fiscal documents, or by in-product announcement, at least 30 days prior to the effective date of the changes.
15.2. If the User does not agree with the changes, they may terminate the Subscription before the effective date of the changes in the manner of Section 12 and obtain a pro-rata refund for the unused paid period in accordance with clause 10.6.
15.3. Amendments do not have retroactive effect as regards the tariff and scope of services for a paid period that has been fully paid prior to the effective date of the amendments.
16. Governing law and dispute resolution
16.1. This Agreement is governed by the law of the Russian Federation.
16.2. All disputes arising in connection with this Agreement shall be settled by the Parties through negotiation. Failing agreement, the dispute is subject to court consideration under the jurisdiction rules established by the legislation of the Russian Federation. A User acting as a consumer may bring a suit at the court of their place of residence in accordance with the Russian Law “On the Protection of Consumer Rights”.
16.3. A pre-trial claim procedure is mandatory. The response time for a claim is 30 (thirty) calendar days from the date of receipt of the claim.
17. Final provisions
17.1. Notices to the Provider are sent to we@magnet.tg. Notices to the User are sent via @wamagentsbot, by email to the address supplied by the User, or by in-product announcement.
17.2. The User may not assign or transfer their Subscription or rights under this Agreement without the prior written consent of the Provider.
17.3. If any provision of this Agreement is held invalid, this does not affect the validity of the remaining provisions.
17.4. This Agreement, together with the Privacy Policy (Part B), constitutes the entire agreement between the Parties in respect of the Service and supersedes any prior understandings.
18. Abuse notices and content-removal procedure
18.1. Where a third party believes that content or actions taken through the Service infringe their rights or are otherwise unlawful, they may send a notice to we@magnet.tg stating: (a) identification of the content; (b) information sufficient to locate it; (c) contact details of the notifier; (d) a statement of good-faith belief that the use is wrongful; (e) a statement of the accuracy of the notice.
18.2. The Provider may investigate, remove or restrict the flagged content, and suspend the associated account, giving the User an opportunity to object.
Part B — WAM Agents Privacy Policy
This Privacy Policy applies to the application. It covers the WAM Agents Service accessible through Telegram (
@wamagentsbot) and the personal Container allocated to each User.
1. Operator
Individual Entrepreneur Silenkov Maxim Eduardovich
TIN 711613398109, OGRNIP 310715428100134
Address: 368600, Russia, Republic of Dagestan, Derbent, Avtovokzalnaya St., 10
Contact: we@magnet.tg
The Operator is entered in the Register of Operators Processing Personal Data maintained by Roskomnadzor (register number: [to be specified upon receipt]).
2. Personal data processed
2.1. Account and identification data: Telegram user identifier (telegram_user_id), Telegram username, Telegram language code, preferred interface language.
2.2. Contact data for receipts: the email address supplied at payment for receiving the fiscal receipt.
2.3. Credential data: Bot Token (Telegram) and OAuth Token (Anthropic), stored solely for operating the Service.
2.4. Payment data: payment-service transaction identifiers, payment status, Subscription state, recurring-charge identifiers (RebillId of JSC “T-Bank”), charging history, promo-code usage. Full bank card numbers and CVVs are not processed by the Operator — that data is processed by the payment provider.
2.5. Consent records: the fact and time of acceptance of the offer, the version of the accepted text, the fact and time of consent to cross-border transfer.
2.6. Service operation metadata: activity logs per Container, including timestamps, command types and short prompt previews (limited to 100 characters) for diagnostics and abuse detection. The full texts of prompts and responses are not retained by the Operator.
2.7. Container telemetry: CPU, memory, disk usage, availability metrics, Docker lifecycle events.
2.8. Agent configuration: policies, skills and other configuration artefacts placed within the writable working space of the Container.
3. Data the Operator does not process
3.1. The Operator does not process the content of the User’s conversations with the Claude model beyond ephemeral transit and the short metadata referred to in clause 2.6. The full bodies of dialogues flow from the User’s Container to the Anthropic API using the User’s OAuth Token and are governed by Anthropic’s privacy and retention policies for the User’s account. For these purposes the User is recognised as an independent data operator in relation to the transfer of dialogue content to Anthropic (see clause 3.2 of Part A).
3.2. The Operator does not process full bank-card numbers, CVVs or other sensitive cardholder data.
4. Purposes of processing
4.1. Registration of the User, allocation and operation of the Container and the Agent.
4.2. Subscription management, billing, auto-renewal, refunds, and generation of fiscal documentation.
4.3. User support, incident response, security monitoring and abuse countermeasures.
4.4. Performance of statutory obligations (including tax and fiscal reporting).
4.5. Service improvement — in aggregated, de-identified form.
5. Legal bases for processing
5.1. Processing is carried out on the basis of:
(a) performance of the contract with the User (clause 5, part 1, Article 6 of Federal Law No. 152-FZ) — to provide the Service;
(b) consent of the User (clause 1, part 1, Article 6 and Article 9 of Federal Law No. 152-FZ) — expressed through acceptance of the offer and separate consent to cross-border transfer;
(c) pursuit of the Operator’s legitimate interests (clause 7, part 1, Article 6) — as regards security, abuse detection and diagnostics;
(d) performance of statutory obligations imposed on the Operator (clause 2, part 1, Article 6) — as regards tax, accounting and fiscal compliance.
6. Two-tier data storage architecture
6.1. To comply with part 5, Article 18 of Federal Law No. 152-FZ, the Operator uses a two-tier architecture for processing personal data.
Russian tier (primary record and storage):
| Data | Infrastructure | Location |
|---|---|---|
| User registration data | Managed PostgreSQL | Russia |
| Subscription, payment, receipt data | Managed PostgreSQL | Russia |
| User consent records | Managed PostgreSQL | Russia |
Billing service and @wamagentsbot entry point | VPS in cloud | Russia |
| ”Telegram identifier ↔ internal user pseudonym” mapping | Managed PostgreSQL | Russia |
Primary recording, systematisation, accumulation, storage and refinement of personal data of citizens of the Russian Federation take place in databases located on the territory of the Russian Federation.
Foreign tier (Service execution):
Only pseudonymised information is processed in the foreign tier (bound to an internal user pseudonym, not the Telegram identifier or email), to the extent necessary for Service execution.
| Subprocessor / recipient | Role | Location |
|---|---|---|
| Anthropic, PBC | LLM provider (Claude) — transfer performed via the User’s OAuth Token | USA |
| Hetzner Online GmbH | Cloud infrastructure for running Containers | Germany |
| Telegram FZ-LLC | Messenger transport | UAE |
| JSC “T-Bank” (TIN 7710140679) | Acquiring, acceptance of bank payments | Russian Federation |
| LLC “CLOUDKASSIR” (TIN 7725364512) | Fiscal agent — generation of cashier’s receipts under 54-FZ | Russian Federation |
6.2. The current list of subprocessors and processing addresses is maintained at https://docs.magnets.tg/subprocessors.
7. Cross-border transfer of data
7.1. Cross-border transfer of personal data is performed in accordance with Article 12 of Federal Law No. 152-FZ.
7.2. Prior to the commencement of cross-border transfer, the Operator files a notification of cross-border transfer of personal data with the authorised body for the protection of the rights of personal-data subjects (Roskomnadzor). The details of the notification are listed at https://docs.magnets.tg/subprocessors.
7.3. Cross-border transfer of data is performed on the basis of the User’s separate consent, given during onboarding in @wamagentsbot, with a clear indication of the recipient countries and the purposes of the transfer.
7.4. Risk-mitigation measures:
(a) pseudonymisation — an internal user pseudonym is transferred to the foreign tier, not the Telegram identifier or any other directly identifying data;
(b) minimisation — email, name and real identifiers are not transferred to the foreign tier;
(c) encryption — transfer over TLS; volumes with user data in foreign infrastructure are encrypted at the filesystem level.
8. Retention periods
8.1. Account data and Container configuration are retained for the duration of the Subscription.
8.2. On cancellation (/cancel), Container data is destroyed at Container de-initialisation.
8.3. On account deletion (/delete), all records associated with the User are removed from the Operator’s systems, save for:
(a) fiscal and accounting data whose retention is required by the legislation of the Russian Federation (not less than 4 years — Article 23 of the Tax Code of the Russian Federation, Article 29 of Federal Law “On Accounting”);
(b) limited log records required to investigate security incidents — up to 90 days;
(c) data that has been irreversibly anonymised.
8.4. Backups are rotated on a cycle of no more than 30 days.
9. Personal-data protection measures
9.1. The Operator applies technical and organisational measures proportionate to the level of risk, including:
(a) per-User Container isolation using Linux namespaces with cap_drop: ALL, read_only: true, no-new-privileges: true, tmpfs-mounted home directory and non-root execution;
(b) volume encryption in foreign infrastructure (LUKS or equivalent);
(c) access control and least-privilege principle for the Operator’s authorised personnel;
(d) transport encryption (TLS) for API traffic;
(e) monitoring, log rotation and incident-response procedures;
(f) pseudonymisation of user identifiers in the foreign tier.
9.2. The Bot Token and OAuth Token are functional credentials and are treated as confidential information. The User remains responsible for their revocation (via BotFather or claude.ai) upon suspected compromise.
10. Rights of the personal-data subject
10.1. The User has the right:
(a) to obtain information about the processing of their personal data (Article 14 of Federal Law No. 152-FZ); (b) to request the refinement, blocking or destruction of personal data (Article 14); (c) to withdraw consent to the processing of personal data (Article 9); (d) to withdraw consent to cross-border transfer; (e) to appeal against the Operator’s actions before Roskomnadzor or in court (Article 17).
10.2. The Operator’s response time to a subject’s request is 10 business days from the moment of receipt of the request (Article 20 of Federal Law No. 152-FZ). Where necessary, the period may be extended, but by no more than 5 business days, with notice to the subject.
10.3. Requests are sent to we@magnet.tg.
10.4. Supervisory authority: Roskomnadzor — https://rkn.gov.ru.
11. Automated decision-making
11.1. The Operator does not use the User’s personal data to take automated decisions producing legal or similarly significant effects without the User’s involvement. Agent actions are performed under the User’s control (Section 7 of Part A).
12. Children
12.1. The Service is not directed to persons under 16 years of age. If the Operator becomes aware that the Service is being used by a person under 16, the relevant personal data will be deleted unless retention is required by law.
13. Amendments to the Privacy Policy
13.1. The Operator may update this Privacy Policy. Notice of material changes is given by the Operator in the manner of Section 15 of Part A.
Part C — Registration details and contacts
Provider (Operator): Individual Entrepreneur Silenkov Maxim Eduardovich TIN: 711613398109 OGRNIP: 310715428100134 Legal address: 368600, Russia, Republic of Dagestan, Derbent, Avtovokzalnaya St., 10 Settlement account: 40802810500001116454 with JSC “T-Bank” (BIC 044525974, TIN 7710140679, correspondent account 30101810145250000974)
General contact: we@magnet.tg
Personal-data enquiries: we@magnet.tg
Abuse / content-removal notices: we@magnet.tg
User support: the /support command in @wamagentsbot
Effective date: April 13, 2026 Last updated: April 21, 2026