Privacy Policy

1. Information handled by this website

The enquiry form asks for a name, Indian mobile number, pickup, destination, travel date and trip information. Email, return date, passenger count, vehicle preference and additional requirements are optional. Do not submit government identity numbers, payment-card details, health data or other sensitive personal information in the enquiry form.

2. Current enquiry handoff

In the default configuration, the form prepares a WhatsApp message and does not automatically email or store the enquiry. Your information is transferred to WhatsApp only if you choose to open and send that message. If the owner enables the secure server-side email endpoint, the form sends the enquiry to the configured business email through the selected transactional provider only after server validation; the website application does not store enquiry content in a database. The actual provider and retention configuration must be published here before email delivery is enabled. You may alternatively contact the business by phone or email. WhatsApp, email and telecom providers process information under their own terms and privacy notices.

3. Analytics and cookies

Google Analytics, Google Tag Manager and Google Ads tracking are not active until measurement IDs are supplied and configured. If configured, optional analytics scripts are held until you choose to allow analytics through the consent control. The site does not intentionally send names, phone numbers, email addresses or trip details to analytics.

4. Contact and questions

For a privacy question, contact Shukla Travels at shuklatravelsjabalpur@gmail.com or +91-93296 72540. Business address: House Number 12, Danav Baba, Sukun Homes, near Shakti Nagar, Sainik Society, Shakti Nagar, Jabalpur, Madhya Pradesh 482001, India.

5. Future form integrations

When the server-side email endpoint is enabled, source IP addresses are used temporarily in memory for rate limiting and are not saved by this application. Hosting and email providers may maintain their own operational logs under their privacy terms. Before production email delivery is activated, the owner must name the actual provider and confirm its retention, access controls and applicable privacy notices here. The optional backend performs server-side validation, a honeypot check and rate limiting; the default static build uses a WhatsApp handoff.