Privacy policy
Updated 9 September 2026
Who we are and how to contact us
Zelax Villa operates this website for Aashiyana in Lonavala. You can explore the villa without an account, send a stay request, or use a private guest workspace before, during and after your stay. We use the information you provide to manage requests and arrangements and to help you during your visit. For privacy questions or requests about your information, email harsh@zelax.club. The website does not process payments.
Stay requests, profiles and private feedback
Submitting Plan a stay sends your name, email, phone number, dates, guest count, occasion and notes to our server and saves them in Firebase. The workspace also stores the preferences, itinerary, service requests, arrival confirmation and private feedback you submit, together with host replies, reservation status, quotes and stay instructions. A signed-in profile can save your name and preferences for later visits. These records remain available after a page reload. We use them to respond, prepare the stay, manage services and follow up. Your preferences, messages and feedback are shared within the private stay workspace and with the authorised host team; they are not published as public reviews. Only include information you are comfortable sharing for these purposes.
Phone sign-in and verification
Phone sign-in currently supports Indian (+91) numbers. Choosing phone sign-in uses Firebase Authentication and Google reCAPTCHA to send a verification SMS. Google stores your number for sign-in and abuse prevention across its services. SMS or data charges may apply. Keep verification codes private. You can instead use your private stay link.
Private stay access and existing arrival links
A private stay link gives access to the associated stay, including its details and the guest actions available in that workspace. Anyone holding it can use that access, so share it only with people you authorise. We remember the link access in this tab’s sessionStorage. Verified account contact details can connect matching stay requests to your account. The new workspace retrieves private records from the server and does not add them to the public offline cache. Existing /stay/ arrival links use a separate guest app that may keep previously opened booking details offline. On a shared device, sign out and clear site data after use. Clearing browser data does not delete server records; email harsh@zelax.club for help with your records or a disclosed link.
Gathering enquiries by WhatsApp or email
The separate Gatherings form prepares your name, date, expected attendance, occasion, timings, space preference, overnight-stay interest and optional notes on your device. That form does not save or transmit its contents to our server. Choosing WhatsApp or email opens a prepared message; you review and send it using that service. After you send it, we use the information to reply, discuss suitability and pricing, and manage the requested arrangements. This handoff differs from Plan a stay, which saves a request in Firebase. Do not include payment details or identity documents in either form.
Optional website measurement
Google Analytics, linked to our Firebase project, runs only after you allow analytics in Cookie choices. It receives public page visits and actions such as opening Airbnb, directions or an enquiry handoff, together with technical browser and connection information. Our custom events exclude enquiry contents, names, contact details, travel dates, URL query strings and private stay links. A booking-link click is not a completed reservation; an enquiry handoff is not proof that a message was sent. Advertising measurement requires a separate choice when available; personalized advertising stays off. You can withdraw consent using Cookie choices in the footer. Google processes measurement under its own policies and account retention settings.
App installation and optional notifications
Installing the website adds a shortcut and offline essentials on your device. It does not enable notifications or analytics. Choosing Enable notifications asks your browser for permission. Firebase Cloud Messaging then uses a browser registration token, installation identifier and your chosen language to deliver occasional villa news, experiences and offers. The subscription endpoint adds that token to the selected public-news topic; it does not store it in a guest database or associate it with enquiries. Firebase keeps the delivery registration until it is deleted or expires under its service rules. Turn notifications off in Zelax on your phone in the footer to unsubscribe this device; browser site settings can also block delivery. Clearing website data removes offline files and local preferences.
Technical data and display preferences
Firebase, Google and our hosting services may process IP addresses, browser details, page requests and security logs to deliver and protect the website and guest workspace. Display choices apply in the current session unless you enable “Remember on this device”; then your motion, text-size and contrast choices are stored in your browser for up to 180 days. These display choices are not sent to our guest database. Stay and profile preferences are different: when you save them in the workspace, they are stored on the server for you and the host team.
Services, retention and your choices
Firebase and Google provide hosting, database, authentication and optional messaging or measurement services. Airbnb, WhatsApp, Google Maps and email providers handle information under their own policies when you use them. We retain guest records and correspondence as needed for your request, stay, follow-up and applicable record-keeping requirements. Closing a tab, checking out, signing out or clearing browser storage does not automatically delete server records. Email harsh@zelax.club to request access, correction or deletion of information held for your stay or account; any limits on deletion will be explained. Clear display choices in Accessibility & preferences and withdraw optional measurement in Cookie choices. This notice will change if our use changes.