Strictly necessary
Authentication, security, load-balancing, CSRF protection, consent memory, and other storage strictly required to deliver the service a visitor requests.
Cookie Policy
This page explains how REM Nutrition uses cookies and similar client-side storage technologies across this Django website, how consent is collected, how geographic localization is applied, and how visitors can update their choices at any time.
The implementation is privacy-first: strictly necessary storage is allowed for security and service delivery, while non-essential storage is blocked until an affirmative choice is recorded. Where a more permissive legal model exists, this implementation still applies the stricter standard by default.
Preferences
Storage used to remember interface choices such as theme, language, or dashboard-state preferences.
Analytics
Storage used to measure traffic, diagnose performance, or understand aggregate usage patterns.
Marketing
Storage used for advertising, remarketing, audience matching, social-media tracking, or cross-site profiling.
Legal baseline and regional handling
European Union / EEA
The implementation applies prior blocking for non-essential storage, no pre-ticked choices, easy refusal, category-level consent, and withdrawal at any time. This baseline is aligned to the GDPR consent standard and Article 5(3) of the ePrivacy Directive as interpreted in Planet49.
United Kingdom and Switzerland
The same strict prior-consent flow is applied for non-essential storage, with necessary-only storage allowed before consent and refusal available at the same level as acceptance.
United States privacy-law states
The system exposes clear notice, granular settings, and server-side handling for Global Privacy Control and sale/share opt-out signaling. Because this implementation blocks non-essential storage until an affirmative action, it is stricter than the minimum notice-and-opt-out model used in parts of the U.S.
Canada, Brazil, Australia, New Zealand, South Africa and other mixed-regime jurisdictions
The implementation uses a privacy-by-default consent standard for non-essential technologies, coupled with detailed disclosures, auditable consent events, and easy withdrawal. That is intentionally conservative where local rules are less explicit than EU ePrivacy rules.
Important limitation
No software-only implementation can guarantee legal compliance for every controller obligation worldwide. Actual compliance also depends on your final cookie inventory, third-party vendors, records of processing, retention practices, contractual terms, and ongoing legal review.
Geo-IP and signal handling
The system selects banner language and legal posture using a conservative hierarchy: trusted reverse-proxy country headers when present, an optional local GeoIP database if configured, and finally a default-country fallback for private or internal-network addresses. No paid CMP dependency is required for that flow.
Global Privacy Control signals are honored when present. In practice, that means marketing consent is forced off and sale/share-style choices remain opted out.
Cookie and storage inventory
| Name | Type | Category | Duration | Purpose | Legal basis |
|---|---|---|---|---|---|
| sessionid First party |
HTTP cookie | necessary | Up to 14 days | Keeps an authenticated session alive and ties requests to the current server-side session state. | Strictly necessary to provide logged-in account features requested by the user. |
| csrftoken First party |
HTTP cookie | necessary | Up to 364 days | Protects forms and authenticated actions against cross-site request forgery attacks. | Strictly necessary security storage. |
| rem_cookie_consent First party |
HTTP cookie | necessary | Up to 365 days | Stores the current cookie-preference state and policy version so the site can honor the visitor’s choice. | Strictly necessary to remember and enforce the visitor’s privacy choices. |
| django_language First party |
HTTP cookie | preferences | Browser or language-cookie setting dependent | Remembers the visitor’s chosen language where the language switcher is used. | Consent for preference storage where deployed. |
| theme First party |
Local storage | preferences | Persistent until changed or cleared | Stores the preferred color theme selected through the UI theme toggle. | Consent for preference storage where deployed. |
| rem_analytics_vid First party |
HTTP cookie | analytics | Up to 180 days | Stores a pseudonymous first-party visitor identifier used only for internal analytics on this website. | Consent for analytics storage. |
| rem_affiliate First party |
HTTP cookie | marketing | Up to 30 days | Stores the referring affiliate or partner code for first-party attribution and commission logic. | Consent for marketing / attribution storage. |
| django.admin.navSidebarIsOpen First party |
Local storage | preferences | Persistent until changed or cleared | Remembers whether the admin-style navigation sidebar is open or collapsed. | Consent for preference storage where deployed. |
| django.admin.navSidebarFilterValue First party |
Session storage | preferences | Until the browser tab or session ends | Remembers the current admin-style navigation filter during the browsing session. | Consent for preference storage where deployed. |