Privacy and data protection
Our defence-in-depth security model, designed to protect your data, services, and endpoints.
Endpoint defences
Allowed origins and tokens. Browser apps use allowed origins. Backend services use a secret token.
Rate limiting. Based on IP address and other factors. See Rate and connection limits.
Traffic filtering. Malformed requests are rejected before they reach the node software:
Unsupported method or path:
405Wrong content type:
415WebSocket version other than 13:
426Request body too large:
413JSON that doesn't parse:
-32700
Client filtering. Requests without a token from known non-browser clients are rejected. Requests with a token skip this check.
DDoS protection
You don't need Cloudflare or another commercial provider in front of your endpoint. See Proxying.
Internal security posture
Access
Permissions. Centralised identity and access management, with least-privilege access.
MFA. Required wherever a service supports it.
Hardware keys. Required for privileged staff accounts.
SSO. Staff sign in through company SSO wherever a service supports it.
SSH. Access to servers is restricted to authenticated staff.
Network
Internal traffic. Runs over a private encrypted network by default.
Host firewalls. Follow a minimal-exposure policy.
Encryption in transit. HTTPS connections are encrypted.
Systems
Work devices. Required to use full disk encryption and antivirus software, and a VPN on untrusted networks.
Security patching. Servers install security updates automatically every day.
Vulnerability monitoring. Server packages are monitored for known vulnerabilities (CVEs).
Personnel
Onboarding. Formal onboarding with gradual access provisioning.
Offboarding. A documented offboarding procedure revokes access.
Training. Regular security awareness training.
Audit and incident response
Audits. Daily automated security audits on all hosts.
Alerting. Critical alerts page the on-call team 24/7.
Security reports. Emails to security@triton.one page the on-call engineer.
Incident response. Documented security incident response and disaster recovery plans.
Data privacy
Triton handles customer data in compliance with GDPR and equivalent regulations.
Customer data we process
Validator node identity keys for customers running validators on our infrastructure
RPC service logs generated by user interaction with endpoints
Account and billing information required for invoicing and account management
How we protect it
Validator keys. Never stored or transmitted unencrypted. Decrypted only in process memory while actively in use.
Billing details. Card numbers and similar sensitive payment info are never stored on Triton systems. Billing is handled entirely by separate, dedicated, compliant third-party processors.
RPC log retention and privacy levels
Shared services. Logs collected solely for abuse prevention and operational stability. Triton does not identify or de-anonymise individual end users. Retention: 4 weeks.
Dedicated services. Customers choose the policy that fits their legal or privacy requirements:
Max privacy
No request parameters or payloads logged.
Highest privacy, but limits some abuse-detection capability. Required for any shared infrastructure components.
Enhanced privacy (default)
Method parameters may be logged, but the signer of a transaction cannot be linked to the originating IP.
Balance of operational insight and user privacy.
GDPR privacy
All parameters may be logged for technical support, legal, or compliance reasons.
Fully GDPR-compliant handling.
Abuse-mitigation measures
Earlier connection drops for repeat offenders
What counts. Repeated
403responses from one source IP.Over the limit. Triton rejects new connections from that IP and drops its requests without a response.
In your logs. First
403errors, then network-level failures ("network connection failed" or similar) instead of an HTTP error.Fix. Check that your token is correct and enabled, that your allowed origins include the requesting origin, and that your organization is active in the customer dashboard.
After the fix. Back off for at least one minute.
Stricter filters on tokenless backend traffic
Tokenless backend requests. Requests without a token that appear to come from a backend environment can get
403.Backend services. Send a token on every request.
Allowed origins. For browser apps only. A backend service that relies on allowed origins instead of a token is likely to be blocked.
Disabled tokens. A disabled token, or a token of an inactive organization, counts as no token.
Contact
General security or privacy questions: contact support by clicking the chat icon in the bottom right of your customer dashboard
Urgent security reports: security@triton.one
What's next
Contact support by clicking the chat icon in your customer dashboard Sales questions? Contact us AI agent? Read llms.txt Follow updates: Blog · X · YouTube · Telegram · GitHub
Last updated