FarmDash Privacy Manifesto
Version: 2026-10-09 · Last Updated: October 9, 2026 · Pseudonymous Architecture & Self-Hosted Typography
FarmDash is built on strict data-minimization and pseudonymous-operation principles. We do not harvest, monetize, or profile off-chain personal identities. The platform operates pseudonymously using cryptographic wallet addresses, public blockchain RPC queries, and self-hosted privacy-hardened infrastructure.
1. Data Minimization & Pseudonymous Architecture
FarmDash is engineered around data minimization and pseudonymous operation. We do not collect, request, or store off-chain personally identifiable information such as your legal name, physical address, email address, phone number, government identity number, or traditional fiat banking credentials.
Sovereignty by Design: Your public account identity across FarmDash is strictly your public cryptographic wallet address (e.g. 0x... on EVM or base58 on Solana). You can inspect and research public DeFi protocols anonymously without account registration or personal disclosures.
2. Data We Actually Process & Persist
To deliver DeFi intelligence, wallet context, and verifiable transaction workflows, FarmDash processes and selectively persists the following technical information:
1. Public Cryptographic Wallet Addresses
When you connect a wallet or enter an address into Scout Mode, we process your public address to query public on-chain balances, token positions, and protocol interactions.
2. Public On-Chain Records & Telemetry
We query public blockchain RPC nodes (including Alchemy, Helius, DRPC, and public validators) to analyze public ledger histories, smart contract calls, liquidity deposits, and claim events. This data is already public on distributed ledgers; FarmDash merely computes Trail Heat scores and Pioneer Pace multipliers.
3. Transaction & Payment Hashes
We persist on-chain transaction hashes and payment receipts (such as USDC subscription payments and x402 micropayments) to verify prepaid activations and prevent replay or double-spending.
4. Authentication & Session Artifacts
In our secure database, we persist user records containing public wallet addresses, active subscription tier and expiry timestamps, and legal consent compliance records (legal_signature_hash, legal_signature_at, and legal_signature_version). Historical consent signatures are preserved strictly as immutable audit evidence of prior terms agreements.
5. Request & Security Telemetry (IP & User-Agent)
To protect the Signal Architect API, x402 TollBooth, and frontend against distributed denial-of-service (DDoS) and bot flooding, we temporarily process incoming IP addresses and user-agent strings. IP addresses are either hashed using rotating cryptographic salts or retained in transient edge memory; they are never compiled into marketing profiles or linked to off-chain identities.
6. Hashed Installation Attribution
An optional installation identifier may be generated client-side and supplied for attribution. FarmDash does not retain the raw installation identifier server-side in installation-attribution analytics. Instead, the server derives a domain-separated HMAC-SHA-256 identifier using a dedicated server-only analytics secret. This pseudonymous identifier measures client distribution and workflow usage; it is analytics/correlation metadata only, not proof of a person or account. It cannot authenticate a user, cannot prove wallet ownership, cannot establish delegation or signing authority, cannot replenish or reset Scout quotas, and cannot authorize an execution or transaction. Installation analytics exclude raw private keys, seed phrases, payment proofs, session tokens or signature payloads.
7. Revenue Spine Events & Warp Gate Routing
When navigating protocol opportunities via the Warp Gate (/go/
Absolute Cryptographic Boundary (Strict Guarantee)
FarmDash NEVER requests, transmits, logs, or stores users' raw wallet private keys or seed phrases under any circumstances. All transaction signing remains strictly on your client device or within explicit, cryptographically bounded policies granted by your wallet.
3. Telemetry, Logging & Self-Hosted Infrastructure
Rate-Limiting & Security: Infrastructure telemetry supports security, abuse mitigation and capacity monitoring. Separate first-party acquisition measurement records a random, non-fingerprint-derived correlation identifier and bounded landing, navigation and product-value events to understand whether discovery reaches useful FarmDash workflows. We do not maintain advertising profiles or sell browsing histories.
First-Party Acquisition Measurement: A random identifier stored in browser local storage is valid for up to 30 days; it is not a browser session, unique person, authentication credential or wallet authority. Acquisition metadata contains only the identifier, bounded path/cohort, source category, event step, timestamp and server-classified synthetic origin. Raw referrer URLs, query strings, search terms and user-agent strings are used only transiently for classification and are not persisted in acquisition metadata. Existing operational funnel records retain their separately disclosed operational fields; acquisition correlation does not change access, quota, billing, signing or execution.
Collection Behavior: First-party acquisition measurement initializes with site analytics without a separate opt-in gate. If browser storage or secure randomness is unavailable, acquisition collection is skipped. Clearing browser local storage removes the local acquisition identifier but does not erase previously recorded server events. Attribution is correlation, not causal proof; source classification can be spoofed.
Zero Third-Party Tracking Cookies: FarmDash uses NO tracking cookies, NO Google Analytics, NO Meta Pixels, NO cross-site tracking beacons, and NO advertising data brokers. Your browsing behavior across FarmDash is never sold, rented, or shared.
Self-Hosted Font Assets: All typography (including Inter, VT323, and Cabin Sketch) is self-hosted directly from our first-party origin (/fonts/). FarmDash makes zero network requests to external third-party font services, eliminating third-party IP exposure on page load.
4. The Revenue Spine & Warp Gate (/go) Attribution
Non-Invasive Attribution: FarmDash operates the Warp Gate (/go/
Server-Side Clean Redirects: When you navigate through a protocol opportunity, referral destinations and affiliate parameters are resolved entirely server-side. Warp Gate injects NO tracking cookies, pixels, or client-side fingerprinting scripts.
Third-Party Venue Policies: Once you redirect to an external partner venue (such as Hyperliquid, Pacifica, or Jupiter), your interactions with that venue are governed exclusively by their own terms and privacy practices.
Third-Party Transaction Routing: FarmDash may transmit information necessary to obtain quotes, prepare transactions, route execution or inspect settlement to third-party protocols and providers, including aggregators, venue APIs and blockchain RPC services. Depending on the workflow, this may include your public wallet address, chain/network, token/mint/contract identifiers, amount, requested action, routing/quote parameters, unsigned/prepared transaction payload information, and transaction hashes or publicly observable settlement information. These providers process the supplied information under their own privacy policies.
Signing Boundary: Raw private keys and seed phrases are not transmitted by FarmDash. Signing remains on the client or within an explicitly authorized, cryptographically bounded signing arrangement; sharing routing or transaction information does not itself confer authority to sign or execute.
5. Data Retention, Sovereignty & Wallet Disconnection
Instant Disconnect: You can terminate your local session at any time simply by disconnecting your wallet and clearing your browser local storage. Disconnecting stops all active polling of your wallet address.
Acquisition Measurement Retention: The 30-day identity validity and 1/3/7/14-day reporting windows are not physical deletion promises. Persisted acquisition events in the existing funnel telemetry spine have no verified automatic deletion guarantee; retention is currently operator-managed. Expired local identifiers are removed or rotated when analytics next accesses them; local storage does not self-delete while the browser is closed.
Installation Analytics Retention: Current installation-attribution analytics do not presently have automatic expiry; retention is operator-managed until automated retention is implemented. Clearing or changing the installation identifier does not erase existing analytics, payment or financial records, and does not reset or replenish Scout quotas. Wallet disconnection does not delete these server-side records.
On-Chain Immutability: Public blockchain transactions, token transfers, and smart contract calls recorded on public chains cannot be deleted or altered by FarmDash.
Historical Audit Evidence: Cryptographic legal consent signatures and on-chain payment hashes are retained in the database solely as immutable compliance evidence demonstrating when and with what parameters terms were accepted or payments verified.
Contact & Inquiries: For questions regarding privacy architecture, telemetry verification, or security, contact the team at @FarmDashone on X.