NeuroDeck

Cookie Policy

Effective date: 19 October 2026
Last updated: 19 October 2026

1. Scope and relationship to other policies

This Cookie Policy explains the cookies and similar storage technologies used by the NeuroDeck website and app. It covers information stored in, or accessed from, your browser or device when you visit public pages, sign in, study, use Axon or install the web app. “NeuroDeck”, “we”, “us” and “our” refer to the operator providing this service.

Read this policy alongside the Privacy Policy, which explains the use of personal information and your data protection rights, and the Terms of Service, which describe use of the app. Acknowledging a storage notice does not waive those rights or agree to optional tracking.

2. Current position at a glance

NeuroDeck currently uses browser storage for sign-in, the study features you request, saved chat and study data, an offline page and acknowledgement of this notice. We do not install advertising cookies, cross-site marketing pixels or third-party analytics trackers. Your Progress tab is calculated from your study records, not from an advertising profile or third-party tracking tag.

The popup therefore provides information and a “Got it” acknowledgement, rather than presenting accept and reject controls for categories that are not installed. Clicking that button does not start advertising or analytics. You can read the full policy without clicking it, and you can reopen the notice with the control below.

3. Technologies covered

A cookie is a small record a website or service can ask your browser to store and return with later requests. Cookies can be limited to a host, a path or a period of time. A session cookie usually lasts for a browsing session; a persistent cookie has its own expiry. Browser session-restoration settings can affect how long a session effectively lasts.

Local storage and session storage hold values that website scripts can use. Local storage normally survives closing the tab, while session storage normally belongs to a particular tab session. IndexedDB can hold more structured records, including authentication state. Cache Storage can hold files used by a service worker. Similar legal rules can apply to these technologies even though they are not technically cookies.

Browser and operating-system controls, automatic privacy protections, private browsing and device storage pressure can change whether records are retained or accessible. A description of a storage duration is not a guarantee that a browser will preserve that record for the whole period.

4. Why the current storage is used

Authentication storage helps verify your account and avoid requiring a complete new sign-in for every request. Study storage keeps the data and checkpoints needed to return to your revision and recover local work while cloud syncing takes place. Chat storage lets you return to conversations. The acknowledgement record avoids repeatedly displaying the same notice on every visit.

These purposes relate to the service and features you request. A storage technology does not become essential merely because it is useful to the operator. If we introduce a materially different purpose, we must assess it separately and provide the information, choice and consent required for that purpose. This policy does not authorise an undisclosed secondary use.

5. Storage inventory and retention

The table lists the principal storage used by the current application. Values such as account and session IDs vary by user; placeholders identify that variation rather than a literal fixed name. Firebase may use different names or storage mechanisms depending on the browser, sign-in method and SDK behaviour.

Storage / providerPurposeDuration
Firebase Authentication / Google
IndexedDB, local or session storage; sign-in cookies on the authentication service
Authenticate your account, keep you signed in and complete a Google sign-in you choose to start. Firebase storage names can start with firebase:.Temporary redirect information lasts for the sign-in flow. Persistent sign-in state remains until you sign out, clear it or the session is invalidated. Provider cookies have their own expiry times.
NeuroDeck
nd_data_v1:<user>
nd-study:<user>:<session>
Local storage
Keep a local copy of your decks, progress and study checkpoints so you can resume your work and recover unsaved changes.No automatic time-based expiry. Entries are updated as you study and remain until removed or your browser clears site data.
NeuroDeck
nd_chats_v1:<user>
Local storage
Store your Axon conversations so you can return to them.No automatic time-based expiry. Conversations are updated when you edit or delete them, or removed when site data is cleared.
NeuroDeck
nd_cookie_notice_v1
Local storage
Remember that you have read the cookie notice. This is an acknowledgement, not permission for optional tracking.The acknowledgement is valid for 180 days. The notice appears again after that or when its version changes. The stored entry is replaced on acknowledgement or removed when site data is cleared.
NeuroDeck service worker
neurodeck-offline-v1
Cache Storage
Show an offline page if the website cannot be reached. This cache does not store account data or API responses.Until replaced by a newer cache, removed by your browser or cleared with site data.

A record with no automatic expiry is not a promise that it will exist permanently. It may be overwritten by a newer record, removed by a feature, cleared manually or removed by the browser. Retention of cloud records is a separate issue covered by the Privacy Policy.

6. Authentication and provider cookies

Firebase Authentication supports account sessions using browser mechanisms such as IndexedDB, local storage or session storage. Google sign-in can involve Google or Firebase authentication pages and cookies belonging to those services. The exact cookies on a provider’s domain can depend on your existing provider account and its privacy settings, so we do not represent that NeuroDeck sets every cookie shown during that external sign-in flow.

Signing out ends the active app sign-in state, but need not erase every study cache or sign you out of Google itself. Changing a Google session or revoking an app permission also does not automatically remove every NeuroDeck record stored in a browser. Use the relevant account and browser controls for the result you want.

7. Study and chat copies on a device

Cached study data and checkpoints can include the questions, answers, settings, progress and other materials needed to restore your study view. Cached Axon conversations can contain your own messages and generated replies. These records may contain personal information if you put personal information into the app.

Account-scoped names help separate records, but a storage name is not encryption and does not make a shared browser private. Someone who can access your unlocked device, browser profile or developer tools may be able to inspect local records. Sign out on shared devices, avoid saving private material there, and consider clearing site data after confirming important work has synced.

8. The acknowledgement record

The nd_cookie_notice_v1 value records the notice version and the time you acknowledged it. It is not an advertising identifier or a record that you consented to an optional analytics service. The current notice treats the acknowledgement as valid for 180 days. It may appear again after that period, after a relevant version change, or after you clear the record.

If storage is blocked, the app can dismiss the notice for the current page without successfully remembering that action for future visits. A malformed or unreadable record is treated as an unacknowledged notice. Different browsers, browser profiles and devices have separate records. A setting on one device does not automatically control another device.

9. Installed app and offline support

The installed web app uses a service worker with a cache named neurodeck-offline-v1. Its current role is to keep an offline fallback page available if a navigation request cannot reach the website. It does not place your account data or API responses into that particular cache. Other normal browser caching remains subject to browser and server behaviour.

A service worker can remain registered after you close a tab. Removing an app icon from a home screen does not necessarily clear its underlying browser data. Browser site settings or developer tools can remove the registration and associated storage. Clearing this cache can remove the offline page until it is installed again.

10. Optional tracking and future choices

There are currently no optional advertising or analytics categories enabled by this notice. We do not treat scrolling, continuing to browse, ignoring the popup or accepting the Terms of Service as consent to tracking. A link to an external service is not permission for us to introduce new tracking on this website.

If an optional technology requiring consent is introduced, we will explain its purpose and providers, give a genuine choice before it runs, and provide an appropriate means to change that choice. Where a lawful exception applies instead, its conditions must still be satisfied and the required information or objection mechanism provided. Essential sign-in storage cannot be turned into optional advertising consent by renaming it.

11. Inspecting, blocking and deleting storage

Your browser’s privacy or site-data settings can show stored cookies and website data. Depending on the browser, you may be able to remove data for this website alone, block cookies, clear local storage and IndexedDB, or unregister a service worker. Some browsers group these controls together; others place them in different menus. A cookie-only setting may not remove local storage or cached files.

Blocking essential authentication storage can stop sign-in working. Blocking local study storage can prevent local recovery or remembering a session. The service may need access to storage to perform the feature you request; a control that blocks it may make that feature unavailable. Private browsing can also discard records when the session ends.

For instructions appropriate to your device, use your browser’s current help pages: Chrome, Firefox or Safari. These external instructions and menus can change independently of NeuroDeck.

12. What clearing storage does and does not do

Before clearing site data, save an independent copy of important work and check for cloud-sync errors. Unsynced edits, local chat copies and study checkpoints can be lost when device storage is removed. Reopening the app while signed in may download saved cloud information again.

Clearing browser data is not an account-erasure request. Signing out is not a cloud deletion request. Deleting a cloud record does not instantly clear a browser that is offline or an independent copy you exported. To request deletion of personal information held by NeuroDeck, use the process in the Privacy Policy. Manage copies held by an external provider through its relevant controls as well.

13. External services, browser signals and personal data

Google sign-in and Google Calendar may open external pages with their own cookies and privacy controls. Other external links can also take you to websites we do not operate. Read Google’s cookie information and Firebase’s privacy information for their services. Those providers are responsible for the storage they independently use on their own services, while we remain responsible for our own processing.

We do not represent that every browser privacy signal, including a Do Not Track setting, is a universal consent or deletion instruction. The current absence of optional tracking is not dependent on turning on such a signal. Browser-level blocking can nevertheless affect how essential features work.

When stored information identifies you or relates to you, data protection law can also apply. Our purposes, providers, international processing, retention criteria, rights and complaint routes are described in the Privacy Policy. This storage notice does not replace that information.

14. Updates and contact

This policy is effective from 19 October 2026. We may revise it to reflect changes to storage, authentication, browser behaviour, integrations or applicable requirements. A new policy does not retrospectively create consent or legalise a past use. Where required, we will give an additional notice or ask for a new choice before a new optional purpose starts.

For questions about a storage record, problems using the notice, or a request relating to personal information, contact neurodeck.mlm@gmail.com. Tell us which browser and feature you were using, but do not send passwords, authentication cookies, tokens or other secrets. The ICO’s guidance on storage and access technologies provides further background.