Account protection
Multi-factor authentication, secondary confirmation for sensitive actions and detection of anomalous logins make it harder for a stolen password to become a stolen account.
Security framework
Security is a system, not a setting.
Accounts, assets, transactions, data and internal governance are connected. Protecting one without the others is not protection at all.
Why security has to be layered.
As millions of users join a platform, securing accounts, assets and transaction data becomes increasingly critical. No single control carries that responsibility. Multi-factor authentication can fall to a convincing phishing page; a withdrawal review can be undermined by excessive internal access; encryption cannot compensate for a compromised operator account.
NPX regards the security of user assets, accounts and data — together with system stability — as foundational pillars for the platform's long-term development. Its framework combines controls across the user journey and the internal organization: multi-factor authentication, secondary confirmation for sensitive actions, detection of anomalous logins, risk-based review of withdrawals, tiered internal access controls, multi-party approval for critical operations, data encryption and real-time risk monitoring.
For NPX, true security is not a standalone technical feature. It is a comprehensive system spanning user accounts, assets, transactions, data and internal governance.
The principle
A control is only useful if it is hard to bypass and easy to audit. Sensitive actions should require more than one proof and one person.
No absolute guarantee
No security program can eliminate risk entirely. NPX's framework is designed to reduce exposure and respond quickly; it does not guarantee that loss, interruption or unauthorized access will never occur.
The layers
Controls that reinforce one another.
Each layer addresses a different failure mode — a stolen credential, an unusual withdrawal, an internal mistake or an emerging threat pattern.
Withdrawal and transaction review
Withdrawals are subject to risk-based review — a checkpoint before suspicious fund movements become irreversible.
Internal access control
Tiered access controls limit what any individual can see and do. Multi-party approval for critical operations reduces the chance that one compromised account can move sensitive systems.
Data protection and monitoring
Data encryption protects information in transit and at rest, while real-time risk monitoring looks for patterns that individual controls might miss.
Separation of duties
Access is not authority.
Asset separation at NPX is treated as a separation of functions, not a label. Account access, transaction authority, review responsibility and administrative control are intended to sit with different roles and proofs. Sensitive actions combine confirmation with review; critical operations require multi-party approval.
The same logic applies internally: staff should do their jobs without blanket authority over user assets, and no single operator should complete a critical action alone. Specific controls, thresholds and review paths may change as the platform evolves.
NPX does not represent that any particular account structure, custody or insurance protection is in place. Review current platform terms before relying on any security claim.
Risk response
Prepared for the moments that matter.
Controls reduce the likelihood of an incident; response determines its impact. NPX continues to strengthen its risk response mechanisms against account hijacking, unauthorized actions, suspicious fund movements and other potential risks.
Detect
Anomalous logins, unusual transaction patterns and risk signals are surfaced for review rather than left to user complaints.
Contain
Risk-based holds, account protections and access restrictions can limit the reach of a suspected compromise while facts are established.
Review and improve
Incidents and near misses inform control changes, training and monitoring priorities. Security is an operating cycle, not a one-time certification.
Compliance boundaries
Incorporation is not a license.
NPX distinguishes enterprise registration, platform operation and specific regulatory authorization. A company established in accordance with the law does not automatically obtain licenses for all financial businesses in all countries.
For digital asset contracts, derivatives, custody, fiat payments and other supervised businesses, NPX states it will complete legal assessment and compliance review based on the actual operating area and business attributes, opening the business only after obtaining applicable licenses when necessary.
The company also plans to gradually establish a compliance management system that includes customer identification, anti-money laundering, counter-terrorism financing, sanctions screening, abnormal transaction monitoring and risk assessment. For a platform serving millions of users, compliance should not be reflected in a single certificate; it should run through accounts, funds, transactions, products and the entire operating system.
What this means for users
- Product availability can differ by jurisdiction and business line.
- Some services may not be offered until applicable licenses are obtained.
- Registration details should be verified against official company records.
- Nothing on this site should be read as a claim of regulatory approval.
The NPX network
Six domains, one company story. Compliance and authenticity have their own place in the network.
Domains in the NPX network are operated as separate informational properties. Verify official channels before acting on any company information.
Questions about security or compliance?
Reach NPX for account protection guidance, institutional due diligence or security reports.