QuantumCat/Features/Privacy & updates

Privacy & updates · 18 of 18

It runs on your machine. Your keys stay put.

Native on macOS and Windows, updates that verify their own signature — and a straight answer about what never leaves your machine.

Privacy & updates in the QuantumCat terminal.
The terminal on your own machine · real build

What QuantumCat is0:22 · narrated · real build

The desktop app is the source of truth

QuantumCat runs natively on macOS and Windows, and that is where your broker sessions and credentials live. There is no hosted copy of it holding your keys, and no server of ours in the trade path.

Updates arrive by themselves

On launch the app checks for a newer signed build, downloads it silently, and shows a “restart to update” pill. Every package is signed with a key that never leaves the developer’s machine, and the app verifies that signature against a public key compiled into the binary before it will install anything. A build that isn’t signed by that key is refused — there is no override.

Your data stays yours

  • Recorded ticks, the session timeline, journals, bots and screeners are files on your machine — not rows in someone’s cloud.
  • Credentials never leave your machine’s encrypted vault, and never travel to QuantumCat’s servers.
  • The licensing service sees an account, not a book. It answers whether your subscription is active. It is not sent your trades, positions or P&L.
  • Diagnostics are scrubbed on your machine before they leave. Every symbol, price, quantity, order id, file path and e-mail address is stripped out on the device — what is sent is a failure’s reason, the command or component it came from, the app version, the operating system and a random per-install id. No trade contents, no credentials, no positions, no P&L. Your IP is never stored beside a diagnostic — the ingest endpoint sees it only to rate-limit abuse, in a counter kept apart from anything you did and cleared within days. That install id is linked to your account on our side, so support can tell which build you are running and which features you use.

Accounts and access

Sign in with an email and password; the terminal re-checks entitlement periodically. If it can’t reach the licensing service it keeps working on the last verified answer for a bounded window rather than locking you out mid-session over a network blip — and it says plainly that it’s running offline, with how long is left, instead of pretending everything is fine.

See it on your account.