Cookie Policy
Effective from 3 September 2026. Version 2026-09-03.1.
This policy explains how killandermusicrecords.com uses cookies and similar technologies. Please also read the Privacy Policy, which explains personal data processing and your rights.
What cookies and similar technologies mean
A cookie is a small text file stored by your browser. The website may also use localStorage, sessionStorage, technical network requests, security services and embedded features. Not all of these technologies are cookies in the strict sense, but they are described together because they may store or read information on your device or send technical information to a provider.
Categories
Necessary
Needed for security, form protection, consent management and basic operation. They cannot be disabled through the cookie tool where they are strictly necessary for a service that you request.
Functional
Remember choices or display features not required for the core content, such as language selection and a reviews widget. They are used only after your consent.
Statistics (”Statistik” in the interface)
Help measure usage and improve the website. They are used only after your consent.
Marketing
Used for advertising measurement, audiences, personalisation and newsletter features. They are used only after your consent. A message subscription also requires you to actively subscribe.
Strict basic mode and your choice
The website uses strict Basic Consent Mode. Google Tag Manager and Google tags for statistics or marketing are blocked before the relevant consent and blocked again after consent is withdrawn. Consent to statistics does not enable marketing. The core content and protected contact forms work with necessary technologies only; language memory, reviews, statistics, marketing and MailerLite forms may then be unavailable.
In the first banner, the “Anpassa” (“Customise”) button opens detailed choices. Afterwards you can use the persistent cookie icon, whose accessibility name is “Anpassa cookieinställningar” (“Customise cookie settings”), at any time and change or withdraw your choice as easily as you gave it. The change stops future optional loading in accordance with the new choice. It does not affect processing that was already lawful or data already sent to a provider.
The consent choice remains valid for no more than 365 days. A new choice may be requested earlier if technologies, purposes or the policy version change materially.
Technologies and providers
| Provider | Technology or name | First or third party | Category | Purpose | Activation | Duration |
|---|---|---|---|---|---|---|
| KMR Consent Manager | localStorage: stcm.kmr-consent-v1.*, kmr-consent-v1.consent.meta and kmr-consent-v1.receipt.subject, receipt.outbox and receipt.failure; receipt requests to the website’s own API | First party | Necessary | Stores the choice and metadata plus necessary consent documentation: a pseudonymous consent reference, a local queue for receipts not yet delivered and a failure status. | When the consent tool is used and on page load to apply a saved choice. | Choice and metadata for up to 365 days; consent reference until cookie settings are reset; queue until successful delivery; failure status until the next receipt is stored. Pseudonymous server receipt for 760 days. |
| Locally bundled Silktide core | localStorage: __stcm_test__ | First party | Necessary | Checks whether the browser can store consent choices. | Temporarily when the consent tool starts. | Deleted immediately after the test during the page load. |
| Forminator | First-party request for forminator_get_nonce | First party | Necessary | Obtains a fresh CSRF token so that a cached form can be submitted securely. | When a Forminator form is displayed or used. | One request; no separate storage was observed for the nonce request. |
| hCaptcha | Challenge, security and verification requests and hCaptcha’s necessary browser signals | Third party | Necessary | Protects forms and the website against spam and automated abuse. | On pages or in flows where a protected form is used. | Session or up to 30 days depending on the security feature. |
| Cloudflare for hCaptcha | Cookie on api2.hcaptcha.com: __cflb | Third party | Necessary | Keeps hCaptcha verification requests on the same healthy backend during the session. | When hCaptcha performs a verification. | From a few seconds to no more than 24 hours according to the session-affinity configuration. |
| Cloudflare | Cookie: __cf_bm | Third party | Necessary | Identifies and limits malicious or automated traffic. | When bot and security protection needs to assess traffic. | 30 minutes of inactivity. |
| Polylang | Cookie: pll_language | First party | Functional | Remembers the language choice and uses the same language in relevant website requests. | After functional consent. | Polylang’s documented default is one year. The cookie was not observed in the 0.3.1 production matrix and is listed only as a possible language-choice technology. |
| Google Tag Manager | gtm.js and container requests | Third-party requests to Google | Statistics or Marketing | Loads only the Google tags whose purpose you have accepted; it has no separate purpose. | Only after the relevant statistics or marketing consent; blocked before consent and after withdrawal. | Individual requests and the current browser session; storage from delivered tags is listed separately. |
| Google Analytics 4 | Cookies: _ga and _ga_BGLXRYZXPJ; Google tag requests, statistics requests and pseudonymous measurement identifiers | First-party cookies; data is disclosed to a third party, Google | Statistics (”Statistik” in the interface) | Measures visits, usage and technical performance to improve the website. | After statistics consent. | Both observed cookies can remain for up to two years. Event-level and user-level data are deleted according to the actually active GA4 setting; aggregated reports may remain for longer. |
| Google Ads | Cookie _gcl_au (90 days), test_cookie on doubleclick.net (15 minutes), localStorage _gcl_ls and conversion, audience and consent signals | First-party storage and a third-party cookie; data is disclosed to Google | Marketing | Measures advertising and may, depending on enabled Google features, be used for audiences and personalised advertising. | After marketing consent. | _gcl_au for up to 90 days and test_cookie for about 15 minutes. _gcl_ls had no fixed expiry in the test evidence and may remain until Google replaces it or site data is cleared. |
| Trustpilot | Widget and network requests to Trustpilot | Third party | Functional | Displays reviews and ratings that you choose to view. | After functional consent when the widget is displayed. | Varies by service signal; no fixed local retention period has been added beyond observed technology. |
| MailerLite | Embedded newsletter form and network requests to MailerLite and mlcdn | Third party | Marketing | Displays and measures the newsletter form. Data is sent when you use the form, and a subscription requires a separate choice. | After marketing consent and when the form is used. | Varies by service signal and the actually active form and provider configuration; no fixed period is asserted here. |
More information from providers
- Silktide’s information about the locally bundled consent core.
- Google Business Data Responsibility, Google’s use of data from partner sites and Google’s Privacy Policy.
- hCaptcha’s Privacy Policy.
- Cloudflare’s Privacy Policy and Cloudflare’s cookie information.
- Forminator on WordPress.org and WPMU DEV’s Privacy Policy.
- Polylang’s Privacy Policy and Polylang’s cookie documentation.
- Trustpilot’s privacy information and Trustpilot’s Cookie Policy.
- MailerLite’s Privacy Policy and MailerLite’s Cookie Policy.
Browser settings and supervision
You can also delete or block storage in your browser settings. This does not replace the website’s consent withdrawal control and may cause the website to ask you again. See the Swedish Post and Telecom Authority’s cookie information. Questions about personal data are handled under the Privacy Policy.
Svenska
