C1.Chain Labs
Legal

Privacy Policy

This page covers what this website collects about you. Candidate and client data handled during an FDE engagement is a different relationship with different rules — see below.

Last updated 03 Aug 2026

1. Who we are

This site is operated by Chaain Labs (trading as Chain Labs), registered at A/11, Dream Palace, Surat, Gujarat 395007, India.

For anything in this policy — including a request to access, correct or delete your data — write to hello@chainlabs.in. A human reads it.

2. Two different relationships

Almost every privacy complaint we have seen comes from conflating these, so they are separated here on purpose.

This websiteAn FDE engagement
Our roleController — we decide what is collectedProcessor — you decide, we act on your instructions
Whose dataYours, as a visitorYour candidates', clients' and staff's
Where it livesOur analytics and scheduling vendorsYour infrastructure, your model keys
Governed byThis policyYour contract and DPA with us

3. What this website collects

There is no account system, no login and no newsletter. Everything below is either analytics or a call you chose to book.

Microsoft Clarity — session recordings and heatmaps

Clarity records how visitors interact with the page: scrolling, clicks, mouse movement and rage-clicks, replayed as a session recording, plus aggregate heatmaps. It is a Microsoft product and Microsoft processes the data on our behalf.

Clarity loads for every visitor, immediately. The bar at the bottom of the page is a notice, not a consent choice — dismissing it does not turn anything on or off, and we are not going to dress it up as a decision you made. If you do not want to be recorded, the options that actually work are in section 8.

These are the cookies Clarity sets, per Microsoft’s own documentation:

CookiePartyPurpose
_clckFirst-partyPersists a pseudonymous Clarity user ID for this site
_clskFirst-partyJoins several page views into one session recording
CLIDThird-partyIdentifies when Clarity first saw this browser on any Clarity site
MUIDThird-partyIdentifies a browser across Microsoft sites; used by Microsoft for advertising, analytics and operations
ANONCHKThird-partyFlags whether MUID is transferred to an advertising cookie. Clarity does not use it, so it is always 0
MRThird-partyFlags whether MUID should be refreshed
SMThird-partySynchronises MUID across Microsoft domains

Vercel Web Analytics and Speed Insights — cookieless

Our host, Vercel, counts page views, records which sections of the page were seen, which buttons were clicked, and how fast the page loaded for you. These set no cookies and do not build a cross-site profile. The events they record are about the page, not about you: which CTA was clicked, which FAQ was opened, which section was scrolled to.

Storage this site sets itself

Four keys in your browser’s own storage, none of them cookies. They are never sent to a server. The three sessionStorage keys are deleted when you close the tab; the one localStorage key persists until you clear site data, because a notice you have already read should not reappear every visit.

KeyKindWhat it does
banner_dismissedSessionRemembers that you closed the top announcement banner, so it stays closed
analytics_section_viewsSessionStops one page section from being counted as viewed twice if you reload
analytics_section_engagedSessionSame, for sections you spent time on
cookie_notice_ackLocalRemembers that you dismissed the cookie notice at the bottom of the page

Booking a call

Every “book a call” button sends you to Cal.com, which is a separate service. If you complete a booking, Cal.com collects your name, email address, time zone and anything you type into the booking form, then creates a calendar invitation for both of us. We see what you submitted. We do not receive anything about people who open the booking page and leave.

Email

If you email us, we keep the message and your address for as long as the conversation is useful — which for a prospective client means the length of the relationship, and for everything else means until the thread is clearly finished.

4. Why we are allowed to do this

If you are in the UK, EU or EEA, the GDPR requires us to name a legal basis for each of the above:

  • Analytics (Clarity, Vercel) — legitimate interests: understanding which parts of a single marketing page work, so we can fix the parts that do not. You can object; see section 8.
  • Booking a call — taking steps at your request before entering into a contract.
  • Email — legitimate interests in replying to someone who contacted us, or pre-contract steps if you are asking about working together.

If you are in India, the Digital Personal Data Protection Act, 2023 applies, and the equivalent basis is the certain legitimate use of data you voluntarily provided for the purpose you provided it.

5. Who else touches it

We do not sell your data. We run no advertising on this site and buy no advertising that targets you off it. One honest caveat, because it is visible in the table above: Microsoft’s MUID cookie has advertising uses on Microsoft’s own properties. That is Microsoft’s cookie and Microsoft’s use of it — we neither receive nor act on it — but it is set as a consequence of us running Clarity, so we are not going to claim the page is advertising-free and leave you to find it.

The vendors below process your data because the site cannot function otherwise:

  • Microsoft — Clarity session recordings, heatmaps and its cookies
  • Vercel— hosting, plus the cookieless analytics above. Every request to this site reaches Vercel’s servers and its logs.
  • Cal.com — scheduling, if and only if you book
  • Our email and calendar provider — correspondence and the resulting invitations

Each of them retains data on their own schedule, published in their own policies. We do not control those periods and will not invent numbers for them here.

6. International transfers

We are based in India and the vendors above are largely US-based, so data collected in the UK, EU or EEA leaves that region. Where a transfer needs a safeguard, it rests on the vendor’s own mechanism — Standard Contractual Clauses or an adequacy decision — as published in their terms.

7. How long we keep it

  • Analytics — for as long as Microsoft and Vercel retain it under their own policies. Nothing in it identifies you by name.
  • Bookings and email — for the length of the conversation or relationship, and afterwards only where we need the record.
  • Session storage — until you close the tab.

8. Your choices and your rights

Opting out of session recording

Blocking cookies for this site in your browser settings stops Clarity from setting them — Microsoft’s script does not set cookies when the browser refuses them. Most tracker-blocking extensions and browsers with built-in blocking will also stop Clarity outright. Vercel’s analytics set nothing to block.

We do not currently act on Do Not Track or Global Privacy Control signals. Saying so is more useful to you than a claim we do not honour.

Your rights

Under the GDPR you can ask us for a copy of your data, ask us to correct or erase it, ask us to restrict how we use it, object to our legitimate-interests processing, or ask for it in a portable form. You can also complain to your national supervisory authority. Under India’s DPDP Act you can ask for access, correction and erasure, nominate someone to exercise your rights, and raise a grievance with us.

Either way the route is the same: hello@chainlabs.in. We will not ask you to prove a legal basis for asking.

9. Client engagements — where we are the processor

This is the part that matters if you are considering hiring us, and it is deliberately different from everything above. During an FDE engagement the candidate and client data an agent touches is yours. You are the controller. We act on your instructions under a signed agreement.

  • Agents run on your infrastructure with your model keys by default. Candidate data does not flow through systems we own.
  • We sign DPAs. If your clients impose terms on you, those terms can be passed down to us.
  • We build redaction into every outbound channel — an agent that messages a candidate does not carry your whole record with it.
  • Model-local deployment is available where an EU desk requires it, so prompts and candidate text do not leave your environment.
  • You own the code from the first commit. Ending the retainer ends our access, not your systems.

None of that is a substitute for the actual contract. Where this page and your signed agreement differ, the agreement wins.

10. Changes to this policy

When the substance changes we update the date at the top of this page. We do not send notifications; this is a marketing site with no account to notify.

This site uses Microsoft Clarity for analytics, which sets cookies. Privacy Policy.