Built to Be Legal
Everywhere You Operate.
The question every landlord asks is: "How does this work in my jurisdiction?" Huddle's Compliance Mesh routes each tenancy through the right ruleset, documentation flow, and exception path for that bond. We automate what we can, surface what needs review, and never present the platform as a substitute for your counsel.
The Legal Foundation
CFTC Release 9180-26
Huddle maintains a jurisdiction-aware compliance layer across deposit bonds, disclosures, timelines, and operational evidence. The platform is designed to work with applicable tenancy law rather than pretend those rules do not exist.
Tenancy Law Compliance Layer
The mesh separates bond mechanics from jurisdiction-specific tenancy requirements. Deposit limits, disclosure obligations, return timelines, interest treatment, and documentation standards are all handled through the applicable ruleset and surfaced to operators when manual review is needed.
A note on legal advice: Huddle provides compliance automation, documentation support, and evidence trails. We do not provide legal advice, and parties should use counsel whenever they need legal interpretation or jurisdiction-specific guidance.
Every automated action has an evidence trail.
Compliance Mesh is not just rule matching. It records the inputs, decision path, reviewer state, generated document set, and on-chain assent references so operators and counsel can reconstruct why a bond proceeded or paused.
Inputs
Property address, tenancy facts, lease type, deposit amount
Ruleset
State, provincial, or territory deposit requirements
Decision
Auto-approve, block, or route for manual review
Evidence
Disclosure packet, signatures, hashes, reviewer notes
Agent-assisted actions are logged with timestamps and decision metadata so a reviewer can audit the difference between automated handling and human exception review.
What the Mesh Handles Automatically
Every time a HuddleBond is created or transferred, the Compliance Mesh runs a jurisdiction check and determines whether the bond can proceed automatically or should be routed for review.
Deposit Caps
Some jurisdictions cap deposits at one month's rent. Others allow more. The mesh checks the applicable cap and blocks or flags bonds that exceed it.
Disclosure Requirements
Different jurisdictions require different notice language, disclosure timing, and evidence records. The mesh prepares the right documentation set for the tenancy facts it is given.
Return Timelines
Return windows vary by jurisdiction. The HuddleSentinel tracks tenancy end dates, required notices, and handoff timing so operators can act inside the applicable window.
Interest Requirements
Several jurisdictions impose deposit-interest obligations or require a specific treatment of funds. The mesh captures those requirements and applies the matching bond terms, disclosures, or review path.
Mutual Assent Verification
Every Deposit Assignment and HuddleBond creation requires verifiable mutual assent from both parties. The mesh records that election and preserves the evidence trail tied to the tenancy.
Canadian RTB Compliance
Canadian jurisdictions can require different deposit handling, notices, and dispute pathways. The mesh applies the province-specific workflow and routes anything uncertain for review.
63 Jurisdictions. One Availability Model.
All 50 United States
All 13 Canadian Provinces & Territories
Vancouver / BC note: Vancouver is Huddle's first proof market, but supported jurisdictions can participate beyond BC as well. The availability model distinguishes featured launch markets, open participation, and manual-review cases without walling off the rest of the compliance mesh.
Operational Clarity for Both Sides
The Compliance Mesh keeps the bond relationship legible. Tenants see protected principal and portability. Landlords and property managers see deadlines, documentation, and bond-specific economics in one place.
No more deposit account management
The bond relationship is tracked in one place with explicit records for deposit amount, elections, timelines, and settlement evidence. That reduces administrative drag and makes handoffs cleaner.
Automatic settlement documentation
When a tenancy ends, the mesh prepares the jurisdiction-aware settlement packet, evidence trail, and next required action so both sides can review the same operating record.
Dispute-resistant by design
On-chain records and structured evidence reduce the most common disputes about timing, assent, and settlement history. Both sides can point to the same ledger-backed record.
Partnership economics stay explicit
The bond terms make the tenant and landlord split visible from day one. Huddle records the election, the concession terms when relevant, and the principal-floor boundaries the workflow is designed to preserve.
Compliance Needs a Living Operating Layer.
63 jurisdictions. One platform. Jurisdiction-aware workflows.
Vancouver is the first spotlight market. Wider participation depends on the applicable ruleset, required disclosures, and any manual review Huddle routes before a bond proceeds.