Cookie policy

A cookie is a small text file a website asks your browser to keep, so it can recognise that browser next time. Some are unavoidable, like remembering that you dismissed a banner. Others count visitors or measure whether an advert worked.

Websites also use localStorage, which does the same job but stays on your device instead of travelling with every request. We use localStorage for the two settings below, which is why they never reach our server. This page covers cookies, localStorage and advertising pixels alike. The mechanism changes; the honesty should not.

We use Google Tag Manager, and Google Consent Mode v2 is configured before the container loads. Here is exactly what that means on your first visit, stated plainly rather than dressed up.

• Advertising is denied. ad_storage, ad_user_data and ad_personalization all start as denied. No Google Ads cookie is written and no advertising identifier is created until you press Accept.
• Analytics is granted. analytics_storage starts as granted, so Google Analytics 4 measures the visit. This is the notice-based pattern Google recommends for visitors in India, the United States, Australia and New Zealand, and it is a setting we chose rather than an accident.
• Functional and security storage is granted, which is what lets the site remember your theme and defend its own forms.
• The container waits 500 milliseconds for a stored choice before any tag fires, so a previous decision is applied before anything runs.

If you would rather analytics did not run at all, open the banner and turn it off, or block cookies for this site in your browser before you browse further. We would rather tell you the real order of events than claim a blanket opt-in we do not operate.

The banner appears once the page has finished loading, not over the top of it. Three choices:

• Accept all turns on analytics and advertising storage.
• Analytics only keeps analytics on and leaves advertising off. This is the second button, and it is a real choice rather than a softer way of saying yes.
• Manage consent opens the per-category toggles, where you can switch analytics and advertising independently and save.

Your answer is stored in localStorage under ki-consent and re-applied on every later visit. The banner does not come back at you page after page. You can reopen it at any time from the Manage consent link in the footer, and clearing this site's data resets you to the defaults above.

Two keys, both first-party, both localStorage rather than cookies, so neither is sent to our server and neither can be read by anyone else's site.

Neither key is a cookie, so neither is sent to our server with your requests. No third party can read them, and neither can be used to recognise you on any other website. There is no session cookie on this site.

Our enquiry forms carry a hidden field a person never sees and never fills in, plus a timestamp taken when the form loads. A submission that fills the hidden field, or that arrives less than three seconds after the form appeared, is treated as a bot and dropped.

Neither of those sets a cookie, writes to storage or leaves anything behind on your device. The timestamp lives in the page for as long as the page is open and travels with the submission. We mention it because it counts as a similar technology even though nothing is stored, and a page that lists only cookies would be telling you half the truth.

Google Analytics 4 loads through Tag Manager and tells us which pages get read, which get ignored and where people give up. That is the difference between guessing and knowing.

IP addresses are truncated before storage, Google Signals is off, advertising features are off, and event data expires after 14 months, the shortest retention Google offers. You can switch analytics off from the banner at any time.

IP truncation is on, Google Signals is off and retention is set to 14 months. Google describes these cookies in its own cookie usage documentation. Switch them off from Manage consent in the footer and they stop being written.

These load only after you press Accept all, and only where a Google Ads campaign is running. They let us see whether an advert produced an enquiry, and they let Google avoid showing you the same advert over and over.

We do not build audience lists from site visitors to sell on, and we do not share data for cross-context behavioural advertising as the CPRA defines it. If no campaign is pointing at the page you are reading, none of these load even with consent given.

We run no Meta pixel, no LinkedIn Insight tag and no advertising tag from any other network on this website. If one ever appears in your browser on our domain, send us the cookie name and the page and we will trace it.

The site is wired to support Microsoft Clarity, which records anonymised session replays and heatmaps. It is switched off. No Clarity script loads and no Clarity cookie is set unless we add a project ID to the site configuration.

If we do turn it on, it will run only after you have accepted analytics, its cookies (_clck and _clsk) will be added to the table above with a new date on this page, and masking will be set so that text you type into a form is never recorded. We are naming it here while it is off, because finding out afterwards is worse.

Our office pages can embed a Google Map, and an article can embed a YouTube video. As this policy is published, no page on the site embeds either, so no third-party embed cookie is set anywhere on knitinfotech.com.

When we add one, these rules apply and this page gets updated first:

• YouTube is embedded through youtube-nocookie.com, which holds back the advertising cookie until you press play.
• A map is loaded only when you click it, not on page load.
• Once you interact with either, the provider sets its own cookies under Google's privacy policy. We do not receive that data and we cannot switch it off for you.

Your browser can block or clear all of this without asking us:

• Chrome: Settings, then Privacy and security, then Third-party cookies
• Safari: Settings, then Privacy, then Manage Website Data
• Firefox: Settings, then Privacy and Security, then Cookies and Site Data
• Edge: Settings, then Cookies and site permissions

Blocking everything breaks parts of most websites, including this one. Your consent choice is itself stored in your browser, so clearing site data brings the banner back and returns you to the defaults. You can also opt out of Google Analytics across every site with Google's browser add-on.

We honour Global Privacy Control. If your browser sends the GPC signal we treat it as a refusal of analytics and advertising storage, and we do not badger you with the banner as though you had said nothing.

We do not act on the older Do Not Track header. It was never given an agreed meaning and browser vendors have dropped it, so treating it as a legal instruction would be pretending.

There is no separate Indian cookie law of the kind the EU's ePrivacy Directive created. Cookies that hold personal data fall under the Information Technology Act, 2000 and the SPDI Rules, 2011 today, and will fall under the notice and consent provisions of the Digital Personal Data Protection Act, 2023 when those commence, currently set for 13 May 2027.

The DPDP framework will require consent that is free, specific, informed and unambiguous, obtained without dark patterns and withdrawable as easily as it was given. Our banner already works that way: no pre-ticked advertising box, an equal-weight second button, and a permanent footer link to change your mind.

Requests to see or delete the data behind any of these tags are handled under our Privacy Policy, by the Grievance Officer named there, within 30 days.

We update this list whenever a tag is added or removed, and the date at the top moves with it. If we add a category of cookie that needs consent, your existing consent does not carry over to it. We ask again.

If a cookie turns up in your browser on our domain that is not listed above, we want to know. Send us the name and the page you were on and we will trace where it came from.

Requests to see or delete the data behind these tags are handled under our Privacy Policy. Our Grievance Officer answers within 30 days.