Security

Security at NoryX

NoryX is designed so that user funds remain on the connected exchange, trading access is limited to supported operations, and users retain control.

Architecture Overview

NoryX connects to supported exchanges through API credentials. Funds, trading access and withdrawal access are kept separate by design.

USER
You
NORYX
Engine
TRADING API
Exchange API
KRAKEN
Your Account
FUNDS
Remain on Exchange
TRADING ACCESS
Required for supported trading
WITHDRAWAL ACCESS
Not required

Your Funds Stay Yours.

NoryX is software, not a custodian. Supported trading occurs through the connected exchange — not through NoryX-held balances.

No Deposits

NoryX does not receive deposits from users. No funds are transferred to NoryX.

No Custody

NoryX does not hold customer crypto balances. Assets remain inside the connected exchange.

No Withdrawal Access

Withdrawal permissions are not required for supported trading operations.

Users should review their exchange API permissions carefully and only enable the permissions required for supported trading.

No Withdrawal Access

NoryX should not require withdrawal permissions for supported trading operations. Users should never enable withdrawal or transfer permissions on API keys connected to NoryX. If the exchange API permission model changes, this wording should be kept technically accurate.

API-Based Connection

NoryX connects to supported exchanges through API credentials for supported trading functions. Credentials are forwarded securely to the trading engine and are not stored in plaintext in the application database.

User Control

Users can pause supported live trading, disconnect the exchange and manage account access using available platform controls.

  • Pause or stop the trading engine at any time
  • Disconnect exchange API access from the dashboard
  • Manage account access and security settings
  • Review trading activity and system decisions

Infrastructure Boundaries

NoryX also depends on third-party infrastructure. Availability, execution quality and service continuity may depend on those third parties. NoryX does not control third-party uptime.

Exchanges (e.g. Kraken)Payment providers (e.g. Stripe)Hosting and cloud infrastructure

Account Security

  • Authentication controls
  • Session protection
  • Access management
  • Password security

Responsible Disclosure

If you believe you have identified a potential security vulnerability involving NoryX systems, please review our responsible disclosure guidelines.

View Responsible Disclosure