Security Policy

Security is a core priority at Teron. We take a straightforward approach to protecting our platform, your data, and the smart contracts deployed through our service. This document outlines our security practices and how you can help.

1. Smart Contract Security

Every token deployed through Teron uses a standard BEP-20 smart contract template. The source code is straightforward, does not include proxy patterns or upgradability, and follows established Solidity best practices.

We compile contracts using a pinned compiler version (Solidity 0.8.20) with consistent optimization settings. When you purchase contract verification, the exact source code is published to BscScan so anyone can inspect it.

Our contracts do not include hidden mint functions, admin backdoors, pause mechanisms, or blacklist features unless explicitly chosen during token configuration. What you see in the verified source is exactly what runs on the blockchain.

2. Platform Infrastructure

The Teron web application is served over HTTPS with TLS encryption for all data in transit. We use secure, managed database services with encryption at rest. Access to production systems is restricted and protected by multi-factor authentication.

We follow the principle of least privilege for all internal systems. Sensitive configuration values such as API keys and database credentials are stored as environment variables, not in source code.

3. Authentication

Teron uses Web3 wallet-based authentication. There are no passwords stored on our servers. Authentication is handled through cryptographic signature verification using your wallet.

Session tokens are scoped and expire after inactivity. Admin access requires specific wallet addresses configured in our environment and verified against our database.

4. Data Protection

We collect only the data necessary to provide our services. Personal information is stored in encrypted databases with access controls. We do not sell user data to third parties.

For complete details on what data we collect and how we handle it, see our Privacy Policy.

5. Key Management

Teron never has access to your private keys. All blockchain transactions are signed locally in your Web3 wallet. Your private keys never leave your device.

Premium service payments are sent to a cold wallet address that is not connected to any online systems. This reduces the risk of fund compromise.

6. Vulnerability Reporting

If you discover a security vulnerability in the Teron platform, we encourage you to report it responsibly. We take all reports seriously and will investigate promptly.

When reporting a vulnerability, please include:

• A clear description of the vulnerability and its potential impact
• Steps to reproduce the issue
• Any relevant screenshots, logs, or proof of concept

Please do not publicly disclose vulnerabilities before giving us reasonable time to investigate and patch the issue. We aim to acknowledge reports within 48 hours and provide updates on remediation progress.

Send vulnerability reports to: teronproject@gmail.com

7. Incident Response

In the event of a security incident, we will assess the scope and severity, contain the issue, notify affected users where appropriate, and publish a transparent post-incident report. We believe clear communication during security events builds trust.

8. User Responsibilities

Platform security is a shared responsibility. We recommend the following best practices:

• Use a hardware wallet or a well-maintained software wallet
• Never share your private keys or seed phrases with anyone
• Verify you are on teron.io before connecting your wallet
• Review all transaction details in your wallet before signing
• Keep your browser and wallet software updated

9. Contact

For general security questions, contact us at:

Email: teronproject@gmail.com