Non-custodial wallet use
ArcFX does not ask for a wallet private key or seed phrase. A wallet signs the ownership and action requests presented to it.
Security model
Wallet authority, operational records, and evidence stay distinct.
ArcFX is designed so a wallet owner retains control of wallet actions while the workspace provides private operational records and a separate evidence trail for eligible invoice analysis.
Explicit payment boundary
A payment action remains distinct from workspace navigation and evidence analysis. Review the wallet request before authorizing it.
Verifiable evidence
Agent Evidence records an analyzed decision and verification state without submitting or executing a payment.
Wallet connection and owner session
Connecting a browser wallet and verifying ownership are separate steps. After the wallet owner completes the ArcFX session verification, ordinary private-workspace navigation can reuse that owner session instead of requesting a signature for every page change.
Disconnect in ArcFX clears the local ArcFX session for that browser context. It does not claim to disconnect the wallet extension from every website.
Private workspace records
Invoice, customer, mandate, run, and evidence records used by the private workspace can be stored through ArcFX backend services. Some convenience features, such as the browser address book, are local to the browser. Do not treat either category as a substitute for your own operational retention and access controls.
Public blockchain activity has its own visibility model and may be independently observable on the relevant network.
Agent Evidence is analysis-only
Agent Evidence remains deliberately Testnet-only. Where it is available, generating evidence can require an Agent Mandate signature for the narrow invoice analysis scope. That signature is not a blockchain transaction, token approval, payment submission, or contract interaction. The resulting decision remains explicitly NOT_SUBMITTED.
A sealed bundle can be retrieved by the authenticated owner and independently verified. The bundle does not transfer wallet authority to ArcFX or an evidence verifier.
Review and release boundaries
ArcFX does not claim that a third-party professional smart-contract audit is complete. Formal review and Mainnet operation are separate release work, not a property implied by a product screen.
- Inspect every wallet signature or transaction request before approving it.
- Do not enter private keys or seed phrases into ArcFX or support channels.
- Keep production and deliberate Testnet development activity separate.
- Report a suspected security issue through the project’s documented contact path.