Security without shortcuts.
Private BTC AI is designed around watch-only Bitcoin monitoring, controlled withdrawals, server-side isolation, and auditable internal accounting.
No private keys in browser
Browser code never receives wallet signing secrets, seed phrases, xprv values, or WIF keys.
No seed phrases stored
The application is not designed as a hot wallet and must not store mnemonic recovery material.
Watch-only architecture
Bitcoin monitoring is designed around deposit observation, not browser-side signing.
Server-side RPC isolation
RPC details and descriptors remain server-side configuration and are not exposed to the UI.
2FA / step-up verification
Sensitive account and admin operations are protected with additional verification flows.
Manual withdrawal review
Withdrawal requests move through controlled review rather than automatic browser signing.
Offline signing boundary
Signing remains outside this application’s browser runtime.
Auditable activity
Deposits, ledger movements, withdrawals, and security events are represented as trackable records.
Withdrawal boundary
Withdrawal requests are operationally separate from browser access.
The application records and reviews withdrawal intent. It does not turn a browser session into an automatic Bitcoin hot-wallet signer.
Deposit monitoring path
Withdrawal control path
This page intentionally describes architecture at a user-safe level. It does not expose internal endpoints, RPC credentials, descriptor strings, wallet details, or private configuration.