KRIM Logistics — Global Logistics Operating System

Privacy & website preferences

Clear choices. Respectful technology.

Understand how cookies and similar technologies may support KRIM website functionality, security and optional services—and how to manage your choices.

Applies to KRIM digital servicesUpdated 14 November 2026
Important: This notice describes categories and implementation standards. KRIM must verify the actual production cookie inventory and deploy any required consent controls; this notice is not evidence that every control is already live.

KRIM aims to use only technologies that are appropriate for the service being provided, explain their purposes clearly and respect applicable privacy and electronic-communications laws. The specific technologies present may vary by page, device, login state and third-party integration.

1. Scope and purpose

This Cookie Notice explains how the KRIM Logistics website and related online services may use cookies, local storage, session storage and similar technologies. Read it with the Privacy Notice, which explains the wider processing of personal data.

A cookie is a small text file stored by a browser. Similar technologies can store or access information on a device. Their use depends on the page, browser, platform features and services actually enabled.

2. Types of technologies

Strictly necessary

May support security, session continuity, authentication, load balancing, fraud prevention and core site functions.

Preferences

May remember choices such as language, region or interface settings where such features are implemented.

Analytics

May help understand page performance and aggregate usage. These should not be enabled until the provider, purpose and consent requirements are assessed.

Marketing

May measure campaigns or personalise advertising. KRIM should not activate these technologies without the required legal basis and consent.

3. What KRIM currently uses

KRIM's website and platform are evolving. This public notice describes possible technology categories; it is not a verified inventory of every script, cookie, SDK or storage key currently deployed. The actual list must be confirmed through a technical scan of the production website, authentication flows, payment hand-offs and connected third-party services.

Transparency note: KRIM does not claim that analytics, advertising or preference cookies are active merely because they are described in this notice. Before public launch, the operator must record each actual cookie/storage item, its provider, purpose, duration, data recipients and whether it is first- or third-party.

4. Strictly necessary technologies

Where enabled, strictly necessary technologies may be used to provide a service the visitor has requested, maintain secure sessions, protect forms, prevent abuse, remember essential security state or complete a transaction. Some essential functions may not work if these technologies are blocked.

Where applicable law requires consent even for a particular technology, KRIM will obtain it before setting or reading that technology. The “necessary” label does not itself create a legal exemption.

5. Optional analytics and marketing

Optional analytics, personalisation and marketing technologies must remain disabled until KRIM has identified the providers and purposes, assessed the applicable law, supplied clear information and implemented any required consent controls. Where consent is required, it must be freely given, specific, informed, unambiguous and as easy to withdraw as to give.

Rejecting optional technologies should not prevent access to core functions that do not depend on them. KRIM should not bundle optional tracking consent with acceptance of unrelated terms.

6. Third-party services

Some pages may connect to third-party services such as payment providers, identity/authentication tools, embedded media, maps, support tools or analytics providers. Those services may use their own cookies or similar technologies under their own privacy notices and terms.

KRIM must disclose relevant providers and data flows before enabling them, and should configure integrations to minimise unnecessary tracking. A link to an external service does not mean KRIM controls that service's technologies.

7. Payments and authentication

When a customer moves to a payment provider or uses a secure sign-in workflow, the provider may process device or session information needed for security, authentication, fraud prevention and transaction completion. The provider's own notice applies to its environment.

Do not share passwords, one-time passcodes, card PINs or complete payment credentials with KRIM support. Payment pages should be tested to ensure optional tracking is not introduced before any required consent.

8. Managing browser choices

Most browsers allow visitors to review, block or delete cookies through browser settings. Settings differ by browser and device; clearing cookies may sign you out, remove saved preferences or affect site functionality. Browser-level blocking does not necessarily control every form of local storage or third-party processing.

Where KRIM provides a consent or preference control, visitors should be able to revisit it and change their choices. If a preference centre is not available on a page, contact KRIM to ask about the relevant technologies while the site is being updated.

9. Duration and retention

Session technologies generally expire when a browsing session ends, while persistent technologies remain for a defined period or until deleted. The actual duration depends on each item and must be documented in KRIM's live technology inventory. Data derived from cookies is retained according to the applicable purpose, provider terms and KRIM's retention schedule described in the Privacy Notice.

10. International processing

Third-party providers may process device or usage information in countries other than the visitor's country. Before enabling a provider, KRIM must assess the applicable transfer requirements, contractual safeguards, security measures and any local restrictions. The Privacy Notice provides further information about international data handling.

11. Privacy rights and contact

Depending on the visitor's location and applicable law, rights may include access, correction, deletion, objection, restriction, withdrawal of consent or lodging a complaint with a competent authority. These rights and their limits are explained in the Privacy Notice.

For questions about cookies or privacy, use the KRIM Contact page. Do not include passwords, OTPs or sensitive payment credentials in your message.

12. Changes and implementation requirements

KRIM may update this notice when website features, service providers or legal requirements change. The revision date should be updated when material changes are made.

Pre-launch implementation checklist: scan all production pages and authenticated areas; identify cookies, scripts, SDKs and local-storage keys; document providers, purposes and lifetimes; block optional technologies until required consent; provide accept/reject and granular choices where required; store consent records; honour withdrawal; review third-party contracts and international transfers; and re-scan after every material release. This page alone does not prove that a consent-management platform or cookie controls have been deployed.

Questions about privacy or cookies?

Contact KRIM through the official contact page and describe the page or feature you are asking about.

Contact KRIM →