We collect session and behaviour data to improve your learning experience on Algobasecamp. No data is sold to third parties.

Your privacy choices

Do not sell my data

Masterclasses in trading psychology and discipline - built for traders who trade with intention.

Security Policy

Last updated: October 29, 2026

Algobasecamp is committed to protecting the security of its platform, systems, and the data entrusted to us by our users. This Security Policy describes the technical and organizational measures we implement to safeguard information and maintain the integrity of our services available at algobasecamp.com.


1. Scope

This policy applies to all systems, infrastructure, applications, and data managed by Algobasecamp in connection with the delivery of its online masterclass platform. It covers all users, staff, contractors, and third parties who interact with our services.


2. Data Protection and Encryption

2.1 Data in Transit

All data transmitted between users and our platform is encrypted using Transport Layer Security (TLS). We enforce current, industry-accepted cipher suites and disable deprecated protocols to prevent interception or tampering.

2.2 Data at Rest

Sensitive data stored on our systems is encrypted using strong, widely accepted encryption standards. Encryption keys are managed through dedicated key management processes with appropriate access controls and rotation schedules.

2.3 Database Security

Databases are isolated from public networks. Access is restricted to authorized systems and personnel only, using authenticated and encrypted connections.


3. Access Control

3.1 Principle of Least Privilege

Access to systems, data, and administrative functions is granted on a need-to-know basis. Users and internal personnel are provided only the minimum level of access required to perform their responsibilities.

3.2 Authentication

We require strong authentication mechanisms for access to sensitive systems. Multi-factor authentication (MFA) is enforced for administrative and privileged accounts. Passwords are stored using industry-standard hashing algorithms.

3.3 Access Reviews

Access rights are reviewed periodically. Access is promptly revoked when it is no longer required or when personnel leave the organization.


4. Infrastructure Security

4.1 Network Security

Our infrastructure is protected by firewalls, network segmentation, and intrusion detection mechanisms. Traffic is monitored and filtered to identify and block unauthorized access attempts.

4.2 Vulnerability Management

We conduct regular vulnerability assessments and apply security patches in a timely manner. Critical vulnerabilities are prioritized and remediated as quickly as operationally possible.

4.3 Secure Configuration

Servers, services, and applications are configured according to security hardening guidelines. Default credentials are changed, unnecessary services are disabled, and configurations are reviewed regularly.

4.4 Cloud and Hosting Security

Our platform relies on reputable cloud infrastructure providers that maintain recognized security certifications and compliance programs. We apply additional security controls at the application and configuration level on top of provider defaults.


5. Application Security

5.1 Secure Development Practices

Security is incorporated throughout the software development lifecycle. Code changes are reviewed for security implications before deployment. We follow established secure coding guidelines to prevent common vulnerabilities.

5.2 Input Validation and Output Encoding

All user-supplied input is validated and sanitized. Output encoding is applied to prevent injection attacks, including cross-site scripting (XSS) and SQL injection.

5.3 Dependency Management

Third-party libraries and components are monitored for known vulnerabilities. Outdated or vulnerable dependencies are updated or replaced in a timely manner.

5.4 Session Management

User sessions are managed using secure, randomly generated tokens. Sessions expire after periods of inactivity and are invalidated upon logout.


6. Monitoring and Logging

We maintain logs of access and activity across critical systems. Logs are protected against unauthorized modification and are retained for a defined period to support security investigations. Automated monitoring and alerting systems are in place to detect anomalous behavior and potential security incidents.


7. Incident Response

We maintain an incident response process to detect, contain, investigate, and recover from security incidents. In the event of a confirmed security breach affecting user data, we will notify affected users within a reasonable timeframe consistent with our obligations, providing relevant details and recommended actions.

To report a suspected security incident or concern, contact us at:


8. Responsible Disclosure

We welcome responsible reporting of potential security vulnerabilities in our platform. If you believe you have discovered a security issue, please contact us at help@algobasecamp.com with a detailed description. We ask that you:

We will acknowledge receipt of your report and work to resolve confirmed issues in a timely manner.


9. Third-Party Services

We may engage third-party service providers to support the delivery of our platform. These providers are evaluated for their security practices and are required to handle data in a manner consistent with our security standards. We do not sell user data to third parties.


10. Business Continuity and Backups

Critical data is backed up regularly. Backups are encrypted and stored in a manner that supports recovery in the event of data loss, corruption, or system failure. Recovery procedures are tested periodically to verify their effectiveness.


11. Physical Security

Where Algobasecamp maintains or operates physical infrastructure, access to those facilities is restricted to authorized personnel. We rely primarily on reputable cloud and data center providers whose physical security controls are subject to independent audits and certifications.


12. Employee and Contractor Security

Personnel with access to systems or user data are required to follow security policies and complete security awareness training. Confidentiality obligations are established through contractual agreements. Access is revoked promptly upon termination of employment or engagement.


13. Changes to This Policy

We may update this Security Policy from time to time to reflect changes in our practices, technology, or applicable standards. The most current version will always be available on our website. We encourage users to review this policy periodically. Continued use of our platform following any update constitutes acceptance of the revised policy.


14. Contact

For questions or concerns regarding this Security Policy, please contact us: