Lawler Lake House
Operated by Lawler Holdings LLC. Last updated October 26, 2026.
Shared Retreat is operated by Lawler Holdings LLC. We collect the email address you use to request a sign-in code, the display name on your profile, and the household and house memberships attached to that account.
If an owner invites you, the invitation stores that email and the invited role. Reservation records store arrival and departure dates, whether the stay is for the whole house or part of the house, bedroom count, status, and optional notes. Owner-created stays may store a typed guest name instead of a linked account.
The service also stores a delivery log of transactional emails (event type, house, and recipient address) so the same notice is not sent twice. Requesting a sign-in code can create an authentication account for that email. The product does not currently collect payment cards, government identification, precise location, photos, contacts, advertising identifiers, or uploaded files.
We use this information to operate the family calendar: show who reserved which nights, let members request stays, let owners approve or deny requests, invite or deactivate members, and send transactional email about those events.
Display names appear on reserved calendar days for other members of that house. Email addresses are used for sign-in, invitations, new-request notices, approval and denial notices, and replies to support or privacy requests. We do not use this information for advertising.
Access is by household and house, not by a public booking site. A person may belong to more than one house. Owners of a house can see pending requests for that house, including who submitted them. Family members see the shared calendar and their own requests.
Approved stays show the guest name and any family calendar note to other members of that house. Denied and cancelled stays are not drawn on the shared calendar. Pending stays may appear as busy days without the requester’s private note.
A requester may add a private note when asking for dates. That note is visible to the requester and to owners of that house. It is included on the owners’ new-request email. It is not shown on the shared calendar and is not included in approval or denial email.
An owner may add a private message when approving or denying. That message is visible to the requester and to owners. It is not shown on the shared calendar.
A family calendar note may be shown to members of the house only after a stay is approved.
Sign-in codes are sent by the authentication provider and use the Shared Retreat product name. They do not name a specific house.
After an owner invites someone, that address may receive an invitation email that names the house and links to that house’s public sign-in page. After a member submits a request, active owners of that house may receive a new-request email. After an owner approves or denies, the requester may receive a decision email.
Email send failures do not undo a saved invitation or reservation. Cancellations do not currently send email. Support and privacy replies are sent from the monitored address listed below, which is separate from transactional no-reply mail.
The website is hosted on Vercel. Authentication and the database are provided by Supabase. Transactional stay and invitation email is sent through Resend. Those providers process the information needed to deliver those services.
Website typefaces are packaged with the application through the Next.js font system. We do not add advertising or analytics scripts.
Payment processors, app-store billing, and mobile push-notification vendors are not used by the current application. If they are added later, this policy will be updated before those features are offered.
Account, membership, invitation, reservation, and email-delivery records are kept while they are needed to operate the household calendar. We do not publish a fixed number of days or years.
Backup, hosting-log, and email-provider retention periods are set by those providers and are not independently stated here. Copies of a stay that you add to a personal calendar file can remain on your devices after you leave the service.
Email support@sharedretreat.com to request access, correction, or deletion of your personal information. Those requests are handled manually and are not instant. Self-service deletion is not available unless the operator has explicitly enabled it for that website. It is not available by default. An owner can deactivate house access; that is not the same as deleting an authentication account or removing historical reservation rows the household still uses on the calendar.
A public delete-account page explains how to request deletion and what reservation history a household keeps.
For privacy questions, email support@sharedretreat.com. Do not send requests to transactional no-reply sending addresses.
House data is authorized by signed-in membership on the server. Calendar and reservation changes go through server-checked procedures. Family members cannot approve stays, invite others, or see other people’s private request notes on the shared calendar.
Service-role and email-provider keys are not shipped to the browser. This policy does not claim a security certification, audit, or specific encryption standard.
You must be at least 18 years old to create an account. We do not knowingly collect personal information from children under 18. If you believe a person under 18 has created an account, email support@sharedretreat.com.
These pages describe Shared Retreat, a family calendar and reservation service operated by Lawler Holdings LLC. Some families open the same service through a dedicated website that shows their house name. The website name is presentation only and does not grant house access.
For customer support and privacy requests, email support@sharedretreat.com.