Skip to main content
ORGDECK← BACK TO HOME

Cookie Policy

Last updated August 15, 2026

1. Overview

This Cookie Policy explains what cookies and similar browser storage OrgDeck uses, and why. It supplements our Privacy Policy, which covers personal information more broadly. We keep this short on purpose: OrgDeck uses a small, fixed set of cookies to run the Service — nothing for advertising or tracking you across other sites.

2. What a cookie is

A cookie is a small piece of data a website asks your browser to store and send back on later requests. Because the web is otherwise stateless, cookies are what let a site recognize you from one page load to the next — for example, staying signed in without re-entering your password on every page.

3. Cookies we set

Session cookies (strictly necessary). When you sign in, our authentication provider (Supabase) sets a small set of cookies that identify your logged-in session on every request. These are essential — without them, the Service can't tell who you are, and features like your dashboard, organization roster, and operations couldn't work. They're cleared when you sign out, or expire automatically after a period of inactivity.

Equipped theme cookie (functional). If you own and equip a personal cosmetic theme from the Store, we set a cookie named orgdeck-accent so your chosen accent color renders correctly on your very first page load, before the page has a chance to check the database. It's HttpOnly (not readable by page scripts), stores only a 6-character color value, and lasts up to a year or until you unequip the theme, whichever comes first.

What we don't use: advertising cookies, third-party analytics/tracking cookies, or cross-site tracking of any kind. If we ever add analytics in the future, we'll update this policy first.

4. Other browser storage

Your light/dark theme mode preference is saved in your browser's local storage, not a cookie — it stays on your device and is never sent to our servers. It's used purely to remember your display preference between visits.

5. Cookies set by others

A few actions briefly take you to a page hosted by someone else, who may set their own cookies under their own policy — not ours:

  • Stripe — if you subscribe or make a purchase, checkout and billing management happen on Stripe's own hosted pages.
  • Discord — if you choose to sign in with Discord, the sign-in flow happens on Discord's own domain.

We don't control these cookies and recommend checking Stripe and Discord's own cookie/privacy policies if you want details.

6. Managing cookies

Most browsers let you view, delete, or block cookies through their settings. Since our session cookie is what keeps you signed in, blocking or deleting it will sign you out and may prevent you from using parts of the Service that require an account.

7. Changes to this policy

We may update this policy if the cookies we use change. We'll update the "Last updated" date above when we do.

8. Contact

Questions about this policy? Reach out at orgdeckinfo@gmail.com, or use the in-app bug report form if you're already signed in.