Cookie Policy
Last updated: 28 September 2026
This policy explains the cookies and browser storage KHEL-O ("we", "us") uses when you visit khel-o.online, and why. It should be read alongside our Privacy Policy.
1. We Don't Use Advertising or Tracking Cookies
KHEL-O does not run Google Analytics, Meta Pixel, or any third-party advertising/marketing tracker. We don't sell or share browsing data with ad networks, and we don't build advertising profiles of visitors.
2. What We Do Store, and Why
| Storage | Purpose | Type | Retention |
|---|---|---|---|
| Session/login tokens | Keeps you signed in between visits | Browser local storage (not a cookie) | Until you log out or the token expires |
| Selected city / location preference | Remembers the city you're browsing cafés in | Browser local storage | Until you change it or clear site data |
Anonymous session ID & referral source (e.g. utm_source) | Lets us see which channel (e.g. Instagram, Google, a referral link) brought a signup to the Platform, and count visits and which of our pages are opened, purely in aggregate. Not used to build a cross-site advertising profile. | Browser local storage | Until you clear site data |
Campaign details from the link you opened (utm_medium, utm_campaign, utm_content, or Meta's fbclid) | Tells us which of our posts, ads, QR codes or links you came from, so we can see which ones actually help people find and book a venue. Attached to the steps you take on KHEL-O (for example opening a venue, starting a booking, reaching payment, completing a booking) and counted in aggregate. We read only the tag in the link; we do not receive your Instagram or Facebook account details. | Browser local storage | 30 days after your last tagged visit |
| Device type & in-app browser | Worked out on our server from your browser's standard User-Agent header: phone, tablet or computer, and whether you opened KHEL-O inside the Instagram or Facebook app. Stored as that label only, to fix problems on the devices people really use. | Stored with the anonymous events above (not on your device) | With those events |
| Google Sign-In session cookie | Set by Google when you use "Sign in with Google" | Third-party cookie, set by Google, governed by Google's own policy | Controlled by Google |
| Razorpay checkout cookies | Set by Razorpay during the payment step, for fraud prevention on their end | Third-party cookie, set by Razorpay, governed by Razorpay's own policy | Controlled by Razorpay |
3. Error Monitoring
We use Sentry to catch and diagnose crashes and bugs. This can include a session identifier and technical logs tied to your browser session, used only to debug the Platform — never for advertising.
4. Your Choices
Most of what's listed above is local storage, not a tracking cookie, and you can clear it any time from your browser's site-data settings — though doing so will log you out and reset saved preferences. Third-party cookies set by Google or Razorpay during sign-in/checkout are controlled by those providers' own cookie settings, not ours.
5. Changes to This Policy
We may update this policy if what we store changes. Material changes will be reflected here with an updated "Last updated" date.
6. Contact
Questions about this policy? Reach us via the details on our Contact Us page.