The Sales TravelerIndependent · Reader-funded · A partnership buys reach, never a ratingIndex Desk Live
The Sales TravelerThe decision desk for revenue travel
Open the Index Desk
Implemented controls · external commissioning pending
Linked-wallet privacy prelaunch specification

Linked-wallet privacy: fail-closed production controls

Wallet linkage is optional, purpose-bound, consented, revocable, and represented only by salted purpose-specific identifiers.

  • Data minimization: never place full wallet addresses, signatures, or transaction identifiers in URLs, analytics, logs, or public artifacts.
  • User control: support explicit consent, unlinking, deletion, retention expiry, and session rotation.
  • Boundary: prohibit cross-purpose behavioral identity graphs and fail closed when protected storage is unavailable.
Non-wallet path: Standard sessions and account recovery work without linking a wallet.

Status: Implemented in code; production verification, custody, audit, compliance, and independent commissioning remain pending.

Error and recovery: If a wallet, credential, or network step fails, focus returns here with a plain-language error and the non-wallet fallback remains available. This page never auto-connects a wallet; mobile users may choose a wallet-app deep link only after reviewing the same consequences and recovery path.

Evidence, freshness, and corrections

Written and edited by
Rachel Julian, founder and editor
Last reviewed
2026-08-13
Readiness rule
Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
Correction path
Report a correction or compare the capability changelog.

Source hierarchy

  1. Primary standards: Protocol specifications and standards bodies define what an implementation must do.
  2. Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
  3. Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
  4. Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.