Privacy and trust

Cookie & Storage Policy

Connect2Code currently uses required authentication and local feature storage, not advertising or analytics cookies.

Last reviewed 17 November 2026

Current use

The reviewed frontend does not install analytics, advertising, social-pixel, or behavior-tracking tools. It does not create a marketing cookie.

A consent banner is therefore not shown merely to obtain consent for required authentication or user-requested local features. If optional analytics, advertising, or other non-essential storage is introduced, it must remain disabled until the required choice is obtained, and this policy and the preference controls must be updated first.

Cookie and storage inventory

MechanismPurposeOwnerDuration / removalRequired
Refresh-session cookie (exact name unverified)Restore and rotate an authenticated sessionConnect2Code APIBackend-configured; exact lifetime and flags require owner verificationYes, for signed-in sessions
In-memory access token and user identityAuthorize protected API requests in the current tabConnect2Code frontendUntil refresh, logout, session failure, or page close/reloadYes, for signed-in features
Account-scoped local storageTheme, progress cache, and code draftsConnect2Code frontendUntil removed in-app or through browser controls; logout preserves themeFeature storage
Session storageReturn path after sign-in and one-time logout noticeConnect2Code frontendCurrent browser tab/session or earlier application removalYes, for the requested flow
BroadcastChannel / transient storage eventNotify other same-origin tabs that session state changed; contains no token or profileConnect2Code frontendMessage-only; fallback marker is removed immediatelySession coordination

Third-party browser requests

Google Fonts and cdnjs currently receive requests for font and icon assets when the document loads. These are network requests, not Connect2Code marketing cookies. Their providers may receive ordinary request metadata such as IP address and user-agent information under their own practices.

Choosing Google sign-in navigates to the backend-managed Google OAuth flow. External company or problem links and some remote images may contact their destination when opened or loaded.

Your controls

  • You can block or remove cookies and site storage through your browser. Blocking the refresh cookie will prevent signed-in session restoration.
  • Use the Data & Account Rights page to clear Connect2Code data for the active account from this device.
  • There is currently no optional analytics category to enable or disable, so a preference toggle would not change any tracking behavior.

Backend verification still required

The API owner must confirm the refresh cookie’s name, Secure, HttpOnly, SameSite, Path, Domain, expiry, rotation, revocation, and whether any server-side service adds cookies or analytics not visible in this frontend repository.