Cookie policy

Cookies are browser records sent with matching requests. Local storage stays in the browser until a page reads it; it is not automatically sent with every request. This policy covers both, including which first-party attribution values can accompany an enquiry when analytics is allowed.

On a first visit, analytics and advertising consent signals start denied. The Google Tag Manager container is not requested until analytics permission is present. There is no no-JavaScript Google tracking iframe.

The site can remember your theme and consent choice and run the enquiry form without analytics. Previously saved attribution values are cleared when analytics is not allowed. A prior affirmative analytics choice is reapplied on reload; a refusal keeps Google tags blocked.

• Accept all permits analytics and advertising.
• Reject all leaves both off.
• Manage consent lets you permit analytics with advertising still off, or permit both. Advertising requires the analytics container and is unavailable when analytics is off.

Your choice is stored as ki-consent, with session storage as a fallback if persistent storage is unavailable. If all browser storage is blocked, the current document can apply a choice but cannot remember it after reload. The footer reopens the settings. Withdrawing analytics clears first-party campaign attribution and accessible first-party Google analytics/advertising cookies. If Google’s container has already loaded, the page refreshes to stop that document’s tags. An unfinished public enquiry can be briefly saved in session storage and restored after the refresh. The refresh does not wait for an in-progress enquiry response. An already-sent enquiry uses browser keepalive support where available and within its payload limit, but delivery is not guaranteed. If the response was interrupted, the restored form warns that receipt is uncertain and asks you to check before sending again. You can still send the enquiry without tracking. Clearing browser data also resets the choice.

The first-party keys are listed below. Attribution keys are read and written only with analytics permission and are cleared on withdrawal. Their expiry rules describe when values are used or replaced; browser storage does not remove expired records by itself. Theme and consent settings remain until you clear them.

ki-consent-draft is functional session storage used only to protect an unfinished public enquiry during an analytics-withdrawal refresh. It can contain the enquiry fields you typed, excludes passwords, tokens and the bot-check field, is removed when read after refresh, and is ignored if older than ten minutes. Session storage ends when the browser tab session ends. It is not sent to analytics.

Only permitted attribution values are included in enquiry metadata. Without analytics permission, campaign identifiers and stored attribution are withheld; the form still sends the project information needed to answer your enquiry.

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 can load through Tag Manager after analytics permission. The site records permitted page interactions and only records a lead conversion after the form receives a confirmed durable receipt. A recorded submission is separate from a qualified sales opportunity.

Google cookie lifetimes and account retention depend on tag and property settings. Those settings need a separate account review; this policy does not assert a configured duration, Google Signals status or a storage setting that the website source cannot verify. Withdrawing consent stops subsequent site event recording and refreshes an already-tagged page. It does not erase previously collected account data.

Google cookies may be set after analytics permission, depending on the container configuration. See Google’s cookie documentation. Previously collected account records are separate from cookies on this device.

Advertising consent signals remain denied until you permit advertising as well as analytics. The site passes that choice to Google Consent Mode when the container is allowed to load. The tags configured inside the Google container require separate verification against these choices. Browser controls can remove stored cookies; this site cannot delete cookies belonging to another domain.

Advertising signals require explicit permission. Tags and third-party cookie behavior must be checked against the configured container; this site cannot remove cookies stored on another domain.

No session-recording script is included in the current website implementation. Any future recording feature would require its own reviewed disclosure, consent handling and field masking before release.

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.

The current website does not read Global Privacy Control or Do Not Track signals and does not suppress the banner in response to them. Analytics and advertising start off, and the banner applies the choices you make. Use Reject all or Manage consent to refuse them. Signal handling and legal obligations require a separate review; this page does not claim GPC compliance.

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.