How We Protect Your API Keys

Protecting your account security is our top priority. This article explains how we protect your Cloudflare Token using advanced encryption technologies.
Dual-Layer Encryption Protection
On the OneClick platform, we employ a dual encryption mechanism to ensure your Token security:
RSA-OAEP Asymmetric Encryption Secures Token transmission and storage
AES-GCM Symmetric Encryption Provides an additional protection layer for system private keys
This mechanism ensures your Token's security even in extreme cases of database breaches.
Encryption System Specifications
Encryption Type | Parameters | Usage |
---|---|---|
AES-GCM | • 256-bit key length • 12-byte IV | Symmetric encryption, protects system private keys |
RSA-OAEP | • 2048-bit key length • SHA-256 hash | Asymmetric encryption, protects user Tokens |
Encryption Process Details
Security Design Features
Data Security Flow
1. Server-side Flow
2. Client-side Flow
3. Access Flow
Security Measures
We strictly follow encryption best practices to ensure system security meets the highest standards. All encryption operations are implemented using the Web Crypto API.
Best Practices and Support
🎯 Core Measures
- Real-time Monitoring — Monitor API access patterns, detect anomalies promptly
- Security Audit — Complete operation logs, regular security reviews
- Continuous Assessment — Regular security assessments and penetration testing
📞 Security Support
If you discover any security issues, please contact us immediately:
We commit to responding to all security-related reports within 24 hours