Security Policy
Our approach to protecting customer accounts, data, systems, infrastructure and digital services.
This Security Policy explains the general security practices and principles used by NaamX to help protect its services, infrastructure, customer accounts and information.
NaamX provides web hosting, ERP, POS, SaaS, cloud, business email and other digital services through naamx.com. Security is an important part of maintaining the availability, reliability and integrity of these services.
1. Security Commitment
NaamX is committed to implementing reasonable technical and organizational measures designed to protect its systems and customer information against unauthorized access, misuse, alteration, disclosure, loss and destruction.
2. Infrastructure Security
NaamX may use security controls at infrastructure, network, operating-system, application and account levels to help protect its services.
3. Access Control
Access to internal systems and customer information is restricted according to operational requirements and authorized access privileges.
4. Authentication
NaamX supports appropriate authentication and account-security mechanisms depending on the service and platform.
Customers are encouraged to use strong passwords and any available multi-factor authentication features.
5. Password Security
Customers are responsible for keeping their passwords and authentication credentials confidential.
Passwords should not be shared with unauthorized individuals or stored in insecure locations.
6. Data Protection
NaamX uses reasonable safeguards designed to protect customer data during storage, processing and transmission where applicable to the relevant service.
7. Encryption
Encryption technologies may be used where appropriate to protect data during transmission or storage.
The availability and implementation of encryption may vary according to the particular service, application and infrastructure.
8. Network Security
NaamX may use firewalls, network controls, monitoring systems and other security technologies to help protect its infrastructure against unauthorized traffic and malicious activity.
9. Monitoring
NaamX may monitor systems and infrastructure for availability, performance, security events, suspicious activity and operational problems.
10. Threat Detection
Security systems may be used to identify suspicious behavior, unauthorized access attempts, malware, abusive traffic and other potential threats.
11. Vulnerability Management
NaamX may review and address known security vulnerabilities in systems under its operational control according to their severity, risk and available remediation options.
12. Security Updates
Security patches and software updates may be applied to supported infrastructure when reasonably necessary to maintain security and reliability.
13. Malware Protection
Depending on the applicable service, NaamX may use malware detection, scanning, firewall or other security technologies to identify potentially harmful activity.
14. DDoS & Network Protection
NaamX may use network protection and traffic filtering mechanisms designed to reduce the impact of denial-of-service and other malicious network activity.
15. Account Security
Customers are responsible for securing their individual accounts, administrator accounts, websites, applications and connected third-party services.
16. Customer Responsibilities
Customers should regularly update their applications, CMS installations, plugins, themes, frameworks and other software components used with NaamX services.
17. Secure Software
Customers should use trusted software, maintain supported versions and remove unused applications, plugins and accounts where appropriate.
18. Security Incident Response
If a security incident is identified, NaamX may take reasonable steps to investigate, contain, mitigate and recover from the incident.
19. Incident Notification
Where required by applicable law or contractual obligations, NaamX may notify affected customers about relevant security incidents involving their information.
20. Emergency Security Measures
NaamX may temporarily restrict, suspend or isolate affected services when necessary to protect infrastructure, customer data or other users from an active security threat.
21. Backups & Recovery
Where backups are included in a customer's service, NaamX may maintain backups to support operational recovery and business continuity.
Customers should maintain independent backups of critical business information where appropriate.
22. Data Retention
Security logs, technical records and other operational information may be retained for periods reasonably necessary for security, troubleshooting, compliance and service management.
23. Third-Party Providers
NaamX may rely on trusted third-party infrastructure, cloud, security, payment, communications and other service providers.
Such providers may have their own security controls and policies.
24. Physical Security
Where infrastructure is hosted in third-party data centers, physical security may be provided by the relevant data-center or infrastructure provider.
25. Employee & Personnel Security
Access to systems and information may be limited to authorized personnel who require access for legitimate business or operational purposes.
26. Confidentiality
NaamX expects personnel and authorized service providers with access to confidential information to maintain appropriate confidentiality obligations.
27. Security Awareness
NaamX may implement reasonable internal practices designed to promote security awareness and responsible handling of information.
28. Logging
Relevant systems may maintain technical logs for security, troubleshooting, performance monitoring, fraud prevention and operational purposes.
29. Fraud Prevention
NaamX may use technical and operational controls to detect and prevent suspicious transactions, account abuse, unauthorized activity and other fraudulent behavior.
30. Responsible Disclosure
Security researchers and customers are encouraged to report suspected security vulnerabilities responsibly and provide enough information for NaamX to investigate the issue.
31. Security Vulnerability Reports
A vulnerability report should, where possible, include a clear description of the issue, affected service, potential impact and reasonable steps to reproduce the problem.
32. Prohibited Security Testing
Security testing must not intentionally disrupt services, access information belonging to other customers or cause damage to NaamX infrastructure.
33. Customer Data Access
NaamX may access customer environments when reasonably necessary for support, maintenance, troubleshooting, security or legal compliance, subject to applicable permissions and policies.
34. Privacy
Personal information is handled according to the applicable NaamX Privacy Policy and relevant data-protection requirements.
35. Security Limitations
No internet-connected system can be guaranteed to be completely secure. NaamX cannot guarantee that every security threat, vulnerability or attack will always be prevented or detected.
36. Customer Security Best Practices
- Use strong and unique passwords.
- Enable multi-factor authentication where available.
- Keep software and plugins updated.
- Remove unused administrator accounts.
- Regularly review account access.
- Maintain backups of important business data.
- Avoid sharing login credentials.
- Monitor unusual account activity.
- Use secure devices and networks.
37. Changes to This Security Policy
NaamX may update this Security Policy from time to time to reflect changes in technology, security practices, services, infrastructure or applicable legal requirements.
38. Contact Us
If you have a security concern, suspect unauthorized access or wish to report a potential vulnerability involving NaamX services, please contact us.
Web Hosting, ERP Solutions & Digital Business Services
Last Updated: 20 August 2026




