Cookie Policy

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

The cookie we set on every visit is 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.

3A. Enquiry cookie — only if you send a request

If you ask to connect with a developer, we may set a second cookie after your request is saved, called dc_lead. It is not set just by browsing.

• Purpose: so that, on this browser, the next time you open the request form we can offer to continue with the number you shared before (shown only with most of its digits hidden) instead of asking you to type it again.
• Duration: 30 days from the request. Sending another request on this browser starts the 30 days again. After that, or if you clear it, you simply see the normal form.
• Protection: it is an httpOnly cookie (page scripts cannot read it), it uses the SameSite “Lax” setting (browsers do not send it with most cross-site requests), and on the live site it is marked secure so it is sent only over HTTPS. Its contents are digitally signed so that a changed or invented value is ignored.
• What it contains: a version marker, an internal reference number for your enquiry record (a random identifier that means nothing outside our systems), an expiry time and the signature. It does not contain your name, phone number or email address. Because the reference number points to your enquiry record on our servers, we treat it as linked to your enquiry details.
• What it is not used for: advertising, cross-site tracking or analytics. If we cannot sign it (a configuration we control), we do not set it and the form is always shown in full.

4. Local/session browser storage

We use a small amount of local browser storage (not a cookie) in two ways.

Convenience, kept on your device: for example, remembering that you've already dismissed a sign-in prompt this browsing session, so we don't show it again immediately. If you make a choice on our cookie banner, that choice is stored the same way so we can remember it on this device. These values are not sent to our servers.

Your details, for next time: after you send an enquiry, your browser keeps the name and mobile number you typed so the next enquiry form is already filled and you can send it with one tap. It stays in your browser's session storage and is cleared when you close the tab; if you have accepted analytics cookies it is also kept in local storage on this device. It is not sent to us until you press send on a form, and "Not you?" on the form removes it straight away. You can also clear it by clearing this site's data in your browser.

How you found us: when you arrive on the site, your browser keeps a short record of how you got here for that visit — the page you landed on, the address (without any query string) of the external site you came from, if any, and campaign tags in the link such as utm_source or an advertising click identifier. This stays in your browser's session storage and is cleared when you close the tab. If you have accepted analytics cookies, a copy of the first arrival is also kept in local storage so it can survive across visits. This record is not sent to us as you browse. It is sent to our servers only if you send a request to connect with a developer or send us a property enquiry (the enquiry form, or the short form on a project page), so that we know which page or campaign led to your enquiry. It contains no name, phone number or email address.

5. Optional — analytics cookies (Google Analytics)

If you choose “Accept” on our cookie banner, we load Google Analytics 4, a service provided by Google, to understand how Developer Connects is used — for example which pages are viewed, and roughly where in the world and on what kind of device. It sets cookies named _ga and _ga_ followed by an identifier, which by default last up to two years unless you clear them, and Google receives the resulting usage data.

If you choose “Accept only essentials”, Google Analytics is not loaded and none of these cookies are set. We do not load Google Analytics on our admin or account pages, and we do not enable Google's advertising features.

One exception applies whatever you choose: we keep an anonymous count of what happens to our “install the app” banner (shown, used, postponed, dismissed, installed, opened). It uses only our anonymous session cookie and goes to our own database, never to Google or an advertiser, and it is skipped if your browser sends a Do Not Track or Global Privacy Control signal. Your choice on the banner is remembered in local browser storage on your device.

6. What we don't use

We do not use advertising cookies or cross-site tracking pixels. Other than the optional Google Analytics cookies described above, we do not use a third-party analytics platform's cookies. Our own product-usage analytics (searches, page views, clicks) are recorded directly to our own database via the session identifier above.

Advertising measurement (such as a Meta Pixel) is built into the site but switched off. If we turn it on, it will load only after you choose “Accept”, and we will update this policy before it does.

7. Consent

The cookies in sections 2 and 3 are strictly necessary for core functionality (sign-in and consistent browsing-session behavior), so they don't depend on a choice. The enquiry cookie in section 3A is set only as a result of something you do (sending a request), never merely by visiting. Analytics cookies are optional and stay off until you choose. Our cookie banner offers two choices, shown with equal prominence: “Accept” (essential cookies plus Google Analytics) and “Accept only essentials”. Your choice is remembered on this device in local browser storage (see section 4). If you later choose “Accept only essentials”, Google Analytics stops running and we remove its cookies from your browser.

8. Managing cookies

You can change your analytics choice at any time using “Cookie settings” in the site footer. You can also clear or block cookies through your browser's own settings. Blocking the authentication or session cookie will likely prevent sign-in and some personalization features from working correctly. Clearing or blocking the enquiry cookie only means the request form always asks for your number again.

9. 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.

10. Contact

Questions about this policy: contact developerconnects02@gmail.com.