Cookie Policy

What this policy covers

This policy describes the browser storage and similar technologies actually used by the current BodyTrainingGuide frontend. Cookies are small data files stored by a browser; local storage is browser storage that is not automatically sent with each request.

Current technology inventory

Managed optional services

No optional statistics, advertising or preference service is currently declared in this registry.

This list is updated when new services are added to the cookie manager.

Requested features and security

The HttpOnly user_jwt and admin_jwt cookies maintain requested member and administrator sessions for up to 12 hours. Administration uses local storage keys mt_admin_posts (editor data) and admin-header-hidden (header control). The API’s separate administration panel uses adminToken for authentication. These keys are preserved. Newsletter submissions and food searches use the application’s endpoints; Open Food Facts is queried by the API. Barcode scanning requests camera permission when used and does not introduce a tracking cookie. Content images can use the configured image hosts (including Unsplash and CloudFront). JSON-LD scripts contain structured content, not an analytics SDK.

Server and third-party merchant data

Hosting and security systems may process ordinary request data such as IP address, user agent, requested URL, and timestamps in server logs without using an optional browser cookie. If you follow a link to a third-party merchant, that party may use its own cookies under its own policy and controls; BodyTrainingGuide does not control those technologies.

Your controls and future changes

Use “Manage my cookies” in the footer at any time. With an empty optional registry, the customization panel reports that no optional cookie is managed. The banner remains visible without preventing browsing. Acceptance and refusal are saved in local storage under btg_consent, containing only accepted categories, the choice date and the registry/policy version. The choice expires six calendar months after it is made; visits do not extend it. Missing, expired, unreadable or outdated choices keep optional services blocked, as does unavailable browser storage. A changed registry requires a new choice. You can accept, refuse, customize or withdraw consent. Withdrawal stops the affected services and attempts to remove only their explicitly identified first-party storage; a reload is used if a running service cannot stop cleanly. Third-party domain cookies and HttpOnly cookies cannot be deleted by this manager.

Contact

Questions about this policy may be sent to support@2dolist.fr.