1. Purpose and Scope
This Information Security Policy ("Policy") establishes the principles, standards, and responsibilities for protecting the confidentiality, integrity, and availability of information assets within the NezenX Platform and operations.
This Policy supplements the Privacy Policy Section 10 (Data Security). Where this Policy provides additional operational detail, it takes precedence.
This Policy applies to all NezenX personnel, contractors, and third-party service providers who access, process, or store NezenX information assets.
Current state: NezenX's information security program is in the process of formalization. Certain controls described in this Policy are fully operational, while others are being implemented or enhanced. This Policy describes both current practices and intended standards.
2. Information Security Principles
NezenX's information security program is guided by the following principles:
- Confidentiality — information is accessible only to authorized individuals on a need-to-know basis;
- Integrity — information is accurate, complete, and protected from unauthorized modification;
- Availability — information and systems are accessible to authorized users when needed;
- Defense in depth — multiple layers of security controls are applied so that no single point of failure compromises the system;
- Least privilege — users and systems are granted the minimum level of access necessary to perform their functions.
3. Governance and Responsibilities
Senior management is responsible for overall information security governance, including approval of this Policy, allocation of resources, and oversight of the security program.
Development team is responsible for implementing and maintaining technical security controls within the Platform, including secure coding practices, access controls, and infrastructure security.
Operations team is responsible for following security procedures in daily operations, including secure handling of credentials, client data, and treasury information.
All personnel are responsible for:
- complying with this Policy and related security procedures;
- protecting credentials and access tokens assigned to them;
- reporting suspected security incidents or vulnerabilities promptly;
- not sharing Account credentials or access with unauthorized individuals;
- not storing sensitive data on personal devices or unauthorized systems.
4. Access Controls
4.1. Authentication
Access to the Platform, admin panel, and internal systems requires authentication through secure credentials (email and password). NezenX is in the process of implementing multi-factor authentication (MFA/2FA) for all administrative and privileged access.
4.2. Authorization
Access to systems and data is granted based on role and business need:
Platform User
Clients (Authorized Users)
Own Account data, Virtual Cards, transactions
Operations
Operations team members
Client support, treasury operations, onboarding
Admin
Senior management, designated personnel
Full admin panel access, system configuration
Development
Development team
Platform code, infrastructure, databases
Access Level | Who | Scope |
|---|---|---|
Platform User | Clients (Authorized Users) | Own Account data, Virtual Cards, transactions |
Operations | Operations team members | Client support, treasury operations, onboarding |
Admin | Senior management, designated personnel | Full admin panel access, system configuration |
Development | Development team | Platform code, infrastructure, databases |
4.3. Access reviews
Access permissions are reviewed when personnel roles change or upon departure from the organization. Formal periodic access reviews will be conducted at least annually once the Compliance Officer is appointed.
4.4. Session management
The Platform implements session timeouts for inactive sessions. NezenX is working to standardize session timeout periods across all access points.
5. Data Protection
5.1. Encryption in transit
All data transmitted between Users and the Platform is encrypted using TLS/SSL protocols. Internal API communications between system components use encrypted channels.
5.2. Stored data security
NezenX implements appropriate security measures for stored data, including access controls, secure storage configurations, and separation of environments (development, staging, production).
5.3. Sensitive data handling
The following categories of data require enhanced protection:
- User credentials (stored in encrypted/hashed format only);
- government-issued identification documents (restricted access);
- USDT wallet addresses and transaction hashes;
- Virtual Card details and transaction data;
- internal financial data (treasury balances, reconciliation records).
5.4. Data classification
NezenX classifies information into the following categories:
Confidential
Client PII, KYB documents, credentials, financial records
Encrypted storage, restricted access, no external sharing without authorization
Internal
Operational procedures, team communications, internal reports
Access limited to NezenX personnel, not shared externally
Public
Published policies, website content, marketing materials
No restrictions on access
Classification | Description | Handling Requirements |
|---|---|---|
Confidential | Client PII, KYB documents, credentials, financial records | Encrypted storage, restricted access, no external sharing without authorization |
Internal | Operational procedures, team communications, internal reports | Access limited to NezenX personnel, not shared externally |
Public | Published policies, website content, marketing materials | No restrictions on access |
6. Infrastructure Security
6.1. Cloud infrastructure
The Platform is hosted on cloud infrastructure with security features provided by the cloud service provider, including network isolation, firewall rules, and automated patching.
6.2. Network security
NezenX maintains network-level controls including:
- firewall rules restricting inbound and outbound traffic to authorized services;
- separation of public-facing and internal systems;
- HTTPS enforcement for all web-facing endpoints.
6.3. Environment separation
Development, testing, and production environments are maintained separately. Production data is not used in development or testing environments without appropriate anonymization.
7. Application Security
7.1. Secure development
The development team follows secure coding practices to minimize vulnerabilities in the Platform, including:
- input validation and output encoding to prevent injection attacks;
- parameterized queries to prevent SQL injection;
- protection against cross-site scripting (XSS) and cross-site request forgery (CSRF);
- secure handling of authentication tokens and session data.
7.2. Dependency management
Third-party libraries and dependencies are reviewed for known vulnerabilities. Critical security patches are applied as soon as practicable.
7.3. Change management
Changes to the Platform are deployed through a controlled process that includes code review and testing before production release. Emergency changes follow an expedited process with post-deployment review.
8. Operational Security
8.1. Treasury operations
Treasury-related activities (USDT processing, balance management, funding operations) follow dual verification procedures where feasible. Access to treasury systems and wallets is restricted to authorized personnel.
8.2. Communication security
Sensitive operational communications are conducted through designated channels (Telegram groups with controlled membership). Sensitive data (wallet addresses, large transaction details) should not be shared through unsecured channels.
8.3. Backup and recovery
NezenX maintains backups of critical data and system configurations. Backups are stored securely and tested periodically for recoverability.
9. Third-Party Security
NezenX assesses the security posture of third-party service providers that process or store NezenX data, including:
- Card Issuing Partners;
- cloud infrastructure providers;
- communication and collaboration tools;
- any vendor with access to User data or Platform systems.
Where feasible, NezenX requires third-party providers to maintain appropriate security measures through contractual terms or service agreements.
Third-party access to NezenX systems is limited to the minimum necessary for the service provided and is revoked when no longer required.
10. Security Awareness
All NezenX personnel receive security awareness guidance covering:
- password hygiene and credential protection;
- recognizing phishing, social engineering, and fraud attempts;
- secure handling of client data and sensitive information;
- incident reporting procedures;
- acceptable use of NezenX systems and tools.
Security awareness is reinforced through ongoing communication and updates when new threats or vulnerabilities are identified.
11. Vulnerability Management
NezenX addresses security vulnerabilities through:
- ongoing maintenance and updates of Platform components and dependencies;
- monitoring security advisories relevant to the technology stack;
- applying critical security patches as soon as practicable;
- investigating and remediating vulnerabilities reported by personnel or Users.
NezenX does not currently operate a formal bug bounty program. Users or researchers who identify potential security vulnerabilities are encouraged to report them responsibly to [email protected].
12. Monitoring and Logging
NezenX maintains logs of security-relevant events, including:
- authentication attempts (successful and failed);
- administrative actions and configuration changes;
- access to sensitive data and systems;
- error events and system anomalies.
Logs are retained in accordance with the Data Retention Policy (technical and device data: twelve (12) months).
NezenX reviews logs as part of its risk management procedures to identify potential security concerns. Automated log analysis and alerting capabilities are being evaluated for future implementation.
13. Physical Security
NezenX operates as a remote-first organization. Physical security of workstations and devices used to access NezenX systems is the responsibility of each individual team member.
Personnel must:
- secure devices with screen locks when unattended;
- not access NezenX systems on shared or public computers;
- use secure network connections (avoid public Wi-Fi for administrative access);
- report lost or stolen devices that have access to NezenX systems immediately.
14. Incident Response
Security incidents are handled in accordance with the Incident Response Policy. All personnel must report suspected security incidents immediately to senior management.
The Incident Response Policy establishes procedures for detection, containment, investigation, remediation, and communication of security incidents.
15. Compliance
This Policy is designed to support compliance with:
- the Personal Data Protection Act 2012 (PDPA) of Singapore — data security obligations;
- card network security requirements (PCI DSS standards where applicable to Card Issuing Partners);
- contractual security obligations with Card Issuing Partners and service providers.
NezenX does not currently hold PCI DSS certification. Card data is managed by Card Issuing Partners who maintain their own PCI compliance. NezenX does not store full card numbers.
16. Policy Review
This Policy is reviewed at least annually and updated to reflect changes in the threat landscape, technology, regulatory requirements, or business operations.
17. Amendments
NezenX may update this Policy at any time. Material changes will be communicated to Users via email and/or Platform notification at least thirty (30) days prior to the effective date.
Continued use of the Platform after the effective date of an amendment constitutes acceptance of the updated Policy.
18. Contact
For security concerns or to report a vulnerability:
- Security: [email protected]
- General complaints: [email protected]
- Formal complaints: [email protected]
- Escalation: [email protected] (subject line: "Complaint Escalation — [Reference Number]")