1. What cookies are
A cookie is a small text file a website stores on your device. It lets the site remember things between page loads — that you are signed in, for example, or which city you selected.
We also use two related browser technologies: sessionStorage, which holds a random session identifier used to join up analytics events within a single visit and is cleared when you close the tab, and localStorage, which we use only to remember your preferences.
2. Cookies we set ourselves
2.1 Strictly necessary
These make the site work. They cannot be turned off, because without them you could not stay signed in or submit a form safely.
- next-auth.session-token — keeps you signed in. Expires after 30 days or when you sign out.
- next-auth.csrf-token — prevents cross-site request forgery on sign-in and form submission. Expires with the session.
- next-auth.callback-url — returns you to the right page after signing in. Expires with the session.
- __Host-next-auth.csrf-token — the secure variant of the CSRF token, set over HTTPS.
2.2 Functional
These remember choices you made so you do not have to repeat them.
- wk_session_id (sessionStorage) — a random per-visit identifier used to join analytics events into a single session. Contains no personal data and is cleared when you close the tab.
- wk_city (localStorage) — the city you last selected, so the site opens on it next time.
3. Third-party cookies
These are set by other companies when their services are enabled on the site. Each is listed with what it does and where to read their policy.
3.1 Analytics
We use one analytics provider at a time, not several. IP anonymisation is enabled.
- Google Analytics (_ga, _ga_*) — measures page views and aggregate traffic patterns. Expires after 2 years. Policy: policies.google.com/privacy
- PostHog (ph_*) — product analytics, used as a privacy-preserving alternative to Google Analytics where configured. Expires after 1 year. Policy: posthog.com/privacy
3.2 Payments
Set only on vendor billing pages, when a payment is initiated.
- Razorpay (rzp_*) — fraud prevention and payment session integrity during checkout. Policy: razorpay.com/privacy
4. What we deliberately do not use
Wedding planning generates unusually sensitive intent data — your wedding date, your budget, your city. We have chosen not to monetise that through advertising, which means we do not set:
- Advertising or retargeting pixels (Meta Pixel, Google Ads remarketing, and similar)
- Cross-site tracking cookies that follow you to other websites
- Data-broker or audience-selling tags
- Session recording or heatmap tools that capture what you type
5. How to control cookies
5.1 In your browser
Every major browser lets you block or delete cookies. Blocking strictly necessary cookies will prevent you from signing in, but the public marketplace — searching vendors, reading reviews, comparing prices — works without any cookies at all.
- Chrome: Settings → Privacy and security → Third-party cookies
- Safari: Settings → Safari → Block All Cookies
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Edge: Settings → Cookies and site permissions
5.2 Do Not Track and Global Privacy Control
We honour the Global Privacy Control (GPC) signal: when your browser sends it, analytics scripts are not loaded at all. We also respect the older Do Not Track header the same way.
6. Changes
If we add a cookie or a new third-party service, this page is updated before it goes live. Questions go to hello@wedderskart.com.
Questions about this policy?
Write to hello@wedderskart.com or 3rd Floor, Prestige Tech Park, Marathahalli, Bangalore, Karnataka 560103, India. We respond to written queries within 30 days as required under Indian law.
See also: Privacy · Terms · Refunds · Vendor Agreement · Cookies