Privacy Policy

1. Introduction

This Privacy Policy explains how Ethereum Classic Wallet handles information when you use the website and the desktop application. The purpose of this document is to clearly describe what data is — and is not — collected, how information is processed, and what responsibilities remain with the user.

Ethereum Classic Wallet is designed as a non-custodial, desktop-based wallet for the Ethereum Classic blockchain. The project does not operate user accounts, does not provide custodial services, and does not store funds or private keys on behalf of users. Because of this architecture, the wallet does not require most types of personal information that are commonly associated with online services.

This Privacy Policy applies to the official Ethereum Classic Wallet website, the downloadable desktop application, and related project resources maintained by the development team. It is intended to help users understand the privacy implications of using the wallet and interacting with the project.

By using the Ethereum Classic Wallet website or application, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with the practices described here, you should discontinue use of the website and the application.

This document is provided for transparency and informational purposes. It is not intended to replace personal responsibility for securing your device, managing your recovery information, or understanding how the Ethereum Classic blockchain operates.

2. Scope of This Policy

This Privacy Policy applies only to the official Ethereum Classic Wallet project and the services directly provided by it. This includes the official website, the downloadable desktop application, and related resources maintained by the project team.

The policy describes how information is handled when you interact with the Ethereum Classic Wallet website or use the desktop application to manage Ethereum Classic (ETC). It covers only the behavior of the wallet software itself and the project’s own infrastructure.

This Privacy Policy does not apply to third-party services, platforms, or tools that may be accessed through the wallet or the website. These include, but are not limited to, public RPC endpoints, blockchain explorers, node providers, mining pools, external documentation, community platforms, or any other external websites or services linked from the project.

When using the Ethereum Classic Wallet, your interactions with the Ethereum Classic blockchain occur directly on the network. Transactions, addresses, balances, and other blockchain-related data are processed by the decentralized Ethereum Classic network and may be visible publicly through blockchain explorers. The project does not control how blockchain data is stored, propagated, or displayed by third parties.

Additionally, this Privacy Policy does not govern the privacy practices of operating systems, hardware devices, internet service providers, or software environments used to run the wallet. Users are responsible for understanding and managing the privacy and security settings of their own devices and networks.

By using external services or third-party tools in connection with Ethereum Classic Wallet, you acknowledge that those services operate under their own privacy policies and terms. Ethereum Classic Wallet is not responsible for the data handling practices of third parties.

3. Information We Collect and Do Not Collect

Ethereum Classic Wallet is designed to operate without collecting personal or sensitive user information. The wallet does not require accounts, registration, or identity verification, and most functionality works without transmitting user data to the project.

To avoid ambiguity, this section clearly distinguishes between information that is not collected at all and information that may be processed locally as part of normal wallet operation.

Information We Do Not Collect

Ethereum Classic Wallet does not collect, store, or process the following types of information:

• personal identification data such as names, email addresses, phone numbers, or physical addresses
• account credentials or login information
• private keys, recovery phrases, or wallet passwords
• transaction signing data or cryptographic secrets
• financial information linked to real-world identity
• usage tracking, behavioral analytics, or profiling data

The project does not operate user accounts and does not maintain databases of user information.

Information Processed Locally on Your Device

Some information is created or processed locally on your device in order for the wallet to function. This information is not collected by the project and is not transmitted to project-controlled servers.

This may include:

• wallet addresses generated by the application
• locally stored encrypted key material
• transaction history retrieved from the Ethereum Classic network
• user preferences and application settings

All such data remains under the user’s control and is stored within the local application environment.

Network-Related Information

When using Ethereum Classic Wallet, the application communicates with the Ethereum Classic blockchain through network nodes. As a result:

• transaction data is broadcast to the public blockchain
• addresses and transaction details become publicly visible on the network
• network metadata may be handled by third-party node providers

Ethereum Classic Wallet does not control how blockchain data is stored or displayed by the network or external services.

Optional Website Interactions

The project website may process minimal technical information necessary for basic operation, such as standard web server logs. This information is not used for tracking, profiling, or identifying individual users.

4. Local Data Handling and Storage

Ethereum Classic Wallet is designed so that all wallet-related data is handled locally on the user’s device. The project does not operate backend systems for storing wallet data and does not have access to information created or stored by the application.

Local data handling is a core part of the wallet’s architecture. This means that key material, addresses, transaction history, and application settings are stored within the local environment of the operating system where the wallet is installed. The exact storage location and behavior depend on the platform (Windows, macOS, or Linux) and the system configuration.

Ethereum Classic Wallet does not transmit locally stored wallet data to project-controlled servers. Network communication is limited to interacting with the Ethereum Classic blockchain through network nodes for the purpose of retrieving public blockchain data and broadcasting transactions.

The persistence of local data depends on user actions. Removing the application, clearing application data, or resetting the operating system may result in the loss of locally stored information. The project does not maintain backups of user data and cannot restore access if local data is removed without a recovery phrase.

Users are responsible for securing their devices, managing backups, and protecting access to their local environment. This includes safeguarding recovery phrases, maintaining system security, and understanding how local storage behaves on their operating system.

Because all critical data is handled locally, the privacy and security of wallet usage are directly influenced by the user’s device, operating system settings, and network environment.

5. Network and Third-Party Services

Ethereum Classic Wallet interacts with external networks and services in order to function correctly. This section explains how those interactions work and clarifies the project’s role and limitations when third-party services are involved.

Interaction with the Ethereum Classic Network

When using the wallet, transactions and address data are communicated directly with the Ethereum Classic blockchain. As a result:

• transaction data is broadcast to the public Ethereum Classic network
• addresses, balances, and transaction history are publicly visible on the blockchain
• blockchain data can be viewed by anyone through public explorers

Ethereum Classic Wallet does not control the Ethereum Classic network and cannot alter how blockchain data is stored, validated, or displayed.

Public RPC Endpoints

To communicate with the blockchain, the wallet may connect to public RPC endpoints operated by third parties. These endpoints are used to:

• retrieve blockchain data such as balances and transaction status
• broadcast signed transactions to the network

Public RPC services are operated independently and may differ in availability, performance, and data retention policies. Ethereum Classic Wallet does not operate or control these services.

Blockchain Explorers

The wallet and website may link to external blockchain explorers to allow users to view transactions or blocks in more detail. These explorers are third-party services with their own privacy policies and terms of use.

Using a blockchain explorer may expose transaction details or metadata according to the explorer’s practices.

6. Cookies and Tracking

Ethereum Classic Wallet is designed to function without user tracking, behavioral analysis, or profiling. The project does not use tracking technologies to monitor how individuals use the wallet application or to build usage patterns linked to specific users.

The desktop wallet application does not use cookies, analytics frameworks, tracking scripts, or similar technologies. No usage data, identifiers, or behavioral information is collected or transmitted from the application to the project or to third parties. The wallet operates entirely without telemetry or background monitoring.

The official website may use a limited number of essential cookies that are required for basic functionality, such as enabling navigation between pages or maintaining simple session-related preferences. These cookies are not used to identify users, track activity across websites, or support advertising or analytics.

Ethereum Classic Wallet does not use the following technologies on its website or within the application:

• advertising or marketing cookies
• third-party analytics services
• behavioral tracking or fingerprinting techniques

If the website includes links to external services, documentation platforms, or community resources, those third-party websites may apply their own cookies or tracking mechanisms. Any such behavior is governed by the privacy policies of the respective third parties and is outside the control of the Ethereum Classic Wallet project.

Users who are concerned about cookies or tracking are encouraged to review their browser and operating system settings, as well as the privacy practices of any external services they choose to access through links provided on the website.

7. Data Security

Ethereum Classic Wallet is designed with a security model that minimizes data exposure by limiting what information exists outside the user’s local environment. The project does not operate centralized systems for storing wallet data and does not have access to user funds, private keys, or recovery information.

Security in Ethereum Classic Wallet is primarily achieved through architectural decisions rather than through centralized controls. By keeping wallet data local and avoiding user accounts, the project reduces the amount of sensitive information that could be exposed through external systems.

All sensitive wallet data is handled on the user’s device. This includes key material, address information, and transaction signing data. Network communication is limited to what is required to interact with the Ethereum Classic blockchain, such as retrieving public blockchain data and broadcasting signed transactions.

The project does not claim to provide absolute or guaranteed security. The safety of wallet usage depends on multiple factors, including the user’s operating system, device security, network environment, and personal practices. Ethereum Classic Wallet does not monitor devices or enforce security policies at the system level.

Key aspects of the project’s security approach include:

• avoiding centralized storage of wallet data
• limiting network communication to blockchain interaction
• relying on open and inspectable code rather than hidden mechanisms

Users are responsible for maintaining the security of their devices, including applying system updates, using trusted software sources, and protecting access to their local environment. Loss of a device, exposure of recovery information, or compromise of the operating system may result in loss of access to funds.

8. User Responsibility

Ethereum Classic Wallet is a non-custodial application, which means users retain full control over their wallets and how they are used. As a result, certain responsibilities remain entirely with the user and are not handled by the project or its contributors.

The project does not manage accounts, recover access, or intervene in transactions. Users are expected to understand and manage their interaction with the wallet and the Ethereum Classic network.

Device and Environment Security

Users are responsible for maintaining the security of the device on which the wallet is installed. This includes:

• keeping the operating system and software up to date
• using trusted sources when installing applications
• protecting the device from unauthorized physical or remote access
• understanding how local storage behaves on their system

Compromised devices may expose locally stored data and affect wallet security.

Backup and Recovery Management

The wallet relies on user-managed backups for recovery. Users are responsible for:

• securely storing recovery phrases offline
• ensuring backups are not shared or exposed
• understanding that loss of recovery information may result in permanent loss of access

The project does not store backup data and cannot restore wallets on behalf of users.

Transaction Review and Network Interaction

All transactions sent through the wallet are broadcast directly to the Ethereum Classic network. Users are responsible for:

• reviewing transaction details before submission
• selecting appropriate network fees
• understanding that confirmed transactions cannot be reversed

Ethereum Classic Wallet does not control transaction confirmation or network behavior.

Use of Third-Party Services

When choosing to interact with third-party services such as public RPC endpoints, blockchain explorers, or external platforms, users are responsible for:

• reviewing the privacy and security practices of those services
• understanding that third-party behavior is outside project control
• making informed decisions about external tools they choose to use

9. Changes to This Policy

Ethereum Classic Wallet may update this Privacy Policy from time to time to reflect changes in the project, improvements to the wallet, or updates to applicable practices. Any changes are intended to improve clarity, accuracy, or alignment with how the project operates.

When updates are made, the revised Privacy Policy will be published on the official website. The updated version will apply from the date it is posted. Continued use of the website or the wallet after changes take effect indicates acceptance of the updated policy.

The project does not provide individual notifications for policy updates. Users are encouraged to review this Privacy Policy periodically to stay informed about how information is handled.

Changes to this policy will not alter the fundamental design of the wallet, including its non-custodial nature, local data handling model, or lack of user data collection. Any updates will remain consistent with the principles described throughout this document.