Last updated: July 26, 2026
This Cookies Policy explains how Caldik uses cookies and similar technologies on its websites, dashboard, hosted services, and checkout interfaces. It should be read with the Privacy Policy and Terms of Service. Processing performed for a merchant is also addressed by the Data Processing Agreement.
1. What cookies are#
Cookies are small text files stored on a browser or device. Similar technologies include local storage, session storage, software development kits, pixels, tags, and device or browser identifiers. They can remember settings, maintain sessions, protect accounts, measure performance, and support features.
2. Who sets them#
First-party technologies are set by Caldik or a Caldik-controlled domain. Third-party technologies may be set by providers that supply authentication, payments, security, support, content delivery, monitoring, or analytics.
A merchant may add technologies to its storefront. Those technologies are controlled by the merchant or its provider and should be described in the merchant’s own cookies or privacy notice. Caldik does not authorise merchants to bypass applicable consent requirements.
Caldik may also provide optional first-party storefront analytics for the merchant. Those analytics can use cookies or similar local identifiers, or can measure limited events without a persistent cookie, depending on configuration and applicable requirements.
3. Categories we use#
Strictly necessary#
These technologies are required to provide requested features, maintain sessions, authenticate users, protect forms, balance traffic, prevent abuse, remember privacy choices, and secure accounts. Disabling them may prevent parts of the Services from working.
Functional#
These remember choices such as interface preferences, region, language, storefront state, or optional connected functionality. Where required by law, we use them only with consent.
Analytics and performance#
These help Caldik and merchants understand aggregate use, diagnose errors, measure storefront visits and conversions, display performance analytics in the Caldik dashboard, and improve the Services. We aim to minimise the data collected and configure providers in a privacy-conscious way. Where required, optional analytics are disabled until consent is provided.
Advertising#
Caldik does not currently use cross-site behavioural advertising cookies on its core dashboard unless a cookie notice expressly says otherwise. If we introduce advertising technologies, we will update this Policy and provide legally required controls before using them.
4. Typical cookie details#
The exact names and lifetimes may change as security and infrastructure evolve. The live consent interface or cookie settings page should identify non-essential technologies currently enabled. Typical uses include:
| Category | Purpose | Typical duration | Availability |
|---|---|---|---|
| Necessary | Authentication, session continuity, CSRF protection, security, load balancing, consent state | Session to 12 months | Always active |
| Functional | Preferences and optional interface features | Session to 12 months | Choice where required |
| Analytics | Storefront visits, conversions, aggregate usage, diagnostics, and performance measurement | Session to 24 months | Merchant and visitor controls |
| Advertising | Cross-site or interest-based advertising | Provider-dependent | Not currently used unless disclosed |
5. Consent and controls#
Where law requires consent for non-essential technologies, Caldik or the merchant will request it before use. A storefront visitor can accept, reject, or adjust available categories through the storefront cookie banner or settings interface when the seller has enabled that interface. Withdrawing consent does not affect processing that occurred lawfully before withdrawal.
You can also delete or block cookies using browser settings. Blocking strictly necessary storage may sign you out, prevent checkout or security features, or stop preferences from being saved. Browser-based Global Privacy Control or similar signals will be handled where legally required and technically applicable.
The merchant can opt out of Caldik storefront analytics, disable available analytics collection, or change its storefront cookie and consent configuration through the Caldik dashboard. The merchant’s choice applies prospectively and may not delete historical aggregated analytics, transaction records, security logs, or information retained under the Privacy Policy.
If the merchant has not enabled a visitor-facing cookie interface, browser controls may still be available. The merchant remains responsible for ensuring its storefront configuration and any scripts it installs comply with the laws applying to its visitors.
6. Storefront analytics#
When enabled, Caldik storefront analytics may record events such as page views, referral source, approximate region, device and browser category, product views, cart actions, checkout progress, and completed-order events. Caldik displays relevant analytics to the merchant operating that storefront.
Rejecting optional analytics should prevent future optional analytics events from being associated through the rejected technologies. Strictly necessary events may still be recorded to complete transactions, prevent duplicate orders, secure accounts, detect fraud, balance traffic, calculate usage, and maintain reliable systems.
Merchants that install third-party analytics, advertising pixels, chat widgets, video players, or embedded services are responsible for identifying those providers and configuring them consistently with the visitor’s choices.
7. Authentication and payment providers#
Signing in through Google, Discord, GitHub, or another identity provider may cause that provider to use its own cookies under its policies. Payment and fraud-prevention providers may use necessary technologies to secure checkout, prevent fraud, remember transaction state, and comply with legal obligations.
8. Local storage and similar technologies#
Local storage and session storage may retain authentication state, checkout state, consent choices, interface preferences, temporary identifiers, and fraud-prevention information. These technologies may persist differently from ordinary cookies and can usually be cleared through browser site-data controls.
9. Do Not Track#
Some browsers send a Do Not Track signal, but there is no universally accepted response standard. We respond to legally recognised preference signals where required and otherwise rely on the controls described above.
10. Retention#
Cookie duration depends on its purpose. Session cookies generally expire when the browser session ends. Persistent cookies remain until their stated expiry or deletion. Related server-side logs may be retained separately under the Privacy Policy.
11. Changes to this Policy#
We may update this Policy when our technologies, providers, or legal obligations change. We will update the date above and, where required, request consent for materially different non-essential uses.
12. Contact#
Questions about cookies or privacy may be sent to support@caldik.com.