ETCMCv2 VPN Client – Data Collection Policy

ETCMCv2 VPN Client – Data Collection Policy

Last updated: March 2, 2026

The ETCMCv2 VPN Client is designed with privacy and transparency in mind. This Data Collection Policy explains what information may be collected when using the ETCMCv2 VPN software, how that information is used, and the limited circumstances in which it may be shared.

Our goal is to design ETCMCv2 in a way that minimizes data collection, protects user privacy, and ensures that users remain in control of their own infrastructure.

1) Overview

ETCMCv2 is software that allows individuals or organizations to run their own VPN infrastructure. The ETCMCv2 development team does not operate VPN servers on behalf of users and does not route or inspect user traffic.

As a result:
  • We do not collect browsing history
  • We do not log VPN traffic
  • We do not inspect or store transmitted content
  • We do not track individual users
  • We do not require accounts to use the ETCMCv2 VPN client

Server operators are responsible for choosing where and how their infrastructure is hosted.

2) Information We Do Not Collect

The ETCMCv2 software does not collect or store:

  • Websites you visit
  • Content of communications
  • DNS queries
  • VPN traffic logs
  • IP addresses of end users connecting to servers
  • Account credentials for cloud providers
  • Payment or billing information

If you host your server using a third-party infrastructure provider, any information you provide to that provider is governed solely by that provider’s privacy policy.

3) Information Collected Automatically

ETCMCv2 collects only minimal technical information necessary for maintaining software stability and security.

Server IP during update checks

When a server checks for software updates, the server IP address may be visible to the software distribution infrastructure. This may reveal:

  • The hosting provider
  • The approximate geographic region of the server

This information cannot identify individual users or devices connected to the server.

Crash and diagnostic reports

If the application encounters an error or crash, limited diagnostic information may be generated to help identify and resolve technical issues.

Examples of diagnostic data:
  • Application version
  • Operating system name and version
  • Date and time of the error
  • Recent application events
  • Device or system architecture

This diagnostic data never includes VPN traffic or communication content.

4) Optional Anonymous Metrics

Server administrators may optionally enable anonymous usage metrics to help improve the ETCMCv2 software.

Examples of aggregated metrics:
  • Total bytes transferred
  • Connection duration statistics
  • Feature usage statistics
  • Country-level traffic origin
Metric sharing is disabled by default and can be enabled or disabled at any time.

These metrics are anonymous and aggregated. They are not linked to user identities, email addresses, or device identifiers.

5) Feedback Submissions

Users may voluntarily submit feedback through ETCMCv2 tools or community channels.

When submitting feedback, you may optionally provide an email address if you wish to receive a response. Providing personal information is never required.

6) Data Security

We apply industry-standard security practices when handling the limited technical information associated with ETCMCv2.

  • Encrypted transmission (HTTPS)
  • Restricted access controls
  • Minimal data retention
  • Principle of least privilege

We do not sell, rent, or monetize user data.

7) Data Retention

Any collected technical data is retained only for as long as necessary to:

  • Maintain software functionality
  • Diagnose and resolve technical issues
  • Generate aggregated, non-identifying statistics

Data that is no longer needed is periodically deleted.

8) Changes to This Policy

If material changes are made to this Data Collection Policy, the “Last updated” date will be modified and the updated version will be published.

9) Contact

If you have questions regarding privacy, data practices, or security in ETCMCv2, please contact the development team.

Email: [email protected]