Cookie notice

1. The short version

We set two cookies of our own: one keeps you signed in (only when you sign in), and one lets your phone vote once a day in India’s Favourite Ganpati Bappa (only when you vote). Every page, mandal pages and invitations included, loads Google AdSense, which shows ads and may set Google’s advertising cookies. Our own pages (home, Explore, sign-up and the vote contest pages at /vote) also load Meta’s pixel to measure our ads, and Meta sets its own cookie there. Just visiting a mandal page or an invitation sets no cookie of ours and never loads Meta’s pixel.

2. The cookies we set

Name

sb-…-auth-token

Why

Keeps you signed in to your dashboard. Long sessions may split it into parts ending .0, .1.

When

Only after you sign in. Signing out removes it.

How long

Until you sign out, and at most 400 days.

Who

Set by utsavmandal.com through our sign-in provider, Supabase. Never shared with advertisers.

Name

um_vd

Why

Lets each phone or browser vote once a day in each contest of India’s Favourite Ganpati Bappa, and helps us catch rigging. We keep only a one-way code of it, never the cookie itself.

When

Only when you vote, on a mandal page or its own address. Page scripts can’t read it.

How long

At most 400 days.

Who

Set by utsavmandal.com, for utsavmandal.com and its mandal addresses. Never shared with advertisers.

3. Other things kept in your browser

These aren’t cookies. They stay in your browser’s storage and are never used for ads:

• um_vid: a random device number, so a mandal can see how many visitors come back. We only ever receive it as a one-way code, different for each mandal, deleted after 120 days. Clearing your browser’s site data removes it.
• um:view:… and um:site:…: stop one visit being counted twice in the same tab. They disappear when you close the tab.
• A note that you already sent a report from this tab, so the form isn’t sent twice. It also disappears with the tab.

4. Other services on some pages

• Google Maps: a mandal page with a location shows a Google map, and Google may set its own cookies when the map loads.
• YouTube and Instagram: videos and reels load only after you tap them; YouTube uses its privacy-enhanced mode. Those services then apply their own cookies.
• Google AdSense: on every page, mandal pages and invitations included. Google and its partners use cookies (such as __gads) to show ads, including ads based on your earlier visits to this and other sites. You can turn off personalised ads in Google’s Ads Settings; how Google uses this data: Google’s partner-sites policy.
• Meta Pixel: on our own pages only (home, Explore, the looks, the committee and invitation pages, sign-up and sign-in). Meta sets its _fbp cookie and receives the page you opened, so we can measure our Facebook and Instagram ads. Mandal pages, invitations and the dashboard never load it.
• Google Tag Manager and Google Analytics: on the same pages as Meta’s pixel, and only those. They tell us which of our pages people open and how they arrive, so we can improve them. Google may set its _ga cookies there. Mandal pages, invitations and the dashboard never load them. How Google uses this data: Google’s partner-sites policy.
• Cashfree Payments or Razorpay: their secure payment window, only while you pay for an own address.

5. Your choices

You can block or delete cookies and site data in your browser’s settings. Visitors need no cookie at all; without the sign-in cookie you can’t use the dashboard. Personalised Google ads can be turned off in Google’s Ads Settings. More about your data in our privacy policy.