Legal

Privacy policy

What this deployment stores, why it is stored, and how account holders can request changes.

Information we collect

  • Account information: username, email address, password hash (bcrypt), membership type, membership expiry and account status.
  • License information: license key, EA product, MT5 account number, broker server, EA version, license status and request timestamps.
  • Support messages: the name, email address, subject and message you submit through the contact form.
  • Operational records: IP address and timestamp for administrative actions and license verification attempts recorded in the audit log.

How we use your information

  • Account authentication and access control.
  • License activation, verification and revocation.
  • Product delivery and membership management.
  • Administrator communication and support.
  • Security monitoring and abuse prevention.

Information we do not collect

  • Card or bank details. This website does not operate a checkout or payment flow.
  • MT5 trading positions, trade history or broker account balances.
  • Government identification numbers or social security numbers.
  • Browsing history outside this website.

Cookies and sessions

The site uses a single session cookie to keep you signed in. It is HTTP-only, uses SameSite=Lax, and is marked secure when the application runs in production behind HTTPS. Sessions are stored server-side and are destroyed on logout.

Data retention

Account data is retained while the account exists and for a reasonable period afterwards for support and legal records. License and audit records are retained for audit and security purposes.

Your rights

  • Request access to, correction of, or deletion of your personal data.
  • Request a copy of your account information.
  • Ask questions about how your data is processed.
  • Lodge a complaint with the relevant data protection authority.

Requests are handled manually by the administrator through the contact channels listed on the support page.

Security

Passwords are hashed with bcrypt using configurable rounds. Sessions use a server-side store, session identifiers are regenerated at login, and state-changing requests require a CSRF token. Production deployments must run behind HTTPS with a strong session secret.

Third-party links

Broker registration links lead to third-party websites. Their privacy practices are governed by their own policies, not this one.

Changes to this policy

This policy may be updated when the platform changes. The current version is always available on this page.

Last updated: 29 October 2026.