Cookies & tracking technologies
This Cookie Policy explains how Makronexus (“Makronexus”, “we”, “us”) uses cookies, local storage, and similar technologies on our public website and the Makronexus Education platform. It is part of our Privacy Policy.
Last updated 13 November 2026 · Version 3.1 · Applies to the website and platform
Contents (12 sections)
1. What Are Cookies?
Cookies are small files written by a website to a browser. Local storage and session storage are related technologies that can retain application settings and authentication state. They operate differently from HTTP cookies, so this notice identifies each where known.
Some identifiers are necessary to sign in, recognise a device or protect an account. Others may remember preferences, measure performance or be provided by a separately configured analytics or communication service. Your school may configure its own tenant features.
A browser can store identifiers under the website origin. Storage that is accessible to JavaScript can also be read by scripts running in that origin; this matters for the security of authentication tokens.
2. Why We Use Cookies
Makronexus Education uses browser storage for user sessions, synchronising authentication between authorised school domains, remembering device context and retaining selected preferences. Depending on the enabled modules, limited offline data or form state may also be cached locally.
Operational logs and error signals may be needed for reliability and incident investigation. Optional analytics, recording, marketing pixels or third-party identifiers are separate activities and must be assessed and identified before activation; the presence of a provider name in a policy does not prove that its cookies are deployed.
Do not use shared or untrusted devices for sensitive school records without appropriate sign-out and browser cleanup. School administrators should manage device access and account revocation.
3. Categories of Cookies
Essential authentication and security storage enables account access, session renewal, cross-host navigation and device recognition. Disabling it may prevent the service from operating.
Preference storage remembers selected display or navigation settings. Offline and application storage may retain limited working information on a device where a supported feature is active.
Analytics or marketing trackers, if separately deployed, require their own documented purpose, provider, retention and lawful basis. Where consent is required, the applicable choice must be provided before the tracker is activated. We do not treat a generic browser instruction as a substitute for a required consent mechanism.
4. Cookies We Use
The following entries reflect storage names identifiable in the Makronexus Education frontend source. Actual activation, scope and expiry can depend on the deployed version, domain and school configuration. A deployment-specific browser inspection is required before treating this as a complete inventory.
| Name / key | Type | Purpose | Indicative retention |
|---|---|---|---|
| accessToken | Local storage and JavaScript-written cookie | Authentication and school-domain session continuity | Cookie typically up to 24 hours or token lifetime; storage until cleared |
| refreshToken | Local storage and JavaScript-written cookie | Obtains a renewed authenticated session | Cookie configured up to 30 days; storage until cleared |
| tokenExpiresAt | Local storage | Records expected access-token expiry | Until changed or cleared |
| makronexus.device.id | Local storage | Stable device context for authentication and security features | Persistent until removed |
| makronexus.tenant.id / makronexus.tenant.slug | Local storage | Remembers selected school tenant | Until changed or removed |
| User interface preference keys | Local or session storage, where enabled | Remembers navigation and display settings | Until cleared or replaced |
These client-managed authentication cookies are accessible to browser scripts and are not HttpOnly. Users must never share access or refresh tokens with support staff or paste them into messages.
Cookie lifetimes and local-storage retention are not identical. Browser or application clearing may end a session even before the normal expiry period.
5. Third-Party Cookies
Third-party hosting, security, payments, messaging or analytics services may process information in the course of the product's operation. Their actual cookie and storage activity depends on the service, integration and deployment and is not necessarily identical across school domains.
We do not list Google Analytics, Cloudflare or any advertising provider as an active cookie issuer solely because a provider was mentioned in a previous policy version. The current live supplier, storage key, domain, purpose, retention and transfer country must be verified before it is entered in a published active-provider inventory.
For deployment-specific disclosures, schools may request the approved service and subprocessor schedule at support@makronexus.com. An external website opened through a link may set its own cookies under its own privacy rules.
6. Local Storage & Similar Technologies
The platform frontend uses browser-accessible local storage for access and refresh tokens and other session information, as well as a persistent device identifier. It may also retain tenant selection, user-interface preferences or offline working data where enabled.
Information in local storage is normally available to scripts running on the same origin and persists until removed by the application or browser. For that reason, users should avoid unknown extensions, shared computers and unmanaged devices, and always sign out when they finish.
Session security also depends on access controls, safe browser behaviour, token revocation and protection against malicious scripts. These technical safeguards must be evaluated separately from the disclosures in this notice.
7. Managing Your Cookie Preferences
Use your browser's site settings to view or clear cookies and local storage. Signing out of Makronexus Education and clearing site data are recommended when leaving a shared device. Clearing stored tokens and preferences can require you to sign in again.
Essential authentication storage may be necessary for the application to function. Optional third-party analytics or marketing storage should have a separate choice where required by law. If you believe a nonessential tracker is active without an appropriate choice, report it to support@makronexus.com.
Your school may also provide device and browser-management rules. Contact the school for questions about locally cached learner records or a managed computer.
8. Browser-Specific Instructions
Below are links to cookie management instructions for popular browsers:
| Browser | How to Manage Cookies |
|---|---|
| Google Chrome | Settings → Privacy and security → Cookies and other site data |
| Mozilla Firefox | Settings → Privacy & Security → Cookies and Site Data |
| Safari (macOS) | Preferences → Privacy → Manage Website Data |
| Safari (iOS) | Settings → Safari → Clear History and Website Data |
| Microsoft Edge | Settings → Cookies and site permissions → Manage and delete cookies |
| Opera | Settings → Privacy & security → Cookies |
| Brave | Settings → Privacy and security → Cookies and other site data |
For other browsers, consult the browser's help documentation or settings menu.
9. Do Not Track Signals
Some browsers transmit Do Not Track or other privacy preference signals. Their operation and legal effect depend on the technology and jurisdiction.
We cannot represent a universal response to every browser signal across all configured third-party services without live verification. Where a required consent or objection applies to an optional tracking activity, the responsible site operator must provide and honour an appropriate choice.
10. Impact of Disabling Cookies
Blocking authentication cookies or removing stored tokens may prevent sign-in, token renewal and navigation between authorised school domains. Removing preferences may restore default settings. Clearing local offline data may remove device-local drafts that have not yet been successfully synchronised.
When using a shared computer, log out, check that any unsynchronised work is saved, and then use the browser's site-data controls if appropriate.
11. Changes to This Policy
We update this notice when material storage practices, relevant providers or legal requirements change. The updated page will show its version and date.
Adding an optional tracker or expanding its purposes may require a new lawful basis, consent mechanism, notice or regulator process before activation. Posting an update does not itself give the required permission.
12. Contact
If you have questions about our use of cookies or this Policy, contact us:
For broader privacy questions, see our full Privacy Policy.