IMI Life Science Cookie Notice
Effective date and last updated: 10 November 2026
This Cookie Policy explains how IMI Life Science uses cookies and similar technologies on this website, including when its optional features are available: customer accounts, the product catalogue, product comparison, shopping baskets, quotations, checkout and Stripe payments, enquiries, bookings, newsletters, campaign measurement, Google Tag Manager (GTM) and Google Analytics 4 (GA4), performance monitoring and embedded content. It supplements our Privacy Notice, which explains how personal information is used and how to exercise your privacy rights.
This policy covers the full-feature website. A feature being enabled does not mean that every technology listed below is used on every visit. The technologies used depend on the page you visit, the service you request, your choices, the provider's configuration and your browser. This policy does not itself enable any feature or give consent on your behalf.
1. Cookies and similar technologies
Cookies are small text files stored by your browser. First-party cookies are associated with the website you visit; third-party cookies are associated with another provider. A session cookie normally lasts for the browser session. A persistent cookie remains until its expiry date or until it is deleted, subject to your browser's limits.
We also use local storage and session storage. These are browser storage mechanisms, not cookies. Local storage can survive browser restarts and has no automatic expiry unless the application or browser removes it. Session storage is associated with a browser tab and is normally removed when that tab's session ends; browser session-restore settings may retain it. Pixels, tracking links and requests to embedded services may communicate information without setting a cookie.
2. Necessary services, accounts and transactions
Necessary technologies support security, remembering your consent choices, account access and services that you request, such as a shopping basket, checkout or submitting a form without creating a duplicate request. They are not used to personalise advertising. Blocking these technologies can prevent the requested service from working.
- imi-consent-storage: first-party local storage recording your necessary, functional, analytics and marketing preferences, whether you have made a choice, and the consent-notice version. It remains until changed, reset or cleared. Obsolete or malformed saved choices are not treated as consent; the website asks you to choose again. Rejection or withdrawal removes the website analytics cookies and identifiers, without clearing necessary account, basket or form-submission state.
- imi_refresh_token: a first-party secure, HttpOnly cookie used to renew an authenticated customer session. Its expiry follows the configured maximum account-session lifetime, and it is removed on sign-out or expiry. It is not an advertising identifier.
- imi_has_session_hint: first-party local storage indicating that an account session may exist. It is not the authentication credential. It remains until removed by the application or until site data is cleared.
- imi-cart-storage: first-party local storage remembering basket items and related basket state. It persists across visits until updated, cleared by the application or deleted through the browser.
- imi-checkout-form: first-party session storage used to restore checkout details during the checkout journey. It is normally retained for the tab session or until cleared by the checkout flow.
- imi_idempotency_*: first-party session storage containing request identifiers used to avoid duplicate form submissions, bookings or transaction actions. Entries are reset as the relevant action completes or restarts, or end with the tab session.
Restricted administration areas use separate account-session technologies, including the imi_admin_refresh_token cookie. Those technologies apply to authorised administration users, not ordinary public browsing.
3. Functional preferences and product tools
Functional storage remembers preferences and optional tools you use. This includes imi_language for the selected language, imi_currency for the selected currency and imi-comparison-storage for product comparison selections. These are first-party local-storage entries and remain until changed, reset or cleared. Basket reconciliation and returning to a page after signing in may also use local or session state.
Preferences saved as part of a requested service may be written when that service is used. Changing a banner preference does not automatically erase previously saved language, currency, basket or comparison data. You can change those selections in the relevant feature or remove them through your browser's site-data settings.
4. Analytics and performance monitoring
Google Analytics 4
Google Tag Manager manages the Google Analytics 4 integration. Neither the GTM container nor Google Analytics is loaded until you explicitly accept Analytics. No analytics events are queued for later replay before that choice. Marketing consent alone does not permit analytics. GA4 helps us understand visits, pages viewed, interactions and website performance, and may measure product interest, enquiries and commerce activity through configured events.
The current GTM integration allows reviewed Google analytics tags, while advertising tags, legacy consent widgets and Custom HTML tags are excluded. Google advertising storage, advertising user data and advertising personalisation remain denied. Google Analytics cookies are limited to this storefront hostname and use the Secure flag on HTTPS with SameSite=Lax. A separate direct-GA4 fallback may be used where no GTM container is configured, subject to the same explicit Analytics choice.
- _ga: a first-party cookie used by Google Analytics to distinguish visitors. Google's default lifetime is two years.
- _ga_*: a first-party cookie used by GA4 to persist session state, with a suffix identifying the configured Google tag. Google's default lifetime is two years.
The actual GA4 expiry may be shorter because of browser limits or different property settings, and expiry may be refreshed on subsequent visits. Cookie names may include the identifier of the configured property. Google receives information associated with analytics requests, such as page and event information, browser/device information and online identifiers. For details, see Google's GA4 cookie documentation and how Google uses information from sites that use its services.
First-party analytics
Our own analytics records website activity after Analytics consent. imi_visitor_id is a first-party local-storage identifier used to associate activity with the same browser; it has no automatic browser-storage expiry and remains until removed. imi_utm is session storage for campaign-source information and normally lasts for the tab session. Analytics may include the visited URL, referrer, time, language, screen information, broad country information and interaction details.
Browser performance and error monitoring
When enabled, Grafana Faro browser monitoring and Core Web Vitals measurement start after Analytics consent. They help identify loading delays, responsiveness problems and technical errors. Monitoring may use session identifiers and record page information, performance measurements, browser details, errors and diagnostic traces. This is separate from GA4 and may operate when GA4 is not configured. Library-managed session storage and identifiers follow the monitoring configuration; they are not advertising cookies.
5. Stripe payments and fraud prevention
When online payment is available and you use a payment feature, Stripe provides payment processing, payment authentication and fraud-prevention services. Stripe's scripts, payment frames or hosted pages may use cookies and similar technologies, including __stripe_mid, __stripe_sid and, depending on the payment flow, other Stripe identifiers such as m. They help recognise a device or payment session and detect potentially fraudulent activity.
Stripe controls the expiry of its identifiers. Some are short-lived session identifiers and others persist across visits; the exact set and lifetime depend on the Stripe service, payment method and browser. Consult Stripe's Cookie Policy and Stripe's Privacy Policy for current details. Stripe may receive device, browser, network and transaction information when its payment services are used.
Technologies genuinely needed to perform and secure a payment you request are treated as necessary for that payment. This does not make every Stripe technology necessary for general website browsing, and accepting Analytics or Marketing is not a requirement for using a payment service. Optional Stripe services, saved payment details or a separate Stripe account may be subject to additional choices and notices from Stripe. Rejecting analytics does not disable payment security; blocking Stripe altogether may prevent online payment.
6. Campaigns, enquiries, bookings and newsletters
Campaign links can include source parameters or a campaign token. imi_ct and imi_ct_reported are first-party session-storage entries used to retain a campaign token and avoid recording the same campaign-link click repeatedly within a session. A campaign-link click can be recorded when the link is opened, independently of the GA4 consent choice.
imi_lead_first_touch and imi_lead_journey are first-party session-storage entries used to retain the initial referral/campaign context and a limited recent browsing journey. This context can accompany an enquiry, booking or other submitted form so that we can understand the request and its source. It may include landing and referring pages, campaign parameters, advertising click identifiers present in the URL, visited pages and device information. These entries normally last for the tab session. Campaign and enquiry-context processing is distinct from GA4 and is not necessarily disabled by rejecting Analytics.
When newsletter and marketing features are enabled, messages may contain tracking links or a tracking pixel to measure clicks or delivery/open activity. Email software and privacy settings affect those measurements. These mechanisms are not necessarily browser cookies. Use the unsubscribe link in a marketing email to withdraw from that mailing; changing website cookie preferences does not itself unsubscribe you.
Salesforce or other connected customer-management services may receive enquiry, subscription or campaign information through server-to-server integrations. Enabling such an integration does not, by itself, install a Salesforce cookie in your browser. Processing of submitted information, customer records and marketing communications is explained in our Privacy Notice.
7. Embedded media, maps and external services
Pages may include videos or other content from providers such as YouTube, Vimeo, Dailymotion or Wistia. Maps may request tiles from OpenStreetMap. When external content is loaded, the provider can receive information such as your IP address, browser details and the page that requested the content. Video providers may also set cookies or use storage for playback, preferences, analytics or advertising, depending on the player, your provider account, browser restrictions and the provider's choices.
These technologies are used only where the relevant external content or service is present; enabling the website's feature set does not cause every listed provider to load on every page. Providers control their own identifiers and retention periods. For details and available controls, see the notices of Google/YouTube, Vimeo, Dailymotion, Wistia and the OpenStreetMap Foundation. A link to an external site is not, on its own, an embedded tracking service.
8. Your choices and how to change them
On a first visit, choose Accept All, Reject Optional or Customize. Reject Optional keeps only Strictly Necessary enabled. Customize lets you select Functional, Analytics and Marketing and then Save Preferences. Analytics starts only after an explicit Analytics opt-in; enabling Marketing alone does not enable it. Previously stored choices from an older notice version require a new choice.
Use the Cookie Preferences control at the bottom-left of the website at any time to review or change your choices. To withdraw analytics consent, switch Analytics off and Save Preferences, or choose Reject Optional when the banner is shown. Withdrawal stops future analytics dispatch, removes the website Google Analytics cookies and analytics identifiers, and reloads the document where needed to unload already-executed tracking code. Necessary account, basket and form-submission storage is retained. Browser privacy settings can also clear all site data; your preferences are specific to the browser and site address.
You can also block or delete cookies, restrict third-party storage and remove stored site data through your browser. This may sign you out, clear your basket or comparison list, remove saved preferences, or interrupt payment and embedded content. For browser-specific instructions, see Chrome, Firefox or Safari.
Stopping future tracking or removing browser data does not automatically delete information already received by us or a service provider. Browser storage expiry is also different from the retention of account, order, enquiry or analytics records. Please refer to our Privacy Notice for information about retention, access, deletion and other rights.
9. Providers, international processing and contact
Google, Stripe and other external providers may process information in countries other than the country from which you visit, including the United States. The applicable provider notices and our Privacy Notice explain their processing arrangements and relevant safeguards. The cookie and storage names in this policy describe the identified integrations; providers may change names, expiry periods or behaviour as their services evolve.
For questions about this policy, your personal information or your privacy choices, please contact IMI Life Science and identify your request as a data-protection or cookie-policy enquiry. We will update this policy when the website's technologies or relevant practices change. The effective date above identifies this version.