eMafundi

Cookies, Local Storage and PWA

R12-2026-11-01

Cookies, Local Storage and PWA

Essential sessions

eMafundi uses a session cookie to keep you signed in and to protect forms against forged requests. The application uses secure-cookie settings over HTTPS and a server-side session; deleting the cookie or signing out ends access on that browser. Security cookies and CSRF tokens are not advertising profiles. You can block cookies in the browser, but account and form features may then fail.

Preferences on your device

The interface can remember light/dark mode, menu expansion and selected interface preferences in local or session storage. Language is associated with your session/account and canonical records keep the same identity when you switch language. A logout marker notifies other open tabs to discard private session context. No password, MFA secret or payment PIN should be stored in these preference keys.

PWA cache and updates

The service worker stores selected public code, styles, icons and an offline fallback. Sensitive account, job, quotation, finance and document responses are not included in the public asset cache. An update notification asks you to save unsent work before applying an update. Being offline does not mean a quotation was sent, a booking was confirmed or a payment succeeded. Browser cache and uninstall controls are available in your device settings.

Push, maps and third-party resources

Push notifications require a separate browser/device permission and an active subscription. The map may request tiles and code from the configured map/CDN providers; they can receive the network information needed to deliver those resources. Precise location is optional and requires browser permission; searching by district does not require device GPS. This release does not bundle third-party advertising trackers or analytics cookies. If the operator later enables nonessential tracking it must disclose the provider and purpose and obtain any required permission before loading it.

Your controls

Use Notification Preferences for service channels, browser settings for push/site permissions and the visible Sign out control when leaving a shared device. Clearing local storage does not erase a provider’s job history. Use Contact or Privacy Requests for server-held information and privacy concerns.