Cookie Policy
Effective date: 20 August 2026 · Version: 2026.08.20
This Cookie Policy explains how HOSPIVERSE INNOVATIONS (OPC) PRIVATE LIMITED uses cookies, browser storage, pixels and similar technologies on Hospiverse.
1. What These Technologies Are
Cookies are small data files stored by a browser. Local/session storage and similar tools may store preferences or identifiers without using a traditional cookie. We use "cookies" in this Policy as a convenient collective term.
2. Categories
- Strictly necessary: These support security, authentication, session continuity, fraud prevention, load balancing and recording your cookie choice. They cannot be disabled through our preference centre because the requested service may not function without them.
- Functional: These remember optional preferences such as interface choices. They are used only where enabled by configuration or choice.
- Analytics: These help measure page use, navigation, device/browser type, approximate geography, performance and errors. Hospiverse currently operates Google Analytics as an essential measurement tool needed to operate, secure and improve the Platform, so it is treated as Strictly Necessary and is not gated behind a separate Analytics opt-in — see the schedule below.
- Marketing: Hospiverse does not currently intend to use cross-site advertising cookies. If marketing/advertising cookies are introduced, they will remain off unless the visitor makes the required choice and this Policy is updated.
3. Current Technology Schedule
| Provider / Technology | Category | Purpose | Typical Duration |
|---|---|---|---|
Hospiverse consent record (hospiverse_cookie_consent or replacement) | Strictly necessary | Stores cookie-category choice and policy version | Up to 12 months |
| Supabase authentication/session storage | Strictly necessary | Sign-in, session and account security | Session or configured account duration |
| Hospiverse security/session controls | Strictly necessary | Security, routing and abuse prevention | Session to 12 months depending on function |
| Razorpay checkout/mandate technologies | Strictly necessary when checkout is requested | Secure payment, mandate, fraud prevention and transaction processing | Set by Razorpay and legal/payment requirements |
Google Analytics (incl. _ga and related properties) | Strictly necessary | Aggregated/pseudonymous usage and performance measurement, used to operate and secure the Platform | Configured for up to 14 months |
The exact technical name may change when a provider updates its service. The category and purpose stated here control; we will update this table for a material new use.
4. Your Choices
On first visit, you may choose:
- Essential Only, which rejects optional Functional and Marketing technologies; or
- Accept Selected/Accept All, according to the categories shown.
Strictly necessary technologies, including the Google Analytics measurement described in the schedule above, are not subject to this choice and remain active in both cases. Rejecting optional cookies must be as easy as accepting them. You can change your choice through the persistent Cookie Settings link in the footer. A change applies prospectively and triggers removal/disablement of optional identifiers where technically possible.
Browser controls may also block/delete cookies, but they are not a substitute for our preference control. Blocking necessary storage may prevent sign-in, checkout or security functions.
5. Third-Party Pages
Opening WhatsApp, LinkedIn, Instagram, Razorpay or another external page may allow that party to apply its own technologies under its policy. Hospiverse's preference centre cannot control storage placed on an independent domain after you choose to leave Hospiverse.
6. Do Not Track and Global Signals
Browser "Do Not Track" signals are not uniformly standardised. Where technically supported and legally required, we will honour recognised consent-withdrawal or privacy signals. The Cookie Settings control remains the primary choice mechanism.
7. Changes
We will update this Policy and the preference interface before using a materially new optional category or purpose. A consent previously given for Analytics is not consent to unrelated advertising.