Cookie Policy

This page lists every cookie CrowdCue sets, what each one holds, and how to clear them.

The cookies we set

Attendee identity: cc_aid

• What it does. Holds a random identifier so the service can tell that two votes came from the same browser. That is what makes one-vote-per-question possible without asking anyone to create an account, and it is how the app knows which questions are yours.
• What is in it. A random value and a signature. No name, no email, no IP address, nothing derived from you or your device. It is stored in our database only as a one-way digest that differs for every event.
• How long. Up to 180 days.
• Flags. httpOnly, so page scripts cannot read it, and SameSite=Lax, so it is not sent from other sites.

Sign-in session: Supabase authentication

• What it does. Keeps an organizer signed in after they enter their six-digit code, so they do not have to sign in on every page.
• Who sets it. Supabase, the authentication provider behind CrowdCue.
• How long. For the length of the session, refreshed while you stay active, until you sign out.
• Attendees never get this cookie. Joining an event does not create an account.

Product analytics by Microsoft Clarity

• What it does. Clarity records how the product is used so we can find what is confusing or broken: which features get used, where people stop, and replays of anonymised sessions showing clicks, scrolling and navigation.
• Cookies it sets. _clck keeps a Clarity identifier for up to a year and _clsk groups one visit together for a day. Microsoft also sets its own identifiers, including MUID, MR, SRM_B, ANONCHK and CLID, which it uses across Microsoft services.
• Who gets the data. Microsoft, as an independent controller under its own privacy statement. It is not strictly necessary for CrowdCue to work, and blocking it costs you nothing.

What we do not use

• No advertising or retargeting cookies set by CrowdCue.
• No third-party social or embedded-widget trackers.
• We never sell any of it.

One honest caveat. The Microsoft identifiers listed above are set across Microsoft services, so while CrowdCue does no cross-site profiling of its own, we cannot promise Microsoft does none on its side. If that matters to you, block the cookies as described below. Everything CrowdCue itself does keeps working.

Clearing them

You can delete cookies at any time in your browser settings, and block them entirely if you prefer. Two consequences worth knowing:

• Clearing cc_aid permanently severs the link between you and questions you have already asked. You will be able to upvote things you have already upvoted, and the app will stop marking your own questions as yours. Nothing you posted is deleted.
• Blocking cookies entirely means an organizer cannot stay signed in, and voting limits cannot be enforced for you.
• Blocking the Clarity and Microsoft cookies costs you nothing. Asking, voting and running an event all work exactly the same without them.

Changes

If we add a cookie, this page changes before it ships, and the date at the top will show when. Questions to apps@tanayarya.com.