Cookie Policy
Last updated: 2026-09-15
We keep cookies to the minimum the product actually needs. This page lists exactly what we use — no invented categories, no generic boilerplate list.
1. What this page covers
This policy describes the cookies and browser-storage mechanisms Developer Connects actually sets, categorized honestly by what they do.
2. Strictly necessary — authentication cookies
Set by Clerk, our authentication provider, when you sign in. These keep you signed in as you move between pages. We don't control their exact names or contents — that's Clerk's infrastructure — but they exist only to support sign-in and account access.
3. Strictly necessary — session cookie
We set one cookie ourselves: dc_session, an httpOnly, randomly generated identifier with no personal information in it. It lets features like zero-result search tracking and “recently viewed developers” work consistently across pages in the same browsing session, whether or not you're signed in. It's valid for up to a year, or until you clear cookies.
4. Local/session browser storage
We use a small amount of local browser storage (not a cookie, and never sent to our servers) for purely cosmetic, per-device convenience — for example, remembering that you've already dismissed a sign-in prompt this browsing session, so we don't show it again immediately.
5. What we don't use
We do not use third-party advertising cookies, cross-site tracking cookies/pixels, or a third-party analytics platform's cookies. Product-usage analytics (searches, page views, clicks) are recorded directly to our own database via the session identifier above, not through a cookie-based third-party analytics tool.
6. Consent
Because the cookies above are strictly necessary for core functionality (sign-in and consistent browsing-session behavior) rather than for advertising or optional tracking, we have not built a cookie-consent banner. If our cookie use expands beyond what's described here — particularly into advertising, cross-site tracking, or optional analytics cookies — we will introduce an appropriate consent mechanism before doing so, consistent with applicable law.
7. Managing cookies
You can clear or block cookies through your browser's own settings at any time. Blocking the authentication or session cookie will likely prevent sign-in and some personalization features from working correctly.
8. Changes to this policy
If the cookies or storage we use change, we'll update this page. The “Last updated” date above always reflects the current version.
9. Contact
Questions about this policy: contact nodalaltalks02@gmail.com.
This page is a production-quality draft, not a substitute for advice from a qualified lawyer familiar with Developer Connects's actual legal entity, operating locations, data flows, and business model. Questions about this policy can be sent to nodalaltalks02@gmail.com.