# Know the boundaries.

Source: https://docs.privatar.app/security

Understand what stays in the wallet, what your application receives, and what has actually been verified.

## Custody

The vendor SDK never receives the recovery phrase, BIP39 seed, or wallet spending keys. Native custody uses protected device storage. The Chrome extension stores a password-encrypted local vault. Ordinary browser app previews and Expo Go keep wallet recovery material in memory only.

JavaScript strings, SDK internals, and garbage collection prevent a guarantee of complete memory erasure. Recovery copying exposes the phrase to the clipboard until it is cleared.

## Local transaction proofs

The wallet’s official zkIR WebAssembly prover runs in a dedicated local worker. Forty-seven fixed public circuit and parameter files are bundled with the app and checked against SHA-256 pins during the build. No runtime download or Mac proof server is required by the default path.

A funded 1 tNIGHT Preprod self-transfer completed with this browser prover in about 24 seconds for proving and finalization. That result is browser evidence. Final native proof and performance verification remain pending.

Wallet synchronization and transaction submission still require Midnight network services. Local proving does not make the wallet an offline network client.

## Connection transport

Desktop extension connections use the browser bridge and a wallet approval panel, with browser-origin, tab, network and permission binding. App connections use the hosted HTTPS relay to route encrypted messages. Authenticated app invitations verify a fresh challenge in the background; legacy app invitations retain their comparison code. Mobile uses a direct app link, and desktop-to-phone pairing uses a QR. The development HTTP relay is for loopback use.

Your application still must validate every server challenge and signature. Transport encryption does not replace origin checks, permission enforcement, or nonce consumption.

## Connected-site transaction requests

Android supports reviewed transaction requests on Preview and Mainnet. The extension supports connected-site transactions on Preview. Grants remain bound to the originating site, account and selected network.

Connected-site `makeIntent` and `submitTransaction` require separate wallet reviews and device authentication. Connected contract calls are balanced against actual wallet assets, reviewed with their contract addresses and entry points, and signed only after approval. Submission is separately reviewed and bound to finalized bytes and the originating session. Local proofs do not independently authorize spending. Physical Android authentication and the phone transaction round trip remain pending.

## Verification status

| Area | Evidence |
| Preprod wallet | Actual balances, history, DUST registration, and proved self-transfers. |
| Browser prover | Funded transfer finalized with bundled public material and no private proof server. |
| Preview contract lifecycle | Confirmed wallet-engine swap round trip, contribution, restart and recovery, creator claim, refund, and duplicate-claim rejection. |
| Physical Android | Pending final phone authentication and transaction verification. |
| Mainnet | Configured Android provider access and network-identity checks passed. A funded physical-phone transaction remains unverified. |
| App-store release | Not published. |

## Report a problem

Keep recovery phrases and private proof inputs out of logs, screenshots, analytics, and issue reports. Reproduce issues with a fresh test wallet and share only the minimum public details needed.
