Privacy Policy / DPDP Notice

1. Information collected and why

• Passenger details: title, first and last names, date of birth and passport number if supplied. These details are stored with the booking to prepare and manage the requested reservation.
• Travel details: trip type, origin, destination, departure and return dates, travel purpose and existing-travel airline if supplied. These are used to prepare and manage the requested itinerary.
• Contact details: email and phone number, used for booking communications, document delivery, booking lookup and support.
• Booking and payment records: booking ID, amount, status, payment method, payment reference / UTR, issued reservation details and documents, and delivery status. These support order management, manual payment matching and customer assistance. FlyDummy does not ask for your UPI PIN, banking password or one-time password.
• Support enquiries: name, email, optional phone number, subject and message submitted through the contact form, used to handle your enquiry.

The initial booking form asks you to accept the Terms & Conditions and separately acknowledge this notice before submitting your booking details. Booking details are saved when you submit that form, before the final payment page. Required form fields are needed to submit the order through the current flow.

2. Access and service providers

Booking and payment records are available through the administration tools for payment review, reservation issuance and support. The website uses hosting, database/storage and transactional email services to operate the service, store records and send booking documents. Transactional emails contain booking information and may include PDF attachments. We do not sell personal data.

Your UPI app and payment provider process the payment under their own terms and privacy notices. FlyDummy receives the reference you submit for manual verification. If you choose to contact us through WhatsApp, that service also processes your communications under its own privacy notice. Please avoid sending unnecessary identity documents or sensitive financial credentials in support messages.

3. Browser storage and analytics

The website stores a booking access token in your browser’s session storage to let you view your booking in that tab. This is for booking access, not marketing permission. Google Analytics can load when enabled in the website configuration and may use cookies and collect usage and device information. The booking-form acknowledgement is not a cookie-consent control and does not manage analytics preferences.

4. Retention

The 48-hour reservation validity is not a data-deletion deadline. Booking, payment, support and document records can remain stored after the reservation expires. The current application does not automatically delete those records when the hold ends. To request deletion or ask about retention of your record, contact support using the details below. Any continuing need to retain information, including applicable legal requirements, must be considered when handling a request.

5. Privacy requests and concerns

You can contact us to ask about your personal data and its use, request access or correction, request erasure, or raise a privacy concern. Where processing relies on your consent, you can also request withdrawal of that consent. Withdrawal does not undo processing already carried out and may affect our ability to continue the service. Rights and any retention requirements depend on applicable law.

Email support@flydummy.com with the subject “Privacy request” and your booking ID if relevant. We may need to verify that you are authorised to make the request before disclosing or changing a record. Do not send passwords, UPI PINs or one-time passwords. This is the existing support address; no separate privacy or grievance contact is published in this notice.

6. Other passengers and children

If you provide another passenger’s details, make sure you are authorised to do so and share this notice with them. A parent or legal guardian should authorise submission of a child passenger’s details. The current booking form does not carry out a separate parent or guardian verification process.

7. Booking acknowledgement is not marketing consent

The initial booking form asks you to acknowledge that you have read this notice. It is separate from acceptance of the Terms & Conditions and does not authorise marketing messages. Both checkboxes are validated in your browser only; their values and an acceptance timestamp are not currently sent to the booking or payment APIs or saved with your booking. The booking flow does not offer a marketing subscription. A checkbox alone does not establish compliance with the Digital Personal Data Protection framework.