Security Policy

Last Updated: 23rd May 2025

  • Home
  • Security Policy

Security Policy

Last Updated: 23rd May 2025

  • Home
  • Security Policy

1. Introduction

2. Data Protection Measures

Encryption

  • In Transit: All data exchanged between your device and our servers is encrypted using TLS 1.2 or higher.
  • At Rest: Sensitive information (e.g., API keys, payment details) is encrypted using AES-256.
  • Passwords: Passwords are securely hashed and salted using bcrypt or an equivalent algorithm.

Infrastructure Security

  • Cloud Hosting: We host data on secure cloud platforms such as AWS, Google Cloud, or Microsoft Azure, utilizing enterprise-grade firewalls, IDS, and DDoS protection.
  • Network Segmentation: Critical components (e.g., databases, payment processors) are isolated from public-facing systems.
  • Regular Patching: Systems are automatically updated to address known vulnerabilities promptly.

3. Vulnerability Management

Penetration Testing

  • Internal Scans: We conduct weekly vulnerability scans using tools like Nessus or Qualys.

Code Security

  • Secure Development: Code is subjected to static and dynamic analysis (SAST/DAST) and peer reviews before deployment.
  • Dependency Monitoring: We use automated tools (e.g., Snyk, Dependabot) to identify vulnerabilities in third-party libraries.

4. Incident Response Plan

Detection & Reporting

  • 24/7 Monitoring: Our SIEM tools detect anomalies such as unauthorized access or data exfiltration.
  • User Reporting: Please report any security concerns to sales@magictradebot.com with "SECURITY INCIDENT" in the subject line.

Response Workflow

  • Containment: Affected systems are isolated to prevent further impact.
  • Investigation: We identify the root cause, scope, and consequences of the incident.
  • Notification: Users are notified within 72 hours if a breach poses a risk to their rights (in accordance with GDPR/CCPA).
  • Remediation: We address vulnerabilities, reset compromised credentials, and restore data from backups if required.
  • Post-Mortem: We document lessons learned and update our security protocols accordingly.

5. Third-Party Risk Management

  • Vendor Assessments: We only work with vendors (e.g., Stripe, AWS) who meet recognized security standards such as ISO 27001 or SOC 2.
  • API Security: Exchange integrations use OAuth 2.0 or HMAC-signed requests for secure communication.
  • Data Sharing: Third parties are contractually required to protect user data and are prohibited from unauthorized usage.

6. User Responsibilities

  • Account Security: Use strong, unique passwords and enable multi-factor authentication (MFA) whenever possible.
  • API Key Protection: Never share your exchange API keys with anyone—including us. We never request them and do not require access. In self-hosted environments, you are responsible for securing your own keys, data, and server infrastructure.
  • Phishing Awareness: Report any suspicious emails claiming to be from MagicTradeBot to sales@magictradebot.com.

7. Compliance & Audits

  • Annual Audits: We undergo regular independent audits to ensure compliance with GDPR, CCPA, and other relevant regulations.
  • Regulatory Disclosures: We cooperate fully with law enforcement and regulatory authorities as legally required.

8. Data Retention & Deletion

  • Retention Period: We retain user data only as long as necessary for service provision and compliance purposes.
  • Secure Deletion: Upon request or account closure, data is permanently erased following NIST 800-88 standards.

9. Policy Updates

10. Contact Us