Shared privacy boundary
Horizon Desk and the tools it links share a public-safe, local-first posture. This is not marketing language — it constrains what the suite will and will not do.
Full legal privacy for the parent publication is at hookthehorizon.blog/privacy/. Company commerce and support: Commerce · Support.
- No exact coordinates collected or stored by the suite
- No private access details or secret spots
- Local-first libraries and mastery where declared
- No forced account for core field tools
- Explicit handoffs only — nothing moves between tools until you choose
- Fail closed on access, legality, hazards, and hard rating conflicts
Core principles
Fail closed
Access, legality, safety, and hard rating conflicts never default to “looks fine.”
Freshness is first-class
Stored URLs and version labels are not current claims. Consequential outputs carry an explicit freshness state.
No exact location
Review queues, TTLs, and correction logs stay public-safe. Named public waters only.
No catch guarantees
Tools refuse “best water” rankings and “will catch” framing. Hypothesis, supported, incomplete, and Stop stay precise.
Ready means probed
Desk never shows Ready from a static label alone. Launch URLs and health endpoints are verified live.