Cookie Policy
Last updated: October 9, 2026
This Cookie Policy explains how Cascade (“Cascade,” “we,” “us,” or “our”) uses cookies and similar technologies on our websites and Services, including cascadedept.com. It should be read with our Privacy Policy.
Questions: support@cascadedept.com.
1. What are cookies?
Cookies are small text files stored on your device when you visit a site. Similar technologies include local storage, session storage, pixels, and SDKs. Together we call them “cookies” in this Policy.
2. How we use cookies
We use cookies to:
- Keep you signed in and secure your session
- Remember preferences and basic site functionality
- Understand how the Services are used so we can improve them
- Attribute visits from referral or campaign (UTM) landing links
- Measure marketing performance where applicable
3. Types of cookies we use
Strictly necessary
Required for the Services to work. These typically include authentication/session cookies, security cookies, and load-balancing cookies. The Services may not function correctly if you block these.
- Account session and authentication (for example via our auth provider)
- Security and fraud-prevention signals
- Checkout and payment flow continuity (via our payment provider)
Functional
Help remember choices such as UI preferences or recently used settings so the experience is smoother.
Analytics and advertising (optional)
Only after you Accept on the cookie notice. If you Decline, or you have not chosen, these are not loaded and their cookies are not set.
- Microsoft Clarity — session recording and heatmaps. Cookies on our site include
_clckand_clsk. Microsoft and Bing may setCLID,MUID,MR,SM,ANONCHK, andSRM_B. - Meta Pixel — advertising and conversion events (page views, registration, checkout, purchase, and product milestones). Sets
_fbpon our site. Meta may setfron facebook.com. - Vercel Web Analytics — page-view counts. It does not set its own cookie on cascadedept.com.
- Signup attribution (
cascade_src) — httpOnly, up to 90 days, with landing page, referrer, and campaign parameters from the link. A copy may sit in local storage ascascade_signup_attribution.
Refer a friend
If you open a link with a ?ref= code, we set an httpOnly cookie named cascade_ref for 30 days so a signup can be tied to that invite. This cookie is strictly necessary for the referral program and is not waiting on the cookie notice. An ordinary visit does not set it.
4. Examples used by Cascade
Depending on features you use, cookies or similar storage may include:
- Authentication / session — keep you logged in across pages and API requests
- Campaign attribution —
cascade_src, only after you Accept - Referral invite —
cascade_refafter a?ref=link - Provider cookies — Supabase auth cookies when you sign in; Stripe during checkout; Microsoft Clarity and Meta cookies only after you Accept
- Local storage — client-side preferences or temporary UI state
Exact cookie names and lifetimes can change as we update the product or providers. This Policy describes categories rather than an exhaustive live inventory.
5. Duration
- Session cookies expire when you close your browser or end a session
- Persistent cookies remain for a set period or until you delete them
6. Managing cookies
You can control cookies through:
- Browser settings (block, delete, or alert on cookies)
- Device-level privacy controls
- Cookie settings on this page, which reopens Accept / Decline
Blocking strictly necessary cookies may break sign-in, checkout, uploads, or other core features. Third-party tools may also offer their own opt-outs.
7. Do Not Track
Some browsers send “Do Not Track” signals. There is no consistent industry standard for responding to them. We treat cookie choices according to this Policy and applicable law.
8. Changes
We may update this Cookie Policy from time to time. The “Last updated” date will change when we do. Continued use of the Services after updates means you accept the revised Policy, except where consent is required.
9. Contact
Related: Privacy Policy · Terms of Service