Cookie Policy
Controller: Queflornchor, Torggata 1, 0181 Oslo, Norway · Email: support@queflornchor.world · Phone: +47 24 15 50 50 · Effective date: 25 March 2026
This Cookie Policy explains how we use cookies, local storage, pixels, and similar technologies (together, “cookies”) on https://queflornchor.world and related landing pages. It should be read together with our Privacy Policy, which describes broader processing of personal data.
1. What cookies are
Cookies are small text files placed on your device when you visit a website. They allow the site to recognise your browser, remember preferences, keep you signed in where applicable, measure performance, and, when you consent, support marketing measurement. Similar technologies include HTML5 local storage, session storage, software development kits in apps, and tracking pixels that load when you open an email or page.
2. Legal framework in Norway and the EEA
The Norwegian Electronic Communications Act implementing the ePrivacy Directive requires consent for non-essential storage or access to information on your device, subject to limited exceptions for strictly necessary communications. The GDPR applies when cookies involve processing of personal data, such as unique identifiers linked to your device or account. We document consent through our banner and store a record of your choices in local storage on your browser.
3. How you can control cookies
You can reopen the preference centre at any time by clearing site data and reloading the page, which will display the banner again, or by contacting us for manual guidance. Major browsers let you block third-party cookies, delete existing cookies, or alert you before storage. Note that blocking strictly necessary cookies may prevent checkout, security checks, or consent recall from functioning.
4. Categories we use
4.1 Strictly necessary
These cookies are essential to deliver the service you request. They include security tokens, load-balancing flags, cookie consent state, session identifiers for forms, and fraud prevention signals from payment partners during checkout. They do not require consent under ePrivacy implementations because they are strictly necessary. You cannot disable them through our banner because the site would not operate safely.
4.2 Functional preferences
Where enabled, we may remember choices such as language, accessibility contrast, or collapsed sections. If these cookies are not strictly necessary, we will only activate them after consent or derive them from browser defaults without storing identifiers beyond the session.
4.3 Analytics
If you opt in, we may deploy first-party or privacy-oriented analytics to understand aggregate traffic, scroll depth, and error rates. Identifiers may include a random client ID stored in a cookie. We configure data retention to the shortest practical period compatible with statistical reliability, typically up to fourteen months. You may withdraw consent at any time; withdrawal does not affect prior aggregated reports that no longer identify you.
4.4 Marketing
With consent, we may load pixels from advertising partners to attribute visits to campaigns, build anonymised lookalike segments, or measure conversions. Partners act as independent controllers or processors according to their policies. We minimise data shared and honour industry opt-out tools where available in addition to your banner choice.
5. Specific cookies and storage keys
The exact names may change when we update software. Representative examples include:
| Name or key | Category | Purpose | Duration |
|---|---|---|---|
| digestivae_consent_saved | Strictly necessary | Remembers that you saved cookie choices | Persistent until cleared |
| digestivae_cookie_prefs | Strictly necessary | Stores JSON object of category toggles | Persistent until cleared |
| sessionid | Strictly necessary | Maintains server session when logged in | Session or 24 hours sliding |
| analytics_id | Analytics | Random identifier for visit stitching | Up to 14 months if consented |
| campaign_ref | Marketing | Stores attributed campaign code from URL parameter | 90 days if consented |
6. Third-party modules
Embedded content such as maps or videos may set their own cookies. We only embed providers that offer GDPR-compliant terms. If you do not consent to marketing, we avoid loading social widgets that track cross-site behaviour.
7. Consent withdrawal and frequency
Withdrawing consent is as easy as giving it. Use “Cookie settings” on the banner, toggle categories off, and save. We will stop non-essential reads and writes promptly, although some aggregated logs may remain in backups until overwritten. We re-prompt visitors when we introduce materially new trackers or after twelve months of stored consent, whichever comes first.
8. Children
We do not direct non-essential tracking at children. Parental devices should use browser parental controls if minors browse the Site.
9. Updates
When we change this Cookie Policy, we update the effective date and, where required, refresh consent for new purposes. Archived versions are available on request for accountability.
10. Interaction with browser privacy modes
Private browsing windows typically delete cookies at the end of the session, which will reset your consent choices and may cause the banner to reappear. Do-not-track signals are not universally standardised; our banner remains the authoritative control for non-essential cookies on this Site.
11. Logs and pseudonymous identifiers
Even when analytics cookies are refused, server logs may contain IP addresses for security. Those logs are rotated and access-restricted as described in the Privacy Policy. We do not reconnect refused analytics cookies with log data for marketing profiling.
12. Social and video embeds
Product education pages may link out to videos rather than embedding them, reducing third-party cookies until you actively click. Where embeds are used, we apply privacy-enhanced modes where the provider supports them and delay loading until consent.
13. Accountability records
We maintain internal records of template versions, deployment dates, and consent statistics in aggregated form to demonstrate compliance to regulators upon request.
14. Contact
Email support@queflornchor.world with “Cookie inquiry” in the subject line, or write to Queflornchor, Torggata 1, 0181 Oslo, Norway.