Version 2026-11-02 · 2 November 2026
Cookies and Similar Technologies
Browser storage, essential functions and the conditions for optional analytics.
You can save or print this page using your browser. Contract terms apply from acceptance or a properly notified effective date; publication does not retrospectively change an existing agreement.
1. Essential and preference storage
The application uses browser storage needed for authentication, session continuity, security and request validation. Preference storage may remember a selected theme or display choice. The exact identifiers and lifetimes depend on the configured service and browser; an authentication token must never be sent to support.
Essential functions may stop working if their storage is blocked. Theme and other optional preferences can be cleared through your browser. Clearing storage does not delete server-side account or transaction records.
2. Analytics, replay and advertising
Optional analytics, session replay or advertising must have a disclosed purpose, provider, data scope and retention period before activation, together with the consent or other lawful basis required for that processing. Where consent is required, the technology must be blocked until a valid choice and withdrawal must be respected. Accepting the Terms or acknowledging the Privacy Policy is not consent to optional tracking.
We do not claim that a cookie-preference centre exists merely because this notice does. If no appropriate choice mechanism is available, optional consent-based tracking must remain disabled. Contact hardus.vandyk@fleximetadoc.com about unexpected tracking or to request the inventory for the page or deployment you use.
3. Third-party content and controls
Payment, security, embedded content or other external services may receive technical information when used. Their purposes and terms must be identified for the relevant feature. Do not assume that labelling a provider “security” or “essential” exempts all of its processing from POPIA.
Your browser can show and remove site storage or block selected technologies. Those controls supplement, rather than replace, our duties to provide lawful processing and an effective consent choice where required. See the Privacy Policy for rights and complaints.
4. Browser storage inventory
| Storage | Purpose | Duration and control |
|---|---|---|
| __Host-FMD.Auth; FMD.Auth on configurations that use the development name | Essential account authentication | Default idle limit 30 minutes and absolute limit 8 hours; server configuration and the selected sign-in flow can change the limits. Remembered sign-in and full-authentication checks have additional controls. Sign out to end access; a browser cookie alone does not guarantee an active server session. |
| .AspNetCore.Antiforgery.* | Essential request-forgery protection | Framework-generated identifier; session cookie unless the service configuration specifies otherwise. |
| .AspNetCore.Session and identity/external-login challenge cookies, when used | Essential session continuity, sign-in and security challenges | Session or short-lived challenge storage; server-side session expiry is separately enforced. |
| dark-mode; theme; theme-panel; page-settings storage | User-selected display and page preferences | Browser cookies or local/session storage. Persistence varies by setting and browser; clear site data to remove the preferences. |
| fmd-newsroom-analytics-consent (local storage) | Remember your optional first-party analytics choice | Until you change the choice or clear site data. It contains granted/denied, not an advertising identifier. |
| newsroom_visitor_id; newsroom_session (local storage) | Optional first-party readership and interaction measurement | Created only after analytics opt-in. Visitor identifier persists until withdrawal or clearing site data; a new session is created after 30 minutes of inactivity. Withdrawal removes both stored identifiers and stops new events from open newsroom pages. |
Optional newsroom events include the article/page path, referring hostname, randomly generated visitor/session identifiers, reading time, scroll progress and selected link/button interactions. Withdrawing does not by itself delete previously received server records; request access or deletion through the Information Officer. External sign-in, payment and anti-abuse providers may use their own technologies when their features are opened; see the provider schedule.