Cookie Policy

1. What cookies and similar technologies are

A cookie is a small text file that a website places on your device to remember information about your visit. "Similar technologies" include browser localStorage and sessionStorage, pixel tags, and identifiers that behave like cookies. In this policy, "cookies" is used as shorthand for all of these.

First-party cookies are set by nirman-ventures.com. Third-party cookies are set by a service embedded in one of our pages (for example, Microsoft Clarity or GoHighLevel). Third-party cookies are governed by that provider's own privacy notice, which we link to below.

2. Categories we use

We group cookies by purpose. Optional categories are denied by default until you make a choice.

Strictly Necessary

Required for the site to function. These include the record of your consent decision (stored in localStorage under nirman.consent.v1) and, on the Contact and Investor Access pages, cookies set by the GoHighLevel (LeadConnector) form and calendar iframes you actively interact with. These are set only when the corresponding form is loaded and are treated as strictly necessary because they are essential to the service you are requesting.

Analytics

Off unless you turn it on. When granted, Microsoft Clarity records anonymized page interactions (heatmaps, scroll depth, session replay of on-page interactions) so we can improve the site. Clarity is loaded only after you grant analytics consent and receives a Consent API v2 signal that mirrors your choice.

Advertising

Not currently used. This build has no advertising, remarketing, conversion, or social-media pixels installed. If an advertising tracker is ever added, we will add an "Advertising" toggle to the preference center, bump the consent schema version, and re-prompt every visitor for a fresh decision before any advertising cookie is set.

Functional

Not currently used as a separate category. Non-essential preference cookies would be listed here if introduced.

3. Providers and cookies actually installed

The following technologies are present in this build. Cookie names and durations are drawn from provider documentation. Please treat durations as indicative; the authoritative source is each provider's own documentation, which is linked below.

Microsoft Clarity

• Category: Analytics (opt-in).
• Purpose: session interaction analytics, heatmaps, engagement measurement.
• Known cookies: _clck (per Microsoft, up to 1 year) and _clsk (per Microsoft, 1 day).
• First-party cookie names, third-party service.
• Consent mechanism: loaded only after analytics consent is granted; controlled via the Clarity Consent API v2.
• Provider notice: https://privacy.microsoft.com/privacystatement.

GoHighLevel (LeadConnector)

• Category: Strictly Necessary (when you engage a GHL form or calendar).
• Purpose: rendering embedded forms on /learn-more and /contact, and the booking calendar on /contact.
• Only loaded on the pages that render those iframes.
• Provider notice: https://www.gohighlevel.com/privacy-policy.

No Google Analytics, Google Tag Manager, Facebook / Meta Pixel, LinkedIn Insight Tag, TikTok Pixel, X/Twitter Pixel, HubSpot, or comparable analytics/advertising service is installed on this build.

4. Your choices

When you first visit the site, a consent banner offers three equally prominent choices: Accept All, Reject All, and Manage Preferences. Scrolling, closing the banner, or continuing to browse is not treated as consent. Rejecting is exactly as easy as accepting.

The preference center exposes a toggle for each optional category. Your decision is stored in your browser under nirman.consent.v1 for up to six months, after which we ask again. Changing categories takes effect immediately: revoking analytics tells Microsoft Clarity to erase its cookies via its documented consent-off call.

You can also clear the record yourself by clearing site data in your browser, which will cause the banner to reappear on your next visit.

5. Global Privacy Control (GPC)

If your browser or a privacy extension sends a Global Privacy Control signal, we treat it as an opt-out of all optional categories until you explicitly opt back in from the preference center. The banner and preference center display a note when GPC is detected. GPC is distinct from the obsolete Do Not Track header, which we do not act on.

6. What we store and for how long

• nirman.consent.v1 (browser localStorage, first-party): our record of your decision. Contains the schema version, decision timestamp, per-category choice, and whether GPC was detected. Kept for up to six months, then we re-prompt.
• Microsoft Clarity _clck and _clsk (third-party cookies): only set after you grant analytics consent. Durations follow Microsoft's documentation.
• GoHighLevel form and calendar cookies: only set on pages where you engage the embedded form or calendar. Durations follow GoHighLevel's documentation.

We do not create a unique tracking identifier merely to remember your consent choice.

7. Changes to this policy

When we add or remove a tracker, we bump the internal consent schema version. That causes the banner to re-prompt every visitor, so you always get a fresh choice against the current set of technologies. Material changes will also be reflected in the Effective Date above.

8. Contact

Questions about this Cookie Policy or your privacy choices can be sent to nikhil@nirman.vc. For matters covered by our Privacy Policy, see that document for the applicable contact and rights information.