Cookie Preferences
1. Categories
We group cookies into essential, preference, and analytics categories. Essential cookies keep sessions secure and remember cookie choices themselves. Preference cookies remember UI states such as reduced motion or newsletter dismissal. Analytics cookies help us understand aggregate navigation patterns without selling data.
The table in the third-parties section lists representative names and purposes; exact names may rotate as we patch software.
2. Consent
On your first visit, we present a compact toast that explains essential cookies and invites you to opt into analytics. Rejecting analytics does not block the site. You may reopen preferences through the footer link labeled Cookie Preferences.
Consent records are stored locally in your browser using a brand-prefixed key so we do not have to show the toast on every page load once you decide.
3. Contact
Questions about cookies or this policy can be emailed to hello@network-nodehub.one. If you need evidence of consent timestamps for an audit, explain your role and the approximate enrollment date so we can correlate internal logs responsibly.
We do not operate a call center solely for cookie questions; email remains the primary channel.
4. What are cookies
Cookies are small text files stored on your device by a website. They can be session-length or persistent, depending on configuration. Similar technologies include local storage entries that remember non-sensitive UI preferences when we avoid server round trips.
Cookies cannot execute arbitrary programs on modern browsers, but they can carry identifiers, so we limit what we store and rotate identifiers when practical.
5. Preferences
Preference storage keeps the site usable, for example remembering that you expanded a navigation panel or chose a high-contrast theme if we offer one. These values are scoped to our domain and are not used for cross-site advertising.
You may clear preferences by clearing site data in your browser; the cookie toast may reappear afterward.
6. Third parties
We aim to avoid third-party advertising pixels. If we embed a map link that sets its own cookies when opened, that processing happens on the map provider after you leave our origin. Analytics, when enabled, may use a first-party proxy style configuration to reduce referrer leakage.
Representative cookies: network-nodehub.one_cookies (essential, 12 months, NodePilot Academy) stores essentials versus analytics-on choices; network-nodehub.one_theme (preference, 12 months, NodePilot Academy) stores light or dark presentation preference; session identifiers issued by the learning portal while you are signed in (essential, session, NodePilot Academy).
7. Managing cookies in browsers
Major browsers let you block third-party cookies, delete existing cookies, or alert you before a site stores data. Instructions differ by vendor and version, so consult your browser help center for the latest clicks.
Blocking all cookies may break portal login persistence until you allow first-party cookies again.
8. Impact of disabling
Disabling analytics does not remove your ability to read marketing pages or submit contact forms. Disabling essential cookies will likely break session continuity and may prevent the site from remembering that you already answered the cookie prompt.
If you use aggressive privacy extensions, whitelist our domain if you need reliable form submissions.
9. Retention of logs
Server access logs that might include cookie-related headers are retained for security investigations on a rolling basis, typically ninety days, then aggregated or deleted unless a security incident extends retention.
Aggregated statistics do not attempt to re-identify individuals.
10. Updates
When we add a new analytics component, we will update this policy and reset consent if law requires. Minor clarifications may occur without resetting consent, provided processing stays within the described purpose boundaries.
Cross-links to the Privacy Statement remain available in the footer Compliance column.
11. Accountability
We maintain internal records of who approves cookie banner copy changes and when engineering deploys related code. Learners may request a plain-language summary of those records during business disputes, subject to confidentiality obligations.
This accountability section does not create third-party beneficiary rights beyond what law mandates.