← Back to Legal Documentation
PRIVACY POLICY
Titan Protocol — Genesis Key Data Practices
Last Updated: March 7, 2026
This public policy summarizes how Titan Protocol handles data related to the Genesis Key concession, Titan Node Software, and the associated operating environment.
Data Categories
- Wallet addresses and on-chain activity relevant to issuance, screening, and node operation.
- Communication data from designated operator channels.
- Operator profile inputs used for onboarding, calibration, and support.
- Node telemetry, session signals, and technical access data used for security and operations.
Why Titan Processes Data
- Operate the network and maintain node eligibility.
- Support onboarding, calibration, service notifications, and operator assistance.
- Protect the network through security monitoring, anti-piracy controls, and anomaly detection.
- Meet compliance and legal obligations applicable to the concession framework.
- Improve system resilience, intelligence, and operational quality.
Monitoring and Security
Titan uses monitoring that is proportionate to network protection and service integrity. This may include session patterns, request behavior, software integrity checks, and operational telemetry needed to secure the network and enforce the governing documents.
Sharing and Retention
Titan does not sell personal data. Data may be shared with infrastructure providers, service providers, and legal authorities where necessary for operations, compliance, or lawful process. Retention follows operational, security, compliance, and contractual needs, while blockchain records remain independently immutable.
Operator Rights
- Request access to data Titan controls about the operator relationship.
- Request correction of inaccurate records where feasible.
- Request deletion where legally and technically possible.
- Request communication changes through the designated operator channel.
International Handling
Where operations require cross-border processing, Titan uses service-provider and contractual safeguards appropriate to the applicable data protection context. The specific controller identity and formal contact path are set out in the individual Concession Agreement.