Terms of Service

Last updated: August 18, 2025

These Terms of Service (“Terms”) govern your access to and use of Eclipse EQ (the “Service”), including our Telegram management bot and the encrypted relay infrastructure, access profiles and software configurations we provide. By accessing or using the Service, you agree to these Terms.

Plain-language summary: the Service supplies secure, encrypted traffic relay for connection stability, privacy and integrity — it is not intended for peer‑to‑peer distribution or unlawful activity.

1. Who we are

Provider / Data Controller: Eclipse EQ
Support: https://t.me/mademix
Official bot: @eclipseeq_bot

2. Eligibility

You must be at least 18 years old to use the Service. If you are under 18, you may use the Service only with the consent of a legal guardian.

3. The Service and Acceptable Use

3.1. The Service provides encrypted traffic relay and access profiles to help maintain connection stability, confidentiality and integrity.

3.2. You must comply with applicable law. You are solely responsible for the legality of the content you access and transmit via the Service.

3.3. Strictly prohibited: peer‑to‑peer file distribution protocols (e.g., BitTorrent and similar) through the Service, regardless of content type. Attempts to circumvent monitoring, chaining other proxies or relay systems to mask P2P use, or other abuse may lead to immediate suspension.

3.4. Also prohibited: spam, port scanning, DDoS/DoS, credential stuffing, brute‑force attacks, unlawful distribution of copyrighted material, dissemination of malware, illegal content, harassment or incitement to violence.

3.5. Keep subscription credentials, access profiles, keys and device slots confidential; do not share them with third parties.

4. Accounts, Bot and Security

4.1. Some features require a Telegram account to interact with our bot @eclipseeq_bot. You are responsible for securing your devices and Telegram account.

4.2. We may impose reasonable technical limits (e.g., device count, bandwidth management, abuse prevention).

4.3. To protect the network and other users, we may temporarily block or rate‑limit connections.

5. Subscriptions, Renewal and Cancellation

5.1. Paid plans are billed in advance. If your plan includes auto‑renewal, you can cancel it no later than 24 hours before the next billing date to avoid further charges.

5.2. Refunds.

• Accidental overpayments: contact support for correction.
• Voluntary cancellation of an active plan: 50% refund of the amount paid.
• No refunds if the Service has been used for more than 24 hours after purchase.
• No refunds in case of suspension/termination for serious violations (e.g., P2P use, attacks, abuse).

5.3. Refunds are processed to the original payment method within 14 business days of approval.

6. Availability and Disclaimers

6.1. We strive for high availability but do not guarantee uninterrupted access to third‑party resources (including resources restricted by government action).

6.2. The Service is provided “as is” and “as available” without warranties of any kind, to the maximum extent permitted by law.

6.3. We are not liable for losses arising from factors outside our reasonable control.

7. Suspension and Termination

7.1. We may suspend or terminate your access for violations of these Terms or to protect the network.

7.2. For non‑urgent matters we normally provide 7 days’ notice; in serious cases (e.g., spam, DDoS, P2P), we may act immediately without prior notice.

7.3. Upon termination, you must stop using any configurations, profiles or keys obtained from the Service.

8. Conduct towards Support

Harassment, insults, threats, hate speech or abusive behavior towards users or support staff are prohibited and may result in temporary or permanent bans.

9. Changes to the Terms

We may update these Terms from time to time. Updates take effect when posted in the official channel/bot. Your continued use after changes means you accept the revised Terms.

10. Governing Law and Dispute Resolution

These Terms are governed by the laws of the Russian Federation. Disputes will be resolved exclusively by the courts of the Russian Federation.

11. Miscellaneous

Severability: if any provision is invalid, the remainder remains in effect. Assignment: you may not assign your rights; we may assign as part of a reorganization or sale. Entire agreement: these Terms constitute the entire agreement regarding the Service and supersede prior understandings.

Privacy Policy

Last updated: August 18, 2025

This Privacy Policy explains how Eclipse EQ (the “Service”) processes information when you use our Telegram management bot, access profiles and encrypted relay infrastructure.

We design the Service with privacy in mind: we do not inspect the content of relayed payloads, and we retain minimal technical data for limited periods needed to operate the network.

1. Who we are (Data Controller)

Controller: Eclipse EQ (“we”, “us”)
Support: https://t.me/mademix
Official bot: @eclipseeq_bot

2. Scope

• the Telegram bot you use to manage subscriptions and receive access profiles;
• the encrypted relay infrastructure (gateways and authentication);
• any related web pages we operate.

3. Data we process

3.1. Account and communications data

• Telegram user ID, username and language, basic support messages, subscription status;
• contact details you provide (e.g., email) when requesting support.

3.2. Payment data

• We receive payment confirmations/metadata from our payment provider (amount, time, transaction ID, status).
• We do not store full card or wallet details; those are processed by the third‑party payment processor.

3.3. Technical and telemetry data (minimal)

• IP address, timestamps, device or app identifiers necessary to establish and maintain sessions, and basic performance metrics.
• No content inspection and no activity logs of the destinations and services you access through the relay infrastructure.

3.4. Retention

• Connection metadata is kept for no longer than 24 hours unless needed to investigate abuse or ensure service stability.
• Billing records are retained for periods required by tax and accounting laws.
• Support messages are retained as needed to resolve your request.

We do not intentionally collect information from children; the Service is for users 18+.

4. Purposes and legal bases (where applicable)

• Provide the Service (set up connections, authenticate sessions, route traffic): performance of a contract.
• Payments and fraud prevention: performance of a contract and our legitimate interests.
• Security and abuse prevention (e.g., blocking DDoS, preventing P2P use, protecting network integrity): legitimate interests.
• Customer support and communications: performance of a contract / legitimate interests.
• Compliance with legal obligations (accounting, lawful requests from authorities where applicable): legal obligation.
• Marketing communications (if any): consent; you may withdraw consent at any time.

5. Prohibition on P2P

To preserve network performance and comply with partner requirements, peer‑to‑peer protocols are prohibited and may trigger automated blocking. See the Terms of Service for details.

6. Third‑party recipients

• Payment processors: we share transaction IDs and amounts to confirm purchases and process refunds.
• Infrastructure providers (e.g., data centers): process technical metadata needed to deliver the Service.
• Customer support tools (if used): limited to the information you provide for support.

We do not sell personal data.

7. International transfers

Where data leaves your country, we rely on appropriate safeguards (e.g., Standard Contractual Clauses) or equivalent mechanisms as required by law. You can contact support for a description of applicable safeguards.

8. Your rights

Depending on your jurisdiction, you may have the right to access, rectify, erase, restrict or object to processing, request portability, and withdraw consent where processing is based on consent. We respond to verified requests within applicable timeframes. You may also lodge a complaint with your local supervisory authority where available.

9. Data security

We apply technical and organizational measures such as encryption in transit, access controls, key rotation and least‑privilege policies. No method of transmission or storage is 100% secure, but we work to protect your information.

10. Cookies and similar technologies

If you use only the Telegram bot and access profiles, we do not use cookies. Our websites may use strictly necessary cookies and minimal analytics; details (if any) will be shown on those sites.

11. How long we keep data

We keep personal data only as long as necessary for the purposes above, and then delete or anonymize it. See section 3.4 for specific retention windows (e.g., 24 hours for connection metadata).

12. Changes to this Policy

We may update this Policy from time to time. We will post changes via the bot/channel and update the “Last updated” date.

13. Contact

Support: https://t.me/mademix • Official bot: @eclipseeq_bot