Privacy Policy
Effective date: May 14, 2026. This policy explains what data nodevera collects to operate customer accounts, payments, support and API access.
Data we collect
- Account data such as email address, display name, registration IP address and authenticator setup status.
- Service data such as API client ID, masked API key metadata, IP allowlists, plan, quota, usage and service expiration.
- Billing data such as order ID, plan, network, amount, transaction hash, payment status and operational notes.
- Support data such as contact details, company, topic, message content and processing status.
- Technical logs such as request path, status code, remote address, error class and timing used for security and monitoring.
How data is used
Data is used to authenticate users, prevent abuse, activate plans, verify payments, enforce quotas, troubleshoot API access, respond to support requests, maintain security logs and improve operational reliability.
Security
Passwords are stored as salted hashes. Login uses authenticator verification. Customer API access is protected by API keys and IP allowlists. Sensitive operational data should still be treated as confidential by customers and administrators.
Sharing
nodevera may send transaction identifiers to blockchain RPC providers or explorers for verification. Operational notifications may be sent to configured Telegram administrators. Data may also be disclosed when required to address abuse, fraud, legal requests or security incidents.
Retention
Account, order and support records are retained for operational history, dispute review, abuse prevention and service continuity. Test records may be deleted by operations staff during pre-production testing.
Your choices
You may request account review, correction or deletion through the support form. Some records may be retained where needed for security, billing, fraud prevention or legal reasons.