Cookie Policy

1. What are cookies?

Cookies are small text files stored on your device when you visit a website. They help sites remember your session, settings, and basic technical context. Similar technologies include local storage and session storage in your browser.

2. Cookies we use

Strictly necessary

These are required for the Service to function. Without them, you can't stay logged in or use protected pages.

• Authentication session — Supabase auth tokens so your dashboard, saved items, and Broker tools work across page loads.
• Security — CSRF and abuse-prevention signals used by our hosting layer (Cloudflare).

Functional

These improve your experience but aren't strictly required.

• Preferences — UI choices and settings you save to your account (stored server-side; session cookies may cache short-lived state).
• Checkout return — Short-lived parameters after Stripe checkout so we can confirm Broker subscription status.

Analytics

We do not currently run third-party advertising or cross-site tracking pixels. If we add privacy-respecting analytics in the future, we'll update this page and describe what's collected.

3. Third-party cookies

Some embedded or linked flows may set cookies when you interact with them:

• Google — if you choose “Sign in with Google,” Google's authentication flow may set its own cookies.
• Stripe — checkout and billing portal pages may set cookies required for payment security and fraud prevention.

We don't control third-party cookie policies — review their sites for details.

4. How long cookies last

• Session cookies — deleted when you close your browser (or when you sign out).
• Persistent auth cookies — may last up to the maximum session duration configured in Supabase (typically days to weeks) unless you sign out or clear storage.

5. Your choices

You can:

• Block or delete cookies in your browser settings.
• Sign out to clear active session state.
• Use private browsing — you'll need to sign in each session.

Blocking strictly necessary cookies will prevent login and dashboard features from working correctly.

6. Do Not Track

We don't respond to Do Not Track browser signals in a standardized way because there is no industry consensus. We already limit tracking to what's needed to operate the Service.

7. Updates

If we change how we use cookies, we'll update this page and the “Last updated” date. Material changes may also be noted in our Privacy Policy.

8. Contact

Questions about cookies? Email hello@dare.diy.