QuantumCat/Security & privacy

Security & privacy

Software you run. Not a service that holds you.

QuantumCat is a desktop application. Your saved keys, recorded tape and trading history live locally. Broker requests, enabled cloud features and JARVIS have their own external connections. Here’s how those boundaries work.

Your machineQuantumCat

Saved keys encrypted locally. Recording follows your enabled scope and cap. Trading tools run here; JARVIS also connects through your ChatGPT session.

official API
direct or configured relay
Your brokerZerodha · Dhan
Angel One · Groww

Executes every order under your own credentials. Your money and securities never leave it.

exchange
member
The exchangeNSE · BSE · MCX

Where the order fills — through the member you already trust.

Your broker executes; the route is explicit. Requests connect directly by default, or through an optional IP relay. Account access, enabled cloud features and JARVIS use separate external connections.

Storage & connections

What stays with you — and what connects.

Local storage and external requests serve different purposes. These are the boundaries of the current product.

Credentials

An encrypted vault on your own disk

API keys, secrets and session tokens are sealed with AES-256-GCM inside QuantumCat’s own data folder. The saved vault is not synced to QuantumCat; credentials are used for the broker authentication flow you choose. Browser sign-in opens the broker’s page; credential-based sign-in takes the required details in QuantumCat. Optional daily sign-in stores those credentials in the local encrypted vault.

Orders

Your broker executes the order

QuantumCat prepares authenticated requests locally. They connect to the broker’s official API directly by default, or through an optional configured IP relay. A relay adds a service dependency; broker acknowledgements and reconciliation still determine the outcome.

Your data

Ticks, journals and backtests stay local

With recording enabled, the terminal saves the streamed contracts selected by your recording scope and cap. Replay and backtests depend on available retained data. Journals, bots and saved research are stored locally.

What we see

Connections depend on the feature

Account access, diagnostics, feature usage, cloud alerts, updates and a configured IP relay use external services. Diagnostic installation identifiers can be linked to your account. JARVIS sends its conversation and relevant tool results through your ChatGPT session. Read the Privacy Policy for data handling, retention and requests.

Updates

Signed, verified, notarized

Every update is signature-checked before it installs. Mac builds are Developer ID signed and notarized by Apple; the app refuses a package whose signature doesn’t match.

AI

JARVIS can’t reach your keys

JARVIS runs on your own ChatGPT plan. The tools that could read credentials or change risk limits aren’t in its toolbox, and it stages orders for your confirmation by default.

The static-IP rule

SEBI’s IP rule, handled.

Since 1 April 2026, brokers accept API orders only from an internet address you’ve registered with them. Market data works from anywhere — only order placement is gated.

  • Guided setup for each broker — one click on Dhan, copy-paste steps for Zerodha and Angel One
  • Drift warnings when your connection’s IP no longer matches what your broker saw
  • Static IP options explained: from your ISP, or your own fixed-IP relay
Read the setup guide
QuantumCat's broker connection setup. Broker setup · real build

Private by design. Fast by nature.