Longyards
Privacy
Last updated September 24, 2026. Draft for attorney review.
This notice describes how Longyards uses Yardlaunch to handle information about guests and staff at its outdoor storage facilities in Florida and Ontario. It is a draft. It does not claim a privacy certification, and it is not a substitute for counsel's review under the laws that apply to those facilities.
Information we collect
From a guest application or a staff move-in, the app may store:
- Name, email, phone, company, and mailing address
- A photo of a driver's license, and whether staff verified that the address matches
- The rental agreement file, signature status, and preferred yard
- Vehicle, boat, RV, trailer, equipment, or container details kept on a yard
- Invoices, payments recorded by staff (method such as cash, check, card, or ACH, amount, and date), and late fees
- Gate check-in and check-out notes entered by staff
This release does not collect a full card number, card security code, or bank account number inside Yardlaunch. A staff member who types a card payment is recording that a card was used, not the card itself. Do not put a card number in a note.
Staff accounts store a name, an email, a role, and a password hash.
Why we use it
We use this information to review an application, prepare and store a rental agreement, bill for a yard, decide lock and gate access, operate the facility, and send emails or texts the guest agreed to or that relate to an open rental agreement. Payment reminders are part of that. We do not sell guest lists.
Email and text messages
The apply form asks for permission before it can be submitted. The permission covers email and texts about the application, the rental agreement, gate access, and payments, including payment reminders. Message frequency varies. Message and data rates may apply. Reply STOP to opt out of texts and HELP for help. Consent is not required to rent a yard. A guest who replies STOP should not receive further promotional or reminder texts; operational messages required to wind down a rental agreement should be reviewed by counsel.
The form blocks submission without that checkbox. This draft does not add a separate consent log in the database. Counsel should decide whether a stored timestamp is required before payment-reminder texts go live.
Who else handles it
Yardlaunch runs on Vercel, with the database on Neon (Postgres). When those features are turned on, email may be sent through Resend, texts through Twilio, and rental agreements through BoldSign. If error monitoring is turned on, Sentry receives technical error reports with personal data stripped (no guest name, email, phone, or card data). Each of those vendors is used to run the service. They should be listed in a processor schedule written by counsel. Leaving a vendor unset means the app does not call that vendor.
How long we keep it
Guest and payment records are kept for facility operations, unpaid balances, and the period counsel sets for tax, facility, and dispute records. A driver's license photo should not be kept longer than the facility needs it to verify identity. A retention schedule is part of the attorney review and is not final in this draft.
Security
Staff access is limited by role. The production site is served over HTTPS. Database backups and restore steps are described for operators in the internal operations runbook. These are ordinary safeguards. This notice does not claim a security certification.
Florida and Ontario
Guests of a Florida facility and guests of an Ontario facility may have different rights to access or correct their information, or to complain to a regulator. This draft does not restate those statutes and does not claim that the app meets them. A request can be sent to the draft contact below and should be handled under the process counsel approves.
Contact
Draft privacy contact, to be confirmed by counsel: privacy@yardlaunch.com.
