KEIZ stores the minimum needed to run your workspace: your NEAR account id, vendor bills, customer invoices, customers, vendors, payments, journal entries and an audit log.
Wallet sign-in asks your wallet to sign a NEP-413 message; that signature is verified server-side. KEIZ never receives a private key.
Bill and invoice documents, ledger entries and payment metadata are stored in the configured MongoDB database. On-chain data is public by nature.
Agent custody. When you enable OutLayer custody, the agent keys live inside OutLayer’s Intel TDX enclave. The master secret is derived from NEAR MPC, and policy is evaluated inside the TEE before anything is signed. KEIZ stores an AES-256-GCM encrypted API key and returns the custody handoff only to the workspace owner.
Private inference. When configured with a NEAR AI Cloud key, prompts and responses go to NEAR AI Cloud, which runs inference in Intel TDX and NVIDIA confidential computing and can provide TEE attestation and signed responses. If you run the local provider, prompts stay in your API process and no external model call is made.
Workspace isolation. Every authenticated query is scoped by the orgId in your session. Assistant tools receive orgId from the request context, never from model output. Chat history and workspace data are stored in your configured MongoDB.
Audit data. The audit log records the method, path, user, status, IP and timestamp. It does not store request bodies. Secret values are never logged.
TEE. A Trusted Execution Environment is hardware-isolated compute. It reduces exposure but is not a guarantee against every threat; review the provider’s attestation and terms.
Third-party services. OutLayer, NEAR AI Cloud, NEAR RPC and 1Click process data as needed for the features you enable. Their terms and privacy policies apply.
This page is a placeholder for a production privacy notice and is not legal advice.