Web storage and connected services
Cookies & Browser Storage Policy
This policy explains the cookies, browser storage, service workers and similar technologies used or potentially set when you visit Nursezy on the web. The audited Flutter web application relies mainly on protected browser storage and authenticated API tokens rather than a traditional login-session cookie. Third-party services can use their own cookies or identifiers when their features are enabled.
Last reviewed: October 31, 2026
What this policy covers
“Cookies” is used here as a convenient term for small browser records and related technologies, including local storage, session storage, IndexedDB or browser databases used by Flutter packages, service-worker caches, notification registrations and third-party identifiers. The exact storage mechanism can vary by browser, operating system and package version. This policy should be read with the Privacy Policy.
Essential account storage
Nursezy uses Flutter secure-storage components for access and refresh tokens, onboarding state, notification navigation state, application-review state and chat encryption keys. On web, secure storage can use browser storage together with Web Crypto or related browser security features. These records support sign-in, protected requests, encrypted chat and continuity. Clearing them can sign you out, remove local encryption keys or require setup again.
Session storage used by the Flutter bootstrap
The Nursezy Flutter bootstrap uses one sessionStorage value while it unregisters an older Flutter service worker. The value prevents an endless reload loop, is scoped to the browser tab session and is removed after the migration attempt. It is a technical compatibility record, not an advertising profile.
Service workers and caches
Flutter and Firebase Messaging can register service workers. Browsers may cache application code, images, fonts, manifests and notification resources so the application can load reliably and receive supported push events. A service worker can continue to exist until the browser or application unregisters it. Nursezy’s bootstrap retires the legacy Flutter worker, while the Firebase messaging worker is used only where web push is configured and permitted.
Preferences and permissions
Nursezy stores account-side notification and quiet-hour preferences in the backend and uses local state needed to apply the interface. The browser or operating system separately stores permissions for notifications, files, media or other capabilities. Denying a permission can disable the related feature without preventing access to ordinary public pages.
Firebase Cloud Messaging
If you enable web notifications, Firebase can use a service worker, push subscription and device token to deliver messages. Google may set or use browser records and technical identifiers needed for messaging security and delivery. Nursezy stores the resulting device token and related platform information until it is revoked or no longer needed. You can remove notification permission in browser settings and revoke registered devices where the app provides that control.
Google advertising technologies
When Google web advertising is configured, Nursezy loads Google’s advertising script. Google and its partners may use cookies, local storage, browser or advertising identifiers, consent signals, IP address and interaction information to select, measure, limit and protect advertisements. Mobile AdMob uses platform advertising identifiers and the Google consent SDK rather than ordinary website cookies. Advertising availability and personalisation depend on region, platform, consent and configuration.
Paystack and external checkout
Starting an enabled Paystack payment can open or redirect to a provider-controlled checkout. Paystack may use its own cookies, browser storage, security signals and payment-session identifiers on its domain. Those technologies are controlled by Paystack under its own policy. Nursezy receives the transaction reference and verification result needed to record the purchase; do not place payment-card information in Nursezy support forms.
External links and embedded resources
A published book, video, download or support link can lead to another domain. That service may set cookies or storage independently when you open it. A link does not give Nursezy control over the external service’s technologies. Review the destination and its policy before providing information.
Analytics status
The audited Flutter project passes a Firebase measurement identifier in public runtime configuration, but it does not include the Firebase Analytics package or another dedicated public-site analytics SDK. This policy therefore does not claim that Google Analytics is currently active. Nursezy still keeps ordinary server, security, payment and feature records described in the Privacy Policy. If a dedicated analytics service is enabled later, the policy and consent treatment should be updated before relying on it.
Your controls
Use browser controls to view or clear site data, block cookies, remove permissions, unregister service workers or use private browsing. You can also disable notification categories in Nursezy and review advertising privacy choices where the supported platform exposes them. Blocking all storage can prevent sign-in, encrypted chat, push notifications and other requested functionality from working correctly. Provider-specific opt-out and consent tools may offer additional controls.
Changes and contact
Storage technologies can change as Flutter, browsers and connected services evolve. Nursezy will update this policy when a material new category or provider is introduced. Questions can be submitted through the Contact page, an authenticated Support Ticket or support@nursezy.com.
