Luminex EA Hosting logoLuminexEA Hosting
Legal Centre

Data Processing and Security Information

Version
1.0
Effective
2026-11-18
Last updated
2026-11-18

Draft – pending legal review

On this page

  1. Safeguards in place
  2. Being confirmed
  3. Privacy requests
  4. Breach response
  5. Reporting a security issue

Safeguards in place

  • Encryption in transit: the site and its services are served over HTTPS (TLS).
  • Passwords: account passwords are handled by the authentication service and stored as hashes, never in plain text by Luminex EA.
  • MT5 credentials: stored in server-only database tables that the app's browser code cannot read; never returned to the app after entry.
  • Access control: database row-level security limits each user to their own records; admin areas are checked on the server against a separate roles table.
  • Sessions: one signed-in device per account; other sessions are signed out.
  • Consent records: stored append-only so they cannot be edited or deleted through the app.
  • Mentor website keys: stored as hashes and can be rotated or revoked.

Being confirmed

  • Encryption at rest for the database and for stored MT5 credentials beyond the hosting provider's defaults: To be confirmed.
  • Audit logging beyond compliance change logs and trade records: To be confirmed.
  • Written operator agreements with each provider (POPIA section 21): To be confirmed.

Privacy requests

You can request a copy of your information or account deletion in Settings. An administrator reviews each request; deletion happens only where legally permissible.

Breach response

  1. Contain the incident and preserve evidence.
  2. Assess what information and which people are affected.
  3. Notify the Information Regulator and affected users as soon as reasonably possible (POPIA section 22).
  4. Fix the cause and record the incident.

Reporting a security issue

Email luminexea@gmail.com with "Security" in the subject.

Luminex EA · South Africa · luminexea@gmail.com