nAble Academy · Legal information

Cookie Policy

This draft covers cookies and similar browser technologies, including local storage and session storage. It distinguishes the integrations visible in the current source from settings that may be enabled later.

Draft prepared 12 November 2026 · Requires operator/legal review

1. Cookies and similar technologies

Cookies are small values stored by a website in a browser. Websites can also use local storage, session storage, pixels and scripts to store or access information on a device. This policy covers those technologies, not only items technically named "cookies".

2. What the current application uses

A review of the application source on 12 November 2026 found no analytics SDK, analytics tag or analytics tracking script. The review did find browser storage used for authentication, session continuity, consent choices, local feature state and appearance preferences.

The source also contained a first-party sidebar_state cookie write with a seven-day expiry. No code path reading that cookie was found, so this release removes that unused write rather than continuing to set a cookie that does not currently restore a setting.

This code review is not a complete browser-level cookie scan. Cloudflare zone settings, response headers and third-party scripts can issue cookies that are not visible as direct document.cookie writes in application source. The Operator must verify the production inventory with browser developer tools and provider dashboards.

3. Browser storage inventory in the application source

Technology / keyPurposeLifetime / control
Supabase Auth local-storage key (sb-[project]-auth-token)Maintains an authenticated session so a signed-in user can continue using the school platform.Managed by Supabase Auth and browser storage lifecycle. Signing out removes the active session; browser controls can clear it. Exact token expiry follows the production Supabase Auth configuration.
naable-session-bundle-v1 (session storage)Session/profile cache used while restoring the authenticated application view.Browser-tab session storage; cleared when the tab/session storage is cleared.
nable-privacy-consent-v1 (local storage)Remembers the user's necessary-storage acknowledgement and optional preference choice so the privacy banner does not reappear on every page.Until browser data is cleared or the user changes the choice using Cookie settings. Consent versioning permits a new notice to be shown after a material policy update.
naable-appearance and legacy theme (local storage)Remembers a selected appearance theme when optional preference storage is allowed.Until removed by the user, browser controls or Cookie settings. Without preference consent, the current visit uses a default appearance and does not persist a selection.
App feature storage (local storage)The source includes user-scoped Question Bank question and purchase caches (qb_store_questions_v2:{userId}, qb_store_purchases_v2:{userId}) and a pending sync queue (qb_sync_pending_queue_v2:{userId}). It also includes notification read markers, Question Bank board/year choices, interactive diagram state and offline-runner score/player-label values.Varies by feature. The Question Bank's per-user cache and pending sync queue are deliberately retained on sign-out so a pending cloud sync can resume; relevant account/data controls or browser site-data clearing remove them. Exact expiry and cleanup behaviour must be verified per feature before publication.

The entries above describe source-level storage keys reviewed for this draft. This is not a claim that they are the only keys or cookies in every production configuration.

The source also contains an older persistent mock-data store usingeduflow_db, plus mock student and academic-data modules that can write local data. This draft does not assert that those code paths are used by the current production service. The Operator must confirm whether any are reachable in production; if they are, identify the records, purposes, retention and deletion controls in the production inventory and privacy notice.

4. Third-party security verification

Authentication-related screens load Cloudflare Turnstile from challenges.cloudflare.com for bot/security verification. Cloudflare says the standard Turnstile widget returns a verification token; the cf_clearance cookie is an optional addition when pre-clearance is enabled. Its issuance and lifetime depend on the configured Cloudflare zone and challenge passage.

Cloudflare may also set the __cf_bm security cookie when the site is protected by Bot Management or Bot Fight Mode. Cloudflare documents a 30-minute inactivity expiry for this cookie. Whether it is set for nAble Academy depends on the bot-protection products actually enabled for this domain. Other Cloudflare cookies can depend on features such as rate limiting, sequence rules or load-balancer session affinity. The Operator must inspect the live response headers and Cloudflare dashboard and add only the cookies actually used, including their purpose and duration.

References: Turnstile overview, Turnstile pre-clearance, Cloudflare Cookies and Cloudflare clearance.

5. Analytics and advertising

Analytics tracking was not found in the application source reviewed for this draft, and no analytics cookies are intentionally set by the application code reviewed. If an analytics provider is introduced later, nAble Academy must first document the actual provider, purposes, data collected, cookie/storage names, retention periods, recipients and any international transfers. Optional analytics technology must not load before any consent required by the applicable law is obtained.

The current privacy settings screen therefore shows analytics as "Not active" rather than asking users to consent to an unspecified future provider.

6. Your choices

The first privacy notice lets you accept essential storage only or allow optional preference storage for appearance and display choices. Use the Cookie settings link below to change this choice later. This control covers appearance and guide preferences; it is not a master switch for every app-specific storage item used by platform features.

The preference switch controls display choices such as the saved appearance theme and dismissed guides. It does not remove school records, Question Bank cached questions or pending sync data. Those feature-specific records are handled by the related application workflow, account controls and applicable retention rules.

Accepting essential storage only does not mean that all device storage or cookies are blocked. The production deployment must be checked for every cookie and browser storage item set by application code, hosting, security verification and enabled third-party services. Any item requiring consent under applicable law must be controlled before it is set or accessed.

You can also clear cookies and site data through browser settings. Doing so may sign you out or reset locally stored feature state and may remove pending local data that has not yet synchronised to the service.

7. Applicable consent rules

Where European Economic Area or Slovenian rules apply, the ePrivacy rules generally require prior informed consent for storing information or accessing information on a user's device unless a relevant exception applies, such as transmission of a communication or storage/access strictly necessary to provide a service expressly requested by the user. The Court of Justice's Planet49 judgment confirms that consent must involve an active choice; a preselected checkbox is not valid consent, and users must be told the cookie duration and whether third parties can access it.

References: ePrivacy Directive, Article 5(3) and CJEU Case C-673/17 (Planet49).

The Operator must obtain local legal advice to confirm how these rules and other applicable laws apply to the live service and its school users.

8. Before analytics is added

The Operator must update this policy and the consent interface with the actual analytics vendor, exact purposes, data categories, cookie/local-storage names, lifetime, recipients and transfer details. A choice made before those details exist is not treated by this implementation as permission to load future analytics.

9. Contact

Questions about cookies or browser storage: [INSERT VERIFIED PRIVACY CONTACT EMAIL]. The Operator's full legal identity and address must be completed in thePrivacy Policy.