Draft — pending attorney reviewThis is a working draft for counsel. It is not legal advice and it is not a final policy.

Facility SaaS Agreement

Version 2026-10-20. Terms for a facility that uses Yardlaunch management software.

Draft status

This page is a working draft for counsel. It is not legal advice and it is not a final contract. Version 2026-10-20.

This agreement is between the facility and Yardlaunch. Longyards and Yardlaunch are used together here. Counsel should insert the legal entity name, address, and governing law before anyone relies on this draft. A facility in Florida and a facility in Ontario may need different notices.

The software is a tool

Yardlaunch is management software. It is a tool the facility uses to keep its own records, messages, and gate commands. Yardlaunch is not the operator of the facility and is not a party to the rental between the facility and its guest.

The software is provided as is. Yardlaunch does not warrant that it will be uninterrupted, error-free, or fit for a particular law or use, or that a gate, camera, or lock will obey a command. Some places do not allow a disclaimer, and those places control.

The facility is the operator

The facility is the operator. It is solely responsible for its guests, for the condition of the yard, and for deciding who may enter. Gate access decisions are the facility's. Yardlaunch does not decide who is allowed in.

The facility is solely responsible for any lien, sale, or auction of stored property. Those steps must follow the law of the place where the yard sits. Yardlaunch does not start a lien or an auction, and it does not decide that the local rules have been met. The facility will not treat a software status, a reminder, or a generated notice as legal advice.

Gates, cameras, and hardware

Yardlaunch is not liable for a gate, camera, lock, sensor, or other hardware failure, including a failure to open, close, record, or alarm. Yardlaunch is not liable for theft, vandalism, weather, or other damage at the yard, or for a loss that follows a hardware failure.

The facility chooses and maintains its own hardware. A command sent by the software can fail, and a failed command can leave the hardware as it was. The facility keeps its own security plan and does not rely on the software as a guard.

Limit of liability

If Yardlaunch is found liable for a claim about the software, the total for all claims is limited to the fees the facility actually paid Yardlaunch for the software in the 12 months before the claim. If the facility paid no fees in those 12 months, the total is zero to the extent the law allows.

Yardlaunch is not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost guests, or a failed lien or auction. These limits apply to the extent the law allows. They cover claims about the software, a data incident, and a hardware result described above.

Guest data

The facility owns its guest data, including names, contact details, agreements, invoices, and gate history that the facility enters or collects. Yardlaunch processes that data only to provide the software to that facility. Yardlaunch is the processor. The facility is the one that decides why the data is used.

Yardlaunch does not use one facility's guest data to market to another facility's guests, and it does not build a marketing list across facilities. Yardlaunch does not sell guest data.

Yardlaunch keeps administrative and technical safeguards appropriate to the data it holds for the facility. This draft does not name a certification. If Yardlaunch confirms a security breach that affects the facility's guest data, it will notify the facility without undue delay, and no later than 72 hours after that confirmation, so the facility can meet its own notice duties. Counsel should confirm that clock before this draft is final.

Subscription, fees, and take-rate

The facility pays the subscription fee and any take-rate shown in its Yardlaunch account or on its invoice. A take-rate is a portion of guest charges the facility collects through the software. A default number stored on a new facility record is not a quote. The amount on the invoice or in the written order controls.

Fees already billed stay billed if a rate changes later. The facility is responsible for taxes on its own guest charges. Unpaid fees can lead to suspension of the software after notice. Suspension does not move guest data to another facility.

Ending the subscription and export

Either party may end the subscription as the invoice or order describes, or, if that writing is silent, with 30 days' notice. Yardlaunch may end it sooner if the facility does not pay, or if the facility uses the software to break the law.

Within 30 days after the subscription ends, Yardlaunch will export the facility's guest data in a common machine-readable format if the facility asks in writing. After that export window, Yardlaunch deletes the guest data it no longer needs to keep for a legal duty, a payment record, or an open dispute. Ending the subscription does not erase a fee that was already earned.

Indemnity

The facility will defend and indemnify Yardlaunch and Longyards from claims, losses, and reasonable legal costs that come from the facility's guests, its access decisions, a lien or auction, the condition of the yard, or the facility's breach of this agreement. This adds to the limit of liability above.

Staff sign in