Privacy & Private AI

Privacy & Data Controls

Device-side Privacy — swap risk analysis runs on your device; data never leaves it.

Identifiers are SHA-256 hashed, secrets are dropped at the pipeline boundary, and the analysis function makes zero network calls — by construction, not by promise. What leaves the device, and why, is listed verbatim in the data-flows table below.

Data-sharing level

This controls what any VAULTRY feature may send off your device. Stored locally as vg_privacy_consent.

Per-module consent

Each feature asks before it acts. Turn a module off and its outbound calls stop; on-device analysis it already performed is unaffected.

Swap quotes

Fetches dry-run quotes (asset IDs, amount, recipient/refundTo → 1Click API).

Risk analysis

Runs the SAFE / CAUTION / BLOCKED engine on quotes, locally.

Faucet

Requests testnet NEAR (account ID + public key → official helper).

Oracle monitor

Reads Pyth price feeds for the depeg guard (no wallet data).

Privacy dashboard

Every feature → the data it uses → where that data goes. Single source of truth: DATA_FLOWS in lib/privacy/data-flows.ts.

Feature	Data it uses	Where it goes	Notes
Wallet key management	seed phrase private keys (NEAR / EVM / Solana)	Your device only	Generated, encrypted (AES-GCM via WebCrypto) and stored client-side. lib/wallet/keys.ts performs zero network calls — proven by the privacy audit, not by promise.
Private swap analysis	redacted swap features (asset IDs, amount, slippage, router) SHA-256 hashes of identifiers (never raw addresses)	Your device only	analyzeSwapPrivately() makes zero network calls by construction. Raw addresses, amounts-as-typed and keys never leave the function.
Swap quotes (dry-run)	originAssetId destinationAssetId amountBaseUnits slippageBps recipient refundTo	1Click API via /api/intents/quote	recipient / refundTo are REQUIRED by the 1Click dry-run API (dry:true — no funds can move). Disabled entirely at data-sharing level “nothing”.
Risk analysis	quote amounts registry token metadata your policy	Your device only	assessSwapRisk() is a pure function — no network, no fabricated numbers.
NEAR testnet faucet	newAccountId newAccountPublicKey	helper.testnet.near.org (official NEAR testnet helper)	A public key is public by design. No private material is ever sent.
Oracle monitor	token price queries (no wallet data)	Pyth Hermes (hermes.pyth.network)	Price feeds only — no identifiers, no keys, no amounts leave the device.
Transaction history lookup	NEAR account ID	testnet.nearblocks.io	Public account IDs only. Read-only.
NEAR AI Cloud attestation verification	client-generated random nonce only	cloud-api.near.ai (public, keyless)	Verifies NEAR AI Cloud's live TEE evidence (Intel TDX). Sends no user data and no key. This does NOT mean our analysis runs inside their TEE — it verifies their infrastructure.
Confidential AI analysis (BYOK)	your pasted API key redacted features only	cloud-api.near.ai (your key, direct from your browser)	OPT-IN ONLY. The key lives in your browser's localStorage (vg_byok_nearaicloud) and is sent browser → NEAR AI Cloud directly — never to VAULTRY servers. Needs paid credits or staked NEAR on your own NEAR AI Cloud account.

Verify my privacy

Runs the real redaction pipeline on labeled sample data (not your wallet) and shows exactly what happened to each field — hashed, dropped, or kept — plus the genuine on-device risk verdict.

NEAR AI Cloud attestation verification (public endpoint)

This verifies NEAR AI Cloud's own infrastructure — live Intel TDX attestation evidence from their public, keyless endpoint. It does not mean VAULTRY's analysis runs inside their TEE: our analysis runs on your device (above).

Source: docs.near.ai — Gateway Attestation · public by explicit documented decision (nearai/infra#193) — no account, no key.

Bring your own NEAR AI Cloud key (optional)

Confidential AI inference on NEAR AI Cloud needs an sk- key with purchased credits (or staked NEAR) — there is no free tier, so VAULTRY ships no key. If you have your own, paste it here: it is stored in your browser's localStorage only (vg_byok_nearaicloud) and is sent browser → NEAR AI Cloud directly — never to VAULTRY servers. Keyed requests run an attestation preflight first.

Get a key at cloud.near.ai (their signup + credits are outside VAULTRY). The BYOK analysis path is implemented but not live-tested by us — your first run is the live test.

← Back to VAULTRY