Cookies are small pieces of data stored by your browser when you visit a website. They help sites remember settings, maintain sessions, and deliver personalized experiences. This article explains common cookie types, why some are essential for site operation, how long they last, and what their legal basis typically is — using a practical example cookie table.
Introduction
This guide focuses on essential and functional cookies used to operate a website reliably. It’s aimed at website users and site administrators who want a clear, practical explanation of cookie purposes, durations, and privacy considerations. The primary keyword: “cookie name” appears early to frame the discussion of specific cookies such as LBSESSIONID and agreed18.
What cookies do and why some are required
- Session management: Cookies keep you logged in as you navigate pages on sites that use multiple backend servers. Without them, users may be repeatedly asked for passwords.
- Preferences and localization: Cookies store language choices and device-type information so pages display in the preferred language and format.
- Promotional features: Some cookies enable campaign-specific pricing or offers so users see correct promotions.
- Consent and UI behavior: Cookies remember if you dismissed an age-warning or cookie settings popup to avoid showing it repeatedly.
Example cookie purposes and durations
Below are common cookie examples and why they exist.
- LBSESSIONID — Purpose: Avoid asking for passwords on each backend server by implementing sticky sessions; Legal basis: legitimate interest; Duration: Session.
- agreed18 — Purpose: Record that an adult warning and cookie selector popup was shown and acknowledged; Legal basis: legitimate interest; Duration: 30 days.
- pop_price — Purpose: Enable promotional pricing during campaigns so the site shows better price offers when relevant; Legal basis: legitimate interest; Duration: 7 days.
- devtype — Purpose: Identify device type to adapt layout and features for mobile vs desktop; Legal basis: legitimate interest; Duration: 30 days.
- customLang — Purpose: Remember the language a customer selected so the site reopens in that language; Legal basis: legitimate interest; Duration: 30 days.
- lang — Purpose: Short-term language indicator to manage immediate display; Legal basis: legitimate interest; Duration: 1 hour.
- calculatedLangFrom — Purpose: Track how the language was determined (user choice, existing cookie, browser language, GeoIP) to improve UX; Legal basis: legitimate interest; Duration: 30 days.
- limited-offer2 — Purpose: Similar to pop_price, supports showing promotional prices for campaigns; Legal basis: legitimate interest; Duration: 30 days.
- personalized_experience — Purpose: Store the summary of user-determined cookie preferences (which cookies the user allowed or refused); Legal basis: legitimate interest; Duration: 30 days.
Legal basis and privacy considerations
- Legitimate interest: Many operational cookies rely on legitimate interest because they are necessary for core functionality (e.g., session cookies). Sites should document why these cookies are necessary and perform a Legitimate Interests Assessment (LIA) where required.
- Consent: Non-essential cookies (analytics, advertising, personalization beyond basic UX) typically require explicit user consent under privacy laws such as GDPR. Even for legitimate-interest cookies, clear transparency in a cookie policy is best practice.
- Minimization: Store only what is necessary and keep durations reasonable (session or limited days). Use secure attributes and limit access to cookies to reduce risk.
Best practices for site owners
- Classify cookies clearly into categories: necessary, preferences, statistics, marketing. Necessary cookies should be explained and marked as always active if that’s the policy.
- Provide a concise cookie table: list cookie name, purpose, legal basis, and duration so users and auditors can quickly understand each cookie’s role.
- Offer granular controls: allow users to accept or reject non-essential cookies and save those preferences (e.g., personalized_experience).
- Keep language options consistent: use short-lived cookies for immediate language handling (lang) and longer-lived cookies for saved preferences (customLang).
- Document session handling: explain why session cookies like LBSESSIONID are required to avoid repeated logins on multi-server architectures.
Practical example: How a cookie table helps users
A clear cookie table helps users see at a glance:
- Which cookies are essential and always active (e.g., LBSESSIONID).
- Which cookies enable features they might care about (language, offers).
- How long each cookie will remain, allowing users to make informed privacy choices.
Implementation tips for developers
- Use secure, HttpOnly flags for sensitive cookies when appropriate.
- Limit cookie scope with path and domain attributes.
- Rotate or expire cookies used for promotions to avoid stale offers.
- Store only non-identifiable data in long-lived cookies; prefer server-side sessions for sensitive user state.
- Log and surface cookie preferences in a single summary cookie (like personalized_experience) to simplify compliance and UX.
Conclusion
Cookies power many everyday website functions from login persistence to language preferences and promotional pricing. Understanding cookie names, purposes, durations, and their legal basis helps both users and site owners make better decisions about privacy and functionality. Maintain clear documentation (a cookie table), follow privacy best practices, and make consent and preference controls simple to use to balance a smooth user experience with regulatory compliance.