QC NetCore
HomeSign In
Privacy & DataLast updated: October 2026

Cookie & Local Storage Policy

Transparent documentation of the essential cookies and browser storage keys used by QC NetCore for authentication, theme preferences, and interactive demo isolation.

Key Compliance Highlights
  • QC NetCore uses strictly necessary cookies and localStorage keys for authentication, dark/light theme persistence, and interactive Demo Mode isolation.
  • We do NOT deploy intrusive third-party behavioural advertising cookies or cross-site tracking pixels.
  • Documents the exact browser storage keys used in production so operators and auditors can verify them directly in browser DevTools.

Section 1How QC NetCore Uses Cookies & Browser Storage

Cookies are small text files placed on your device by a web server, while browser `localStorage` allows web applications to store configuration state locally within your browser. QC NetCore uses these mechanisms strictly to keep your operator session authenticated, remember your visual theme preference, and isolate interactive Demo Mode testing from production databases.

Section 2Inventory of Cookies & LocalStorage Keys Used

In accordance with engineering transparency, below are the exact cookies and localStorage identifiers utilized by the QC NetCore web application:

  • Supabase Auth Session Cookies (`sb-*-auth-token`): Strictly necessary HTTP/browser cookies used to maintain authenticated ISP operator sessions and enforce Row-Level Security.
  • Demo Mode Session Cookie (`gtech_demo_mode`): Functional cookie set when you click 'Explore Demo' or visit a `?demo=true` route, allowing you to explore the full operator dashboard with realistic sample telemetry without requiring login.
  • Theme Preference (`gtech_theme` in localStorage): Stores your chosen interface appearance (`dark` or `light`) so the platform renders without visual flash on page reload.
  • Isolated Captive Portal Demo State (`qc_netcore_demo_captive_v1` in localStorage): Stores temporary branding and package customizations made inside the interactive Captive Portal Demo Customizer so your browser preview updates live without altering production tenant records.
  • Cookie Notice Acknowledgment (`qc_netcore_cookie_consent_v1` in localStorage): Remembers your acknowledgment or preference selection on the QC NetCore cookie notice banner.

Section 3Absence of Third-Party Advertising Trackers

QC NetCore does not embed third-party ad-network cookies, retargeting pixels, or cross-site behavioral profiling scripts on the operator console or subscriber captive portals.

Section 4Managing or Clearing Cookies & Local Storage

You can review, reset, or clear your QC NetCore cookie preferences at any time via the Cookie Notice banner or through your browser's privacy settings. Note that blocking strictly necessary authentication cookies (`sb-*-auth-token`) will prevent you from signing into protected operator dashboard routes.

Questions About This Policy or Compliance Verification?

Reach our legal, privacy, billing, and security engineering desk directly via email or WhatsApp.

WhatsApp 0712052104quantumcode7777@gmail.com