Cookie Policy & Consent Notice
TravelnFlex Cookie Policy and Consent Notice
This Cookie Policy explains how SIFAKA LABS LLP, through the TravelnFlex marketplace, uses cookies, local storage, session storage, and similar technologies on the website and booking flow.
1. Short notice
TravelnFlex uses essential browser storage to keep the Platform secure, maintain login and booking flows, remember temporary checkout state, and support basic features. We also use first-party analytics storage to understand marketplace and checkout usage. We do not use advertising cookies or sell browsing information.
By using essential Platform functions, you agree that the technologies required for those functions may operate. Where applicable law requires consent for a non-essential technology, TravelnFlex will request consent before enabling it. You can withdraw optional analytics consent or clear stored data using the controls described below.
2. Technologies currently used
Essential authentication and security cookies
The Platform uses authentication and security cookies to maintain signed-in sessions, protect account actions, support logout, and complete secure account-linking flows. These cookies may be set by the customer application or its authentication provider and generally expire when the session ends or according to the configured security lifetime.
Without these cookies, account access, profile updates, bookings, payment verification, and protected support actions may not work.
Essential session storage
The booking flow uses browser session storage for temporary state such as a pending booking intent and the return path after profile completion. Session storage is normally removed when the browser tab or session ends and is not used as a permanent customer profile.
Essential or preference local storage
The Platform may use local storage for wishlist or preference state, a short-lived analytics session identifier, analytics deduplication, blog-view deduplication, and presentation preferences. These values are stored in the customer’s browser and are not payment credentials.
First-party analytics
TravelnFlex records limited marketplace and checkout events such as searches, filters, listing views, booking-flow actions, payment failures, and selected booking or package references. The analytics session identifier is generated in the browser, and duplicate events are suppressed for configured short periods. Analytics are best-effort and must not receive card numbers, CVV, UPI PINs, passwords, or other payment secrets.
Analytics may use local storage and send event data to the TravelnFlex analytics endpoint. If optional analytics consent is disabled or storage is unavailable, essential booking and account functions should continue to work, although analytics may be incomplete.
Payment and media providers
When a customer opens Razorpay Checkout, Razorpay may use its own cookies or similar technologies under Razorpay’s terms and privacy policy. TravelnFlex does not control Razorpay’s provider-side storage.
Profile or review images may be uploaded to Cloudinary or another configured media provider. That provider may use technical storage needed to deliver the media. Review the provider’s applicable privacy information where relevant.
3. What we do not use
Based on the current customer application, TravelnFlex does not intentionally use advertising cookies, cross-site behavioural advertising pixels, or cookies to sell or rent customer browsing profiles. If this changes, the Cookie Policy and consent mechanism must be updated before the new technology is enabled.
4. Consent and withdrawal
Essential authentication, security, session, and checkout technologies cannot be switched off while using the associated Platform function.
For optional analytics or other non-essential technologies, TravelnFlex will request consent where required. A customer may withdraw optional consent by:
- using the consent control shown by the Platform, where available;
- clearing TravelnFlex site data and local storage in the browser;
- blocking optional cookies or site storage in browser settings; or
- contacting support@travelnflex.com for a privacy request.
Withdrawing consent does not make earlier lawful analytics processing automatically unlawful or delete booking, payment, support, security, or legal records that must be retained. It stops or limits future optional processing to the extent supported by the Platform and applicable law.
5. Browser controls
Most browsers allow customers to view, block, delete, or restrict cookies and site storage. Blocking all cookies may prevent login, profile completion, booking, payment, or support functions from working. Clearing local storage may remove wishlist, temporary booking-intent, preference, or analytics-deduplication state.
Browser controls apply only to that browser and device. A customer may need to repeat the choice on another device, browser, or private browsing session.
6. Retention and data protection
Cookie and local-storage values remain for the duration configured for the relevant function or until the customer clears them. Server-side analytics, security logs, account, booking, payment, refund, support, and legal records are retained according to the TravelnFlex Privacy Policy and applicable requirements.
Do not place payment credentials, passwords, UPI PINs, CVV, or unnecessary medical or identity information into browser storage, analytics metadata, or support messages.
7. Third-party links
The Platform may load or link to third-party services, including payment, media, authentication, email, analytics, and infrastructure providers. Their storage and privacy practices are governed by their own policies. TravelnFlex will maintain a current production vendor list internally and update this notice when a new non-essential tracking technology is introduced.
8. Contact and changes
For questions, consent withdrawal, or privacy concerns, contact support@travelnflex.com.
SIFAKA LABS LLP
TravelnFlex marketplace
Badri Kedar Enclave, Zero Point, Nakronda, Dehradun, Uttarakhand, India - 248001
We may update this Policy when browser technologies, vendors, analytics, the booking flow, or applicable law changes. The latest version and date will be published on the Platform.