Privacy Policy
Your privacy matters. This policy explains how New Leaf Properties collects, uses, and protects your information.
Effective Date: March 26, 2026
Last Updated: November 6, 2026
New Leaf Properties (“New Leaf Properties,” “we,” “us,” or “our”) operates the websites tfrooms.com, twinfallsroomsforrent.com, nlprent.com, rentnlp.com, renttf.com, twinmotels.com, tfapollo.com, montereytf.com, parktf.com, elranchotf.com, dunestf.com, deluxetf.com, jonestf.com, oldtownetf.com, downtowntf.com, 760maintf.com, kimberlytf.com, moteltf.com (collectively, the “Sites”). This Privacy Policy describes how we collect, use, disclose, and safeguard your personal information when you visit our Site, use our services, or interact with us in any capacity.
By using our Site or providing us with personal information, you consent to the practices described in this policy. If you do not agree, please do not use our Site.
1. Information We Collect
1.1 Information You Provide Directly
We collect personal information you voluntarily provide when you:
- Submit a booking or contact form: Name, email address, phone number, preferred property, room type preference, check-in date, and special requests.
- Submit a guest registration request: Full name, date of birth, current address, employer, phone, email, property and room preferences, duration of stay, number of guests, pet information, purpose of stay, digital signature, and typed name confirmation.
- Submit a career application: Full name, email, phone, position of interest, resume/cover letter content, digital signature, and typed name.
- Schedule a viewing: Your name and phone number, given to us over the phone. Viewings are arranged by phone and we do not collect viewing requests through this Site.
- Contact us directly: Any information you share via phone, email, text message, or in-person at our office.
1.2 Information Collected Automatically
When you visit our Site, certain information is collected automatically:
- IP address and approximate geographic location
- Browser type, version, operating system, and device type
- Pages visited, time and date of visits, time spent on pages, and click patterns
- Referring URL (the page that linked you to our Site)
- Accessibility preferences (text size, contrast mode, dark mode) stored in your browser’s local storage
1.3 Information from Third Parties
We may receive information about you from third-party platforms where our properties are listed, such as Google Hotels or Yelp, when you interact with our listings on those platforms.
2. How We Use Your Information
We use personal information for the following purposes:
- To process and respond to guest registration requests, booking requests, and inquiries
- To communicate with you about room availability, reservations, payments, and services
- To process employment applications and contact job candidates
- To manage guest relationships, including payment collection and maintenance requests through Gearco
- To improve our website, services, and overall guest experience
- To analyze website traffic, usage patterns, and marketing effectiveness
- To ensure the security and integrity of our Site and properties
- To comply with legal obligations, resolve disputes, and enforce our agreements
3. Third-Party Services
We use the following third-party services that may collect or process your data:
3.1 Gearco (Property Management)
Our properties use Gearco CPMS for guest check-in, payment collection, payment processing, maintenance requests, and stay management. When you become a guest, your information is entered into the Gearco system. Gearco is PCI DSS compliant and uses bank-level encryption. Their privacy practices are governed by their own privacy policy at gear.co.
3.2 Netlify (Website Hosting & Forms)
Our Site is hosted on Netlify, which processes form submissions (booking request, guest registration request, career application). Form data is transmitted over HTTPS and stored securely on Netlify’s servers. See Netlify’s Privacy Policy.
3.3 Google Services
- Google Analytics 4: We use Google Analytics to understand how visitors use our Site and our property sites. It sets the
_gacookies described in our cookie policy; it is not loaded when your browser sends a Global Privacy Control or Do Not Track signal or when you chose Reject All on the first-visit notice. Google Signals is off and reports are kept for 14 months. You can also opt out with the Google Analytics Opt-out Browser Add-on.
3.4 Microsoft Clarity
We use Microsoft Clarity for session replay and heatmap analytics to help us understand how visitors interact with our Site and improve usability. Strict masking is on, so text and form entries are replaced by placeholders before they leave your browser; Clarity is not used to identify you: it receives your IP address for a rough location, browser details and your movements on the page, never your name or what you type, and Microsoft keeps recordings for 30 days (a small random sample, and any we mark as favourites, for up to nine months; heatmap and aggregate data longer). Google Analytics, Clarity and the Meta Pixel are all loaded through Google Tag Manager, a Google loader that sets no cookies of its own. See Microsoft Clarity Privacy.
3.5 Meta Pixel and Conversions API (Meta Platforms, Inc.)
Loaded on every page to measure our Facebook and Instagram advertising and to show a reminder ad to people who visited this site or one of our property sites; not loaded when your browser sends a Global Privacy Control or Do Not Track signal or when you chose Reject All on the first-visit notice. Our cookie policy lists exactly what it receives. On our property sites, sending the reservation form also has our server send Meta a copy of that one request through Meta’s Conversions API, with your name, email address and phone number hashed rather than in plain text, so that it is counted even when the pixel was blocked; it is not sent when your browser sends a Global Privacy Control or Do Not Track signal, and each property site’s cookie policy lists exactly what it contains. tfrooms.com itself sends Meta no such copy. See Meta’s Privacy Policy.
4. Cookies & Local Storage
Our Site uses the following storage mechanisms:
- Cookies: First-party analytics cookies from Google Analytics (
_ga) and Microsoft Clarity (_clck,_clsk), and the Meta Pixel’s_fbpand_fbcadvertising cookies, all described in our cookie policy; none of them is set when your browser sends a Global Privacy Control or Do Not Track signal or when you chose Reject All on the first-visit notice. You can manage cookies through your browser settings. - Local Storage: We store your accessibility preferences (text size, dark/light mode, high contrast, reduce motion, reading guide, link highlighting) in your browser’s local storage. This data stays on your device and is never transmitted to our servers.
Our Site functions without cookies if you choose to disable them, though analytics and some embedded features may be affected.
5. Data Sharing & Disclosure
We do not sell, rent, or trade your personal information to third parties for marketing purposes. We may share information in the following limited circumstances:
- Service providers: With trusted third-party services (listed in Section 3) that help us operate our Site and business.
- Advertising measurement: With Meta, only through the pixel and, on our property sites, the server copy of a reservation request, both described in Section 3.5 and in our cookie policies; neither happens when your browser sends a Global Privacy Control or Do Not Track signal, and on this site nothing goes to Meta after you chose Reject All.
- Legal requirements: When required by law, court order, or governmental authority.
- Business protection: To protect the rights, property, or safety of New Leaf Properties, our guests, or the public.
- Business transfers: In connection with a merger, acquisition, or sale of assets, in which case your data would be transferred to the successor entity.
6. Data Security
We implement reasonable administrative, technical, and physical safeguards to protect your personal information, including:
- HTTPS encryption on all pages
- Secure form submission through Netlify
- PCI-compliant payment processing through Gearco
- Limited employee access to personal data on a need-to-know basis
- Regular security reviews of our hosting and third-party integrations
No method of electronic transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.
7. How Long We Keep It
Enquiries that do not become a booking: about a year, then deleted. Guest and booking records: kept for as long as the tax, lodging and business record rules require. Website server logs: our host’s ordinary short retention cycle, used to keep the sites online and to spot abuse. Accessibility preferences: never retained by us at all, because they stay in your own browser.
8. Privacy Laws People Ask About
We would rather tell you where you actually stand than imply a compliance department that does not exist behind a small family business.
California. The CCPA and CPRA apply to businesses far larger than this one, so as written they do not cover us. We will still honour a California resident’s request to know, delete or correct, using the contact details above. We do not sell personal information. Loading the Meta Pixel, and on our property sites our server’s copy of a reservation request to Meta, are the only things we do that could count as “sharing” for cross-context behavioural advertising under the CPRA, so we give you the opt-out anyway: send a Global Privacy Control or Do Not Track signal from your browser and the pixel is never loaded and our server sends Meta nothing about your reservation.
Europe and the United Kingdom. We operate motels in Twin Falls, Idaho. We do not offer services in the EU or the UK and we do not monitor anyone’s behaviour there, so the GDPR and UK GDPR do not ordinarily reach us. If you are there and have contacted us anyway, you can still ask for access, correction, deletion or portability, or object to our use of your information, and we will deal with it.
9. Data Retention
We retain personal information for as long as necessary to fulfill the purposes described in this policy:
- Booking and contact form submissions: Retained for up to 12 months or until your request is fulfilled.
- Guest registration data: Retained for the duration of your stay plus 12 months after checkout.
- Career applications: Retained for up to 12 months to consider you for future openings.
- Analytics data: Google Analytics event data is kept for 14 months; Clarity recordings follow Microsoft’s retention (30 days for recordings).
10. Your Rights
You have the right to access the information we hold about you, the right to correct anything that is wrong, the right to delete what we are not legally required to keep, the right to portability of your data, and the right to opt out of marketing contact from us.
Ask at newleafmotels@gmail.com or (208) 733-2010. You do not need to give a reason, and you will not be treated differently for asking. We respond within 30 business days.
11. Idaho Privacy Rights
Idaho does not currently have a comprehensive state privacy law equivalent to California’s CCPA or Virginia’s CDPA. However, we voluntarily extend the rights described in Section 10 to all visitors regardless of location. If Idaho enacts privacy legislation in the future, we will update this policy to comply.
12. Children’s Privacy
Our sites are not directed to children under 16, and we do not knowingly collect data from children. That is a broader commitment than the United States Children’s Online Privacy Protection Act, COPPA, requires: COPPA sets its threshold at children under 13, and we hold ourselves above it.
If you believe a child has sent us information through one of our sites, email us and we will delete it.
13. Contact Us
To contact us about privacy questions, or to make any request on this page, email newleafmotels@gmail.com or call (208) 733-2010. There is no privacy department and no data protection officer; the owner answers these directly.
Mail: New Leaf Properties, P.O. Box 2611, Twin Falls, ID 83303.
14. Advertising
We advertise on Facebook and Instagram and measure those ads with the Meta Pixel and, for reservation requests on our property sites, Meta’s Conversions API (Section 3.5 and our cookie policy). To opt out, send a Global Privacy Control or Do Not Track signal from your browser, choose Reject All on this site’s first-visit notice (this site only; on the property sites, use Global Privacy Control or Do Not Track), or turn off ad personalisation in your Facebook or Instagram settings. This site does not currently display Google AdSense advertisements; if that changes, these services may use cookies and similar technologies to serve ads based on your prior visits to this site or other websites. Google uses cookies such as the DART cookie to serve ads based on your activity. You can opt out of personalized advertising by visiting Google Ad Settings. For more information about how Google uses data, visit policies.google.com/technologies/partner-sites.
15. Changes to This Policy
We may update this Privacy Policy periodically. Changes will be posted on this page with an updated “Last Updated” date. Material changes will be highlighted on our Site. We encourage you to review this policy regularly.
16. AI Assistants and the TF Rooms Connector
TF Rooms is our connector for AI assistants at https://tfrooms.com/mcp. Our connector documentation explains its search, pricing and two-step booking tools. This section covers the connector; the rest of this policy also applies to a reservation made through it.
- What we collect and why: Searches use dates, room type and property. A booking requires the guest’s name, email address and contact phone number, plus the stay details; guest count and notes are optional. We use these to verify the email, reserve a room, contact the guest, enforce stay and abuse limits, and manage the reservation. No payment details or online signature are collected by these tools.
- Where it is stored and who sees it: The hub relays requests over an authenticated connection without a separate reservation database. It stores portfolio timestamps and counts without guest details, plus separate keyed hashes for email-code limits and short contact markers. The staff desk retains its existing snapshot cache for up to 30 seconds. Booking intents, verification state, property limits and reservations are stored by the properties alongside their inventory records. Staff see the reservation in the desk system and receive notices; our email service processes the messages it delivers. Starting a booking does not read stored stays or use contact history; the phone has no role in a limit before the email code is proved. After verification, checks match only the proved email across properties to apply overlap, reservation and 30-continuous-day limits. One night away does not reset the continuous-stay limit. A phone-only match does not affect the answer or hold and is noted only on the signed-in desk, never in email or tool answers. A contact-based refusal never includes stored dates, counts or another property. A property that cannot be checked is named in the reservation for staff review before confirmation.
- Codes and retention: Unverified booking and cancellation codes expire after 15 minutes. Codes are stored as salted hashes, deleted when verified; expired records are removed on the next state-changing booking operation or the cleanup scheduled every 15 minutes. An identical start while its intent remains open returns the same booking_id without another email; that booking_id can resend the code. A start with any changed detail replaces the earlier unproved intent at the same property and invalidates the old code only after its new code is sent; a failed send leaves the earlier code usable. A keyed verification receipt and reservation summary are retained for 400 days to return the same result on a retry, without retaining the original code or salt. Verified operations may retain recovery data for up to 24 hours after the intent expires. Booking and portfolio cancellation-code counters use rolling 24-hour windows; per-reservation cancellation counters use rolling 24-hour windows, and lookup counters use one-hour windows. Uncertain email delivery conservatively retains a temporary allowance until its accounting window passes. Contact markers expire within 30 seconds and are released when confirmation finishes. A refused hold erases its pending reservation data; cleanup erases a pending record with no inventory row after 24 hours. Empty storage markers may remain without guest data. Actual reservation records remain in the existing booking store under Sections 7 and 9; actual reservation records are not automatically deleted by the connector.
- Your conversation: The connector receives only the inputs sent for each tool, not your conversation with the assistant. Your assistant provider handles that conversation under its own privacy policy.
- What is logged: The connector booking path logs references and fixed reasons, never guest names, email addresses, full phone numbers, notes or codes. Netlify processes each request and keeps ordinary hosting logs under the retention description in Section 7. Dates sent in availability request addresses can appear in hosting logs. The MCP endpoint sets no cookies and runs none of the analytics or advertising tools in Sections 3 and 4.
- Booking and cancellation: Starting a booking sends an email code and holds no room. Configurable hourly and rolling 24-hour code ceilings apply; if the hub counter cannot confirm and record the allowance within two seconds, no code is sent and chat booking is briefly paused. Reaching a booking ceiling returns the requested stay link and property phone. Reservation notices never use code allowances. Chat reservation notices are retried for at least 36 hours after a delivery failure; signed web-form notices retain their direct-send behavior. Confirming the code can reserve an available room awaiting staff confirmation within 24 hours; success means the room is held. After starting over, the same proved email and identical property, room type and dates return the existing non-cancelled chat reservation that still holds a room without another room or another set of notices. Bring photo ID and sign the guest agreement at check-in. The existing web form remains available. To check a reservation, use its number and the last four phone digits. To cancel in the assistant, request a cancellation code and confirm it; automated cancellation is available more than 48 hours before check-in during office hours. Cancellation codes have a separate budget of three per reservation in a rolling 24 hours and, by default, five across the portfolio in a rolling 24 hours, independent of booking traffic. If that budget is reached or cancellation is unavailable, the answer explains cancellation by phone and gives the property phone, never a booking link. The published cancellation policy applies; the connector takes no payment and processes no refund. To change dates, cancel and rebook.
© 2026 New Leaf Properties. All rights reserved. This privacy policy applies to tfrooms.com and all related domains: twinfallsroomsforrent.com, nlprent.com, rentnlp.com, renttf.com, twinmotels.com, tfapollo.com, montereytf.com, parktf.com, elranchotf.com, dunestf.com, deluxetf.com, jonestf.com, oldtownetf.com, downtowntf.com, 760maintf.com, kimberlytf.com, moteltf.com.