Governance
A high-level explanation of how LightRain is positioned relative to custody, obligations, and auditability. This is orientation for operators and the public—it is not legal advice. Engage qualified counsel for your jurisdiction and use case.
LightRain is built so the product does not take possession of customer funds in the omnibus, pooled sense that regulators associate with custodial platforms. You—or your licensed service provider—remain the party that actually controls movement of value. The software surfaces addresses, history, and policy hooks; it does not substitute for your own custody decisions.
Where the law expects a licensed money services business, bank, or broker-dealer to own compliance, that entity—not LightRain—carries the obligation. Federation endpoints and settlement views are designed to make those boundaries obvious in day-to-day operations, so teams do not accidentally imply that “the app” is the regulated actor.
Human-readable federation-style addresses and structured activity history are first-class. The goal is an audit trail your finance and risk teams can follow without reverse-engineering raw chain data for every question. Exports and labels are shaped for review conversations—not for hiding movement behind opaque IDs.
We steer clear of marketing and product copy that could be read as guaranteeing yield, insurance, or regulatory approval. LightRain describes what the software does in engineering and operational terms. Anything that sounds like legal, investment, or regulatory advice belongs with your counsel—not in a vendor brochure.
For binding terms and policy downloads, see Legal. For product help, see Support. For the conceptual security overview, see the Whitepaper.
© 2026 Hated By Many LLC. All Rights Reserved