Legal

Cookie Policy

Last updated: August 11, 2026  ·  Effective: August 11, 2026

Privacy Policy Terms of Service Acceptable Use Sub-processors Cookies Refunds & Cancellation

This policy explains what imatic.ai stores in your browser, why, and how to control it. It covers cookies and equivalent technologies such as localStorage. It supplements our Privacy Policy.

No advertising trackers. Analytics only if you say yes.

The imatic.ai marketing website sets no advertising cookies, shares nothing with data brokers or ad networks, and builds no profile of you across other websites. There is no cross-site profile of you to opt out of.

We do use Google Analytics to count visits and see which pages are useful. It is off by default: no analytics cookie is written and nothing is requested from Google until you choose Accept analytics in the banner. Rejecting costs you nothing and changes nothing about how the site works. What is stored in each case is set out in sections 2 and 3.

Contents

  1. What these technologies are
  2. What our website stores without asking
  3. Analytics cookies
  4. What the product stores
  5. Third-party content
  6. How to control it
  7. Consent
  8. Changes
  9. Contact

1. What these technologies are

A cookie is a small text file a site stores in your browser and sends back on later visits. localStorage serves a similar purpose but stays in your browser and is never transmitted automatically. Both let a site remember something between page loads — that you are signed in, or which page you first landed on.

They become a privacy concern when a third party sets them across many sites to build a profile of you. We do not do that, and we do not permit anyone else to do it on our sites.

2. What our website stores without asking

Two things, both first-party, both kept in localStorage in your own browser. Neither needs your consent: one records how you arrived, the other records the analytics choice you made so we do not have to ask you again.

NameTypePurposeRetained
Attribution First-party localStorage Records how you arrived — campaign parameters (UTM), click identifiers, referring site, and landing page — so that if you later submit a contact or demo-request form, we know which campaign to credit. It is not read for any other purpose. Until you clear your browser storage
im_cookie_consent First-party localStorage Remembers whether you accepted or rejected analytics cookies, and when. Without it we would have to ask you again on every page. It is never sent to us or to anyone else. Until you change your choice or clear your browser storage

The attribution value stays in your browser and is sent to us only if you choose to submit a form. If you never submit one, we never receive it. It contains no name, email, or identifier we could use to recognise you, and it is not shared with anyone. If your browser blocks storage, the site works normally — attribution is best-effort by design, and a blocked consent record simply means we ask you again.

3. Analytics cookies — only after you accept

We use Google Analytics 4 on the marketing website to count visits and understand which pages people find useful. Nothing below exists in your browser, and nothing is requested from Google, unless you press Accept analytics. If you have not been asked, none of these cookies exist.

NameSet byPurposeExpires
_ga Google Analytics (first-party cookie on imatic.ai) Holds a randomly generated identifier so repeat page views in the same browser count as one visitor rather than several. It is not linked to your name or email. 2 years
_ga_<container-id> Google Analytics (first-party cookie on imatic.ai) Holds the session state for our specific Analytics property — when the current visit started and how many visits there have been. 2 years

What Google receives. When the tag runs, Google receives the page address and title, the referring page, your browser, device type and language, the identifier above, and your IP address — which it uses to derive an approximate location (typically country, region and city) and, per Google’s documentation, does not store in Analytics. We do not send your name, email address, phone number, or anything you type into a form.

What we switch off. The tag is configured for measurement only: Google Signals and ad-personalisation signals are disabled, so the data is not used to build advertising audiences, and Google’s advertising cookies are never set by us. Until you accept, Google Consent Mode is set to denied for analytics, advertising, and personalisation storage alike.

4. What the product stores

When you sign in to the imatic.ai portal, calendar, or survey applications, we store what is strictly necessary to keep you signed in and to remember your interface preferences:

PurposeTypeWhy it is necessaryRetained
Session & authentication First-party storage / cookie Keeps you signed in between pages and protects your session. Without it you would be logged out on every navigation. Until you sign out or the session expires
Preferences First-party storage Remembers choices such as language, timezone, interface density, and theme. Until you change or clear them
Security First-party Protects against cross-site request forgery and detects abnormal session activity. Session

These are strictly necessary for a service you have asked for, so they do not require consent under the ePrivacy rules. Blocking them will prevent you from signing in.

5. Third-party content

Our legal and marketing pages load web fonts from Google Fonts. This means your browser makes a request to Google’s servers, which necessarily reveals your IP address to Google as part of fetching the font. Google Fonts does not set advertising cookies for this.

The only other third-party resource is the Google Analytics tag described in section 3, and your browser requests it only after you accept. The standalone legal pages — this one and the policies linked at the top — load no analytics script at all; they are plain HTML and work with JavaScript disabled.

Where you connect an integration such as Google Calendar, that provider’s own cookies may apply during the sign-in flow, under its policies rather than ours.

6. How to control it

Blocking storage on the marketing site costs you nothing. Blocking it in the product will prevent sign-in, because the session cannot be maintained.

Analytics cookies are the only non-essential category we use, and we ask before setting them. On your first visit you are shown a banner with two equally weighted choices — Accept analytics and Reject analytics — presented in the same size and style, because a choice that nudges you is not a choice. Until you accept, Google Consent Mode is set to denied, no analytics cookie is written, and nothing is requested from Google.

You can also dismiss the banner without deciding; that leaves analytics off. Your decision is recorded in your own browser (see section 2), honoured on later visits without asking again, and reversible at any time through the Cookie preferences link in the footer. Withdrawing consent is as easy as giving it.

The strictly necessary items in sections 2 and 4 do not require consent, because they are needed to deliver a service you asked for. If we ever add a new non-essential technology, we will ask for your consent first and update this page before the change takes effect.

8. Changes to this policy

We will update this page if what we store changes, and revise the “Last updated” date above. Material changes are notified as described in our Privacy Policy.

9. Contact

Entity
Vizionsys Technologies Private Limited
Address
Bengaluru, Karnataka, India
Email
hello@imatic.ai
Phone
+91 99675 80291