Trip brief creation
With online delivery disabled, creating a trip brief runs on your device. Your entered information stays in the page’s memory and in any text file you choose to download; it is not submitted to an enquiry service.
If delivery is enabled
Submitting sends your name, mobile number (when supplied), travel period, traveler count and preferences to the configured server-side enquiry service. The operator must identify the recipient, lawful basis, retention period and privacy contact before launch. The application itself does not store enquiry content in a database.
Reservation checkout
Submitting checkout details stores your name, mobile number, travel choices, price snapshot and accepted policy in the booking database. A private access key is saved in this browser’s local storage. Demo records are labelled as simulations. In gateway mode, contact details are passed to Razorpay for payment processing; payment credentials are not stored by JaisalGo. The operator must set and enforce retention and deletion rules before real customer collection.
Technical data
The server uses a temporary process-local counter keyed to a request IP header to limit abuse, expiring after roughly one minute. Hosting providers can collect access logs under their own policies. Optional first-party analytics measure anonymous sessions and booking steps only after you allow them. Names, mobile numbers, full URLs and payment credentials are excluded. You can decline or withdraw through Privacy preferences. Sessions expire after 30 minutes of inactivity; anonymous event data is retained for 180 days. Necessary payment and booking records remain separate. No advertising analytics are installed.
Your choices
Only provide information needed for planning. Avoid sensitive health details; describe practical access needs instead. You can stop before sending or downloading. A verified privacy contact is not configured; real lead collection should remain disabled until one is published.