Cookies and local storage
Last updated:
Technical information Arrangely stores in your browser and why.
Sign-in
__Host-kc_session (kc_session in local development) keeps you signed in for up to 30 days. It uses HttpOnly, Secure in production HTTPS environments, and SameSite=Lax. Signing out ends the corresponding server session.
Guest workouts
__Host-kc_training_guest (kc_training_guest in development) distinguishes guest browsers for workouts and completion history for up to 365 days. It is not used for advertising. Clearing cookies may prevent your browser from recognizing earlier guest activity, but does not delete the coach’s records.
Interface storage
Local storage supports language, interface preferences and recovery of unsaved changes. These are not advertising identifiers. Retention depends on the entry and browser cleanup; some settings remain until cleared.
During email confirmation, sessionStorage temporarily keeps the link token in the current tab across sign-in. It is removed after successful confirmation or when the tab session ends. Password recovery uses a separate temporary sessionStorage token for up to 30 minutes in the current tab; it is removed after a successful password change.
The current Arrangely code does not include advertising pixels or third-party behavioral analytics. Admin account statistics are calculated on the server. New analytics or other optional trackers require separate assessment and, where required, consent before activation.
External sites and media
Opening an external link or loading user-added media may involve another site’s cookies and rules. That site’s policy applies; these are not included in Arrangely’s technical cookie list.
Your controls
You can clear or block cookies and local data in your browser. This may sign you out, reset preferences and stop earlier guest actions being recognized. Strictly necessary storage supports features you request and does not imply consent to advertising.