Legal Center
Cookies & Storage

Cookie Policy

This policy explains how MakerHub uses cookies, browser storage, and operational diagnostics to support secure authentication, saved preferences, and reliable platform operation.

Effective date: March 10, 2026
Last updated: March 10, 2026

Contract Priority

This public page complements your signed agreement, collection notices, and local legal review. If there is a conflict, the signed agreement controls.

Audience

Written for school authority, board, district, and education authority deployments in a school-managed environment.

01

Overview

This Cookie Policy explains how MakerHub uses cookies, local storage, session storage, and similar browser technologies when users access the platform.

These technologies help deliver secure authentication, maintain user preferences, recover from failed loads, and support platform reliability in school-managed environments.

02

Categories of Technologies We Use

MakerHub uses a limited set of storage technologies based on functional necessity, security requirements, and user experience needs.

  • Strictly necessary technologies for authentication state, session continuity, route protection, and platform operation.
  • Security and integrity technologies used to validate sessions, detect abuse, and maintain account security.
  • Preference storage such as theme selection, timer settings, and other user convenience settings.
  • Operational recovery storage used to recover from failed chunk loads or temporary client-side faults.
  • Operational diagnostics and logging used to support reliability, troubleshooting, and platform maintenance.
03

What We Do Not Use

MakerHub does not sell personal information through cookies or similar technologies.

MakerHub does not use student cookies or persistent identifiers for targeted advertising or cross-context behavioral advertising.

04

Third-Party Storage

Where MakerHub relies on contracted infrastructure, authentication providers, billing providers, or embedded content, those services may set technical cookies or similar identifiers required for their secure operation.

Examples may include Google or Firebase authentication flows, Stripe billing pages, or third-party embedded media enabled by the institution.

Those third-party technologies are governed by the applicable provider relationship and, where relevant, the provider's own terms or notices.

05

Browser and Device Controls

Users and institutions can manage cookie and storage settings through browser controls, device settings, and enterprise policy tooling.

Blocking strictly necessary technologies may prevent login, class access, saved preferences, password reset completion, and assignment workflows from functioning correctly.

06

Retention

Storage duration varies by purpose. Session-related technologies typically expire automatically after sign-out or inactivity, while preference settings may persist until cleared by the user, institution, or browser.

07

Updates and Contact

MakerHub may revise this policy as platform features, vendors, or legal requirements evolve. Updated versions will include a revised effective date.

Questions about platform browser storage can be sent to support@makerhub.app. Institution-specific privacy questions should be directed to your school authority or school privacy contact.