1. Data-controller responsibilities
The responsible company determines why and how personal data is processed for registration, account administration, security, verification, support and connected MT4 services. Current company and contact information is published in the website footer and contact page.
2. Lawfulness, fairness and transparency
Processing is tied to stated purposes and an appropriate legal basis, such as contract performance, legal obligation, legitimate interest, consent or establishment of legal claims. Notices should explain material processing in clear language and avoid using information incompatibly with the original purpose.
3. Data minimization and accuracy
Only information reasonably relevant to account creation, KYC, financial requests, security, communications and MT4 connectivity should be collected. Clients can update eligible profile information and should notify the platform when identity, address or contact details become inaccurate.
4. Privacy by design and default
- Role-based access to administrator and client data.
- Encrypted storage for retrievable sensitive credentials and financial details.
- CSRF protection, rate limiting and strict form validation.
- Private storage and authenticated delivery for KYC files.
- Minimal public exposure of MT4 comments and technical identifiers.
5. Individual rights
- Access eligible personal data and obtain information about processing.
- Correct inaccurate or incomplete records.
- Request erasure or restriction where legal conditions are met.
- Object to certain legitimate-interest or marketing processing.
- Withdraw consent where consent is the basis.
- Request portability for eligible data in a structured format.
- Complain to an appropriate supervisory authority.
6. Automated processing and profiling
Automated controls may support fraud detection, rate limiting, sanctions screening, security alerts or assignment workflows. Where a decision produces significant legal or similar effects and applicable law grants rights, appropriate information and human review should be available.
7. Processors and service providers
Hosting, email, realtime messaging, security, analytics, storage and MT4 connectivity providers may act as processors. Agreements should define confidentiality, security, permitted processing, assistance with rights requests and deletion or return of data when the service ends.
8. International transfers
When personal data is transferred outside the relevant jurisdiction, the platform should assess the destination and apply a recognized transfer mechanism or other lawful safeguard where required, such as adequacy decisions, standard contractual clauses or supplementary protections.
9. Retention and accountability
Retention schedules should reflect legal, accounting, AML, complaint, security and operational needs. Processing activities, access controls, incidents and rights requests may be documented to demonstrate accountability. Data should be deleted or anonymized when no longer required.
10. Incident response
Suspected personal-data breaches are assessed to determine scope, risk and containment measures. Relevant processors and internal teams should cooperate promptly. Authorities and affected individuals are notified when the applicable legal threshold is met.
11. Exercising your rights
Submit a clear request through the published privacy or support contact. Identity may be verified before information is released or changed. Complex or repetitive requests may require additional time where permitted, and legally required records may be retained despite an erasure request.