Zero-Telemetry Protocol • Non-Custodial Architecture

Zero Telemetry & Cryptographic Privacy Commitment

A comprehensive technical specification of HumidiFi’s zero-knowledge posture, local OS keychain isolation, zero analytics tracking guarantee, and sovereign peer-to-peer routing on Solana.

KEY ISOLATION: Secure Enclave / TPM 2.0
TRACKING: 0 Trackers / 0 Telemetry Bytes
NETWORK: Direct Client-to-Validator QUIC
STORAGE: AES-256-GCM / Argon2id
SPECIFICATION: RFC-009-PRIVACY-INVARIANT STATUS: MATURE PROTOCOL STANDARD APPLIES TO: HUMIDIFI DESKTOP & CLIENT LIBS

HumidiFi Cryptographic Privacy Policy & Telemetry Specification

Authored by the HumidiFi Core Cryptographic & Security Engineering Working Group • Last Verified Revision: February 2026
Executive Privacy Declaration
HumidiFi is engineered on a fundamental axiom: your cryptographic keys, trade routing intentions, portfolio balances, and device network identifiers are sovereign private property. In high-frequency decentralised trading, any client telemetry, centralized logging, or third-party web tracking script creates severe informational vulnerabilities, alpha leakage, and regulatory exposure. HumidiFi establishes a verifiable zero-telemetry invariant across all desktop binaries and web portals.
KEYWORDS: Zero Telemetry Non-Custodial Zeroize Memory Secure Enclave TPM 2.0 Direct TPU QUIC Air-Gapped Signing

01. Absolute Zero-Telemetry & Tracking Invariant

#

Traditional Web3 interfaces and browser extensions silently embed dozens of third-party analytical SDKs, session replay trackers, telemetry beacons, and error-reporting daemons. These trackers capture browser canvas fingerprints, IP addresses, wallet connection timestamps, RPC latency profiles, and granular DOM interactions.

HumidiFi enforces an architectural ban on all tracking SDKs. Neither our website nor our native desktop application contains any form of third-party telemetry, behavioral monitoring, or analytics middleware.

Strictly Prohibited & Excluded Tracking Services
BANNED
Web Trackers
Google Analytics, Mixpanel, Segment, Amplitude
BANNED
Session Replays
Hotjar, FullStory, LogRocket, Clarity
BANNED
Ad Pixels
Meta Pixel, Twitter Tag, Reddit Pixel, TikTok
BANNED
Cloud APM Beacons
Datadog RUM, Sentry Replay, New Relic Browser

1.1 Zero Network Pingbacks & Telemetry Scrubber

When you launch the HumidiFi Desktop terminal, zero network requests are dispatched to any HumidiFi server. The terminal establishes direct socket connections only with the blockchain RPC nodes, TPU validator leaders, and local hardware keyrings explicitly specified by the trader.

  • Zero App Launch Telemetry: No heartbeat pings, crash reporting beacons, or license validation queries.
  • Zero User Profiling: We do not generate, assign, or persist any Unique Device Identifier (UDID), Advertising ID (IDFA/GAID), or hardware MAC address hash.
  • Zero Unsolicited DNS Queries: HumidiFi resolves DNS strictly for configured RPC hosts and validator gossips.

02. Local Key Custody & Volatile Memory Lifecycle

#

HumidiFi is strictly non-custodial. We have never held, cannot hold, and will never have access to your private keys, seed phrases, mnemonics, or recovery passwords. All cryptographic key operations occur in dedicated, hardware-isolated memory regions on your local machine.

Operating System Hardware Enclave Primitive Cryptographic Primitive Protection Guarantee
macOS (Apple Silicon & T2) Apple Secure Enclave Processor (SEP) Keychain Services + kSecAccessControlBiometryAny Hardware-isolated from macOS kernel & root malware
Windows 10 / 11 Trusted Platform Module 2.0 (TPM) Windows DPAPI + CryptProtectData API Cryptographic key encryption bound to host motherboard TPM
Linux (X11 / Wayland) Kernel Keyrings / Secret Service API Argon2id KDF + AES-256-GCM Hardware Vault Memory-locked pages via mlock(2) preventing swap file spills

2.1 Rust zeroize Memory Scrubbing Invariant

In volatile system memory, private key bytes are held for the minimum microseconds required to compute Ed25519 Schnorr signatures. Upon transaction signing completion, the memory allocations are aggressively overwritten with zeros using the cryptographic Rust crate zeroize::Zeroize.

Rust (Memory Scrubbing Invariant)
use zeroize::{Zeroize, ZeroizeOnDrop};

#[derive(Zeroize, ZeroizeOnDrop)]
pub struct EphemeralSigningKey {
    pub key_bytes: [u8; 32],
}

impl EphemeralSigningKey {
    pub fn sign_and_wipe(&mut self, message: &[u8]) -> Signature {
        let signature = ed25519_dalek::SigningKey::from_bytes(&self.key_bytes)
            .sign(message);
        // Memory is immediately overwritten with 0x00 upon drop
        signature
    }
}

This guarantees that even if a malicious process attempts a cold-boot attack, core dump inspection, or memory scraping technique (`ptrace`), no plaintext private keys remain lingering in unallocated RAM buffers.

03. Direct RPC & Network Layer Anonymity

#

Many modern Web3 applications funnel user transactions through proprietary cloud relays or hosted RPC nodes. This centralized bottleneck exposes trading intentions to internal front-running bots, MEV searchers, and IP address loggers.

HumidiFi eliminates all intermediate proxy servers. The client communicates directly over encrypted TLS 1.3 and QUIC transport to decentralized Solana nodes and TPU validator sockets.

  • No HumidiFi Proxy Servers: Transactions and RPC calls are never routed through or inspected by HumidiFi infrastructure.
  • Custom RPC Support: Users can configure private, dedicated RPC providers (such as Helius, Triton One, QuickNode) or their own local Solana validator node directly in the terminal settings.
  • Tor & SOCKS5 Proxy Compatibility: The desktop terminal includes built-in SOCKS5 proxy support, allowing advanced traders to route all gossip and RPC network traffic through the Tor network or private WireGuard VPN tunnels.
  • Dynamic Validator TPU Routing: Swaps are dispatched straight to the current and next 4 leader validators over direct UDP/QUIC streams, bypassing public mempools and preventing front-running.

04. Public Blockchain State vs Private Client Data

#

A critical distinction must be drawn between public on-chain consensus state and private client-side data. Because Solana is a public distributed ledger, transactions broadcast to validators become part of the immutable public record. However, all off-chain metadata, layout configurations, and unbroadcasted orders remain strictly private on your device.

Data Category Location / Storage Visibility Scope Encryption / Protection
Signed Transactions & Swaps Solana Blockchain Ledger Public (Validators & Block Explorers) Cryptographic Ed25519 Schnorr Signature
On-Chain Token Balances Solana SPL Token Accounts Public On-Chain State Protected by Account Authority Keys
Unbroadcasted Limit & DCA Orders Local SQLite / RocksDB (User Machine) 100% Private (Never Transmitted) AES-256-GCM Local Database Encryption
Token Watchlists & Chart Layouts Local Application Preferences 100% Private (Local Disk Only) OS Sandboxed Storage
Wallet Nicknames & Account Tags Local Client Keyring 100% Private (Never Synced) Argon2id Master Password Vault
IP Addresses & Network Timestamps Direct Socket Transport Zero Logs Kept by HumidiFi TLS 1.3 / Optional SOCKS5 Tor Proxy

05. Data at Rest Encryption, Anti-Fingerprinting & Nuclear Cache Purge

#

All persistent files created by HumidiFi Desktop—including token metadata caches, RPC benchmark records, and locally encrypted keyrings—are stored with strict operating system access permissions (POSIX 0600 on macOS/Linux, restricted ACLs on Windows).

5.1 Zero Hardware Fingerprinting

HumidiFi does not perform Canvas rendering fingerprinting, WebGL shader sampling, AudioContext frequency analysis, battery status API polling, or font enumeration attacks. Our desktop codebase is compiled with native graphics bindings that interface directly with Metal, DirectX 12, or Vulkan without exposing hardware telemetry IDs.

5.2 Nuclear Cache Purge (“Zeroize Vault”)

Inside the HumidiFi Desktop Settings menu, traders have instant access to the Nuclear Purge function. Executing this command performs a three-pass cryptographic overwrite (Gutmann-derived pattern) of all local caches, IndexedDB databases, RPC logs, and session tokens, followed by immediate process termination.

  • Instantly clears all volatile RAM allocations and system caches.
  • Overwrites and unlinks local SQLite transaction history databases.
  • Revokes all temporary hardware wallet session handles.
  • Leaves zero residual configuration files or recovery traces on disk.

06. Deterministic Builds, Code Signing & Update Security

#

Software supply-chain integrity is an essential pillar of cryptographic privacy. A privacy policy is meaningless if binary updates can be hijacked by compromised build servers or malicious DNS resolvers.

HumidiFi guarantees that all desktop artifacts are built via Deterministic, Reproducible Rust Toolchains and digitally signed with verified cryptographic certificates:

  • Apple Developer ID & Notarization: macOS universal binaries (.dmg, .pkg) are signed with an official Apple Developer ID certificate, hardened with macOS Hardened Runtime, and notarized directly by Apple's automated notary service.
  • Microsoft Authenticode EV Code Signing: Windows installer is signed with an Extended Validation (EV) hardware token certificate, preventing SmartScreen tampering warnings.
  • SHA-256 Checksums & GPG Signatures: Every official release publishes SHA-256 checksums alongside an ASCII-armored GPG signature file signed by the official HumidiFi Security Master Key (`0x4D65FF00D2FF66E0`).
  • Ed25519 In-App Update Verification: The in-app auto-updater checks the cryptographic Ed25519 signature embedded inside the release manifest before staging or executing any binary update, eliminating DNS hijacking and CDN spoofing vectors.

07. Web Showcase vs Desktop Client Privacy Model

#

To serve institutional and retail traders worldwide, HumidiFi maintains both an informational static web showcase (humidifi.app) and the native HumidiFi Desktop terminal. Both environments adhere to strict privacy safeguards:

Privacy Vector Static Web Showcase (Website) HumidiFi Desktop (Native App)
Third-Party Cookies & Ads Zero Cookies (Strict Cookie-Free Header) Zero Cookies (No Web Browser Engine)
Content Security Policy (CSP) Strict default-src 'self' (No external scripts) Native OS Sandbox with Zero DOM Injection
Private Key Handling No key generation (Read-only Showcase) Secure Enclave / TPM 2.0 / Ledger HID
Network Dispatch Static Global CDN edge caches (Cloudflare/Fastly) Direct Peer-to-Validator Socket QUIC
Server Logs Retention Transient edge routing logs (Pruned every 24h) 0 KB Server Logs (Client-Only Architecture)

08. Hardware Wallets & Air-Gapped Signers Model

#

For maximum cryptographic security, HumidiFi provides native, zero-cloud integration with institutional hardware keyrings and air-gapped signers:

  • Direct WebHID & libusb USB Protocol: Direct USB communication with Ledger Nano S, Nano S Plus, Nano X, Ledger Flex, and Ledger Stax. Key handles and APDU frames communicate straight over raw OS USB interfaces without routing through third-party browser extensions or cloud relay servers.
  • Air-Gapped Keystone QR Code Verification: When signing transactions via Keystone hardware wallets, the transaction payload is rendered as an animated, high-density QR code on screen. The camera scanner decodes the signed payload locally in volatile memory using open-source Rust QR decoders. No camera video frames or images are ever persisted to disk or sent across the network.
  • Clear-Signing Verification: The desktop terminal decodes all instruction data, spl-token transfer amounts, slippage bounds, and compute budget priority fees before displaying them on your hardware wallet display, preventing blind signing vulnerabilities.

09. Zero Third-Party Monetization, AI Data Mining & Analytics

#

HumidiFi operates strictly on an open-source decentralized liquidity protocol model. We reject the extractive business models prevalent in conventional financial platforms.

  • Zero Data Brokering: We do not sell, rent, license, or monetize user data, trading volume records, IP locations, or wallet balances to third-party data brokers, hedge funds, or advertising networks.
  • Zero AI Model Training on User Trades: We do not ingest user order history, portfolio balances, or private strategies into large language models (LLMs), automated market maker prediction models, or proprietary quantitative trading bots.
  • Zero Payment for Order Flow (PFOF): HumidiFi does not sell user swap order flow to private market makers or centralized OTC desks. Swaps are routed transparently into on-chain Aquarium Prop AMM pools and validator leader slots.

10. Cryptographic Verification, Open Source & Policy Immutability

#

True privacy cannot rely on corporate goodwill—it must be provable through transparent source code, deterministic binaries, and formal mathematical audits.

HumidiFi’s client protocols and on-chain Anchor smart contracts are subject to continuous peer review and third-party security verification by top-tier cryptographic audit firms including OtterSec and Neodyme.

Immutable Policy Specification Manifest SHA-256 Verified
DOCUMENT_SPEC: RFC-009-PRIVACY-INVARIANT-v2.4
CANONICAL_HASH: 3c8e92f1b4a7d6e5c891f2b45a6d7e890123456789abcdef0123456789abcdef
SIGNING_KEY:    0x4D65FF00D2FF66E0 (HumidiFi Core Security Master)
VALIDITY:       Continuous Protocol Invariant (Mainnet-Beta Verified)

Any prospective modification to this privacy policy or the underlying telemetry architecture is published transparently via cryptographic pull requests in our open-source repositories with mandatory multi-signature authorization.