Cookie policy
What we store in your browser, what it is for, and what you can switch off.
Last updated
01The short version
We use a small number of cookies to make bookings and payments work. Those cannot be turned off, because without them the site cannot hold your seats or keep you signed in.
We also use Meta (Facebook) advertising cookies to measure how well our ads work. For visitors in India they are ON by default. Everywhere else they are OFF unless you accept them. Wherever you are, you can turn them off at any time from the Cookie settings link in the footer.
We also use Google Analytics to understand how people find and move around the site. It follows the same rule as the advertising cookies: on by default in India, off unless you accept everywhere else, and the same Cookie settings link turns it off.
We do not use Tag Manager, session recording, heatmaps, or any other analytics tool. There are two optional trackers on this site and both are listed below.
02Strictly necessary (always on)
These run whatever you choose, because the site cannot function without them:
- Sign-in session cookies (names beginning sb-): keep you signed in to your account or the partner portal. Set by Supabase, our authentication provider. They last for the length of your session or until you sign out.
- nss-persist: remembers whether you ticked 'keep me signed in'. Session-length.
- nss-cookie-consent: stores the choice you make about the cookies on this page, in your own browser. Without it we would have to ask you on every visit.
- nss-partner-sidebar-collapsed: remembers whether a travel agent collapsed the portal sidebar. Partner portal only.
- nss-agent: for travel agents only, stores your agency name so the site header can show your account instead of a sign-in link. It is not a sign-in credential and grants no access on its own. Cleared when you sign out; otherwise session-length, or 30 days if you ticked 'keep me signed in'.
- nss-agent-logo: for travel agents only, stores the web address of the logo you uploaded, so the header can show it. Kept in your browser's local storage, never sent to us, and cleared when you sign out.
Razorpay, our payment provider, also sets its own cookies while you are paying. Those are necessary to process the payment securely and are governed by Razorpay's own policy.
03Analytics (on by default in India, otherwise only if you accept)
When it is on, we load Google Analytics, which sets cookies beginning _ga to recognise a returning browser. It tells us which pages people visit, roughly where in the world they are, and which site or search sent them to us. We use it to decide what to write more of and what to fix.
What Google receives: the page you are on, how you got there, your approximate location, and your device and browser type. Google shortens IP addresses before storing them and we have no way to see your full address through this tool.
What it never receives: your name, phone number, email address or travel documents. We do not send any of those to Google, and Analytics is never loaded on booking, checkout, QR verification, account or partner pages, for the same reason the advertising pixel is not: the address of those pages is itself the key to your booking.
When it is off, Google Analytics does not load and sets no cookie.
04Advertising (on by default in India, otherwise only if you accept)
When it is on, we load the Meta pixel, which sets cookies named _fbp and _fbc and stores a small key in your browser to avoid counting the same event twice. These let Meta tell us which of our ads led to a booking.
What Meta receives as you browse: the page you are on, your IP address and browser details, which tour you looked at, any search or filter you used, a travel date if you pick one, and the number of travellers and indicative amount once you start a booking. Meta can link this to a Facebook or Instagram account if you have one.
For a completed booking only, and again only while it is on, our server also reports that one sale to Meta directly. This is how a sale still gets counted when your browser blocks the pixel. It includes the booking amount, the number of seats, the tour page, and your email address and phone number in scrambled (hashed) form, which lets Meta match the sale to an ad click without us handing over your actual address or number. We never send your name, your travel documents, or the private link to your booking.
Where it never runs: we do not load the pixel on booking pages, checkout, QR verification, account pages or the partner portal, and no advertising event is sent from them either. Those pages carry traveller names and document details, and their web address is itself the key to your booking, so neither the script nor the address ever reaches an advertiser. Where we do need to record that a checkout started or a payment began, our server reports just that step, attributed to the public tour page rather than to your private booking link.
When it is off, none of this loads at all, no advertising cookie is set, and nothing is reported to Meta from your browser or from our server.
05Changing your mind
Use the Cookie settings link in the footer of any page. Turning tracking off is exactly as easy as turning it on, and takes effect immediately. You can also clear cookies in your browser settings at any time.
How we tell where you are: from your device's time zone setting (India Standard Time). We do not look up your location for this.
One exception, for honesty: if you are part-way through paying when you withdraw, your choice as it stood when you pressed Pay is the one that applies to that single booking, so that one sale may still be reported. Everything after it follows your new choice.
Questions? Email info@northsikkimsharing.com. See also our privacy policy.
