Nursezy

Privacy and data use

Privacy Policy

This Privacy Policy explains how the Nursezy service processes information when you use its public website, create an account, practise questions, read books, watch videos, use Tutor AI, participate in conversations, manage coins or payments, receive notifications, view advertising or contact support. It reflects the audited Nursezy application and database as of 31 October 2026. Feature availability depends on platform and configuration.

Last reviewed: October 31, 2026

Scope and responsible use

This policy applies to the Nursezy public website, authenticated web application, supported mobile applications and the Nursezy API. “Nursezy,” “we” and “the service” refer to the Nursezy service that provides these products. No company-registration or governing-law identity is stated here because the audited configuration does not establish one. Privacy questions can be sent through the public Contact page, an authenticated Support Ticket or the configured address support@nursezy.com.\n\nNursezy is an education platform, not a clinical records system. Do not enter patient names, identifiers, photographs, case notes or other confidential clinical information in a profile, note, review, chat, support request or AI prompt. If your school or employer imposes additional confidentiality duties, you remain responsible for following them.

Public website and contact requests

You can read public pages without creating an account. The web server necessarily receives technical request information such as IP address, requested URL, date and time, browser headers and response status. This information may appear in operational or security logs used to deliver pages, investigate errors and protect the service.\n\nThe public Contact form collects the name, email address, subject, message, request key and technical anti-duplication information needed to create and protect a support request. The resulting support ticket receives a reference. The information is used to acknowledge, route, investigate and answer the request. Do not submit credentials, full payment-card data or sensitive patient information.

Account and authentication information

Registration and account operation use identifiers such as email address, username, password hash, account UUID, status, email-verification state, role assignments, creation and update times and account-deletion state. Passwords are stored as hashes rather than readable passwords. Email-verification, password-reset, two-factor and security records can include time-limited codes or tokens, expiry information, attempt state and related timestamps.\n\nAuthenticated sessions use access and refresh tokens. Supported clients store session material using protected application storage. The backend stores refresh-token records and can revoke sessions. Nursezy may process IP, device, session and authentication-event information to confirm access, detect misuse, troubleshoot sign-in and enforce restrictions. Never share a password, token or verification code.

Profile information and uploads

A profile can contain first and last name, phone number, biography, country and avatar URL. You decide which optional profile fields to provide, but some information may be visible in community or administrative views. Profile-photo uploads are stored in Nursezy-managed storage and associated with the account.\n\nGroup avatars, conversation attachments, voice notes, support attachments and content files can include original filename, stored path, media type, size, duration, encryption state and timestamps. Files may contain personal information chosen by the uploader. Only upload material you are authorised to use, and remove metadata or confidential information that is not needed for the purpose.

Exam, practice and progress records

When you start or use an exam session, Nursezy can store the exam, user, selected setup, question pool, session status, start and submission times, answers, saved or marked questions, score and configuration such as mode, duration, difficulty and rationale choice. Submitted results can include total, correct and wrong answers, score, status, breakdown, recommendations and timestamps.\n\nProgress views may combine exam history, achievements, bookmarks and saved questions. These records are used to deliver the session, resume active work, calculate results, show learning history, apply configured coin rules, prevent duplicate actions, support investigations and improve operation. They describe activity inside Nursezy and are not official educational or professional records.

Books, notes, reviews and reading activity

Library use can create access and purchase records, reading start and finish information, last page, progress percentage and completion state. Notes can include the book, page number, note text and timestamps. Reviews can include rating, title, review text and moderation status. Reader quizzes can store source context, generated questions, answers, feedback, AI provider information and coin amounts.\n\nNursezy uses this information to check access, avoid duplicate coin charges, resume reading, show your books and transactions, operate notes and reviews, and deliver supported reader features. Review content may be made visible according to its publication status. Private notes are associated with the user account and should still not contain patient-identifying or other highly sensitive information.

Video activity and rewards

For signed-in video use, Nursezy can store video identifier, watch percentage, watch seconds, watch count, first and last watch time, reward state, reward amount and timestamps. If a video has a coin access cost, the wallet ledger records the unlock. If reward rules are enabled, the service uses watch time, daily limits, cooldowns and prior claims to determine eligibility.\n\nThis data supports playback continuity, access control, rewards, fraud prevention and support. Opening or playing content does not guarantee a reward; eligibility depends on the active policy and successful server-side recording.

Coins, purchases and payment information

Nursezy maintains a coin wallet and transaction ledger containing balance, credit or debit amount, source, action key, reference, balance after the action, description, status, metadata and timestamps. Coin records can be created by purchases, learning activity, advertising rewards, authorised adjustments and configured feature costs.\n\nWhere Paystack checkout is enabled, Nursezy sends the amount, currency, reference, customer email and callback information needed to initialise and verify a transaction. Nursezy stores payment identifiers, provider, platform, package, amount, currency, coin amount, status, authorisation URL or access code, provider transaction reference, verification information and paid or verified timestamps. Payment-card entry is handled by the payment provider rather than the Nursezy application database. Do not send card details to support. Google Play and Apple purchase verification code exists in the project but is disabled in the audited settings, so those providers are not described as active payment processors here.

Conversations, groups and encryption

Nursezy conversations process participant and group records, membership or join requests, sender, message type, reply and forwarding links, delivery and read state, reactions, typing state, timestamps and deletion markers. Messages can contain plain body text or an encrypted payload, key identifiers, recipient-key map and nonce. Supported clients use X25519 key exchange and AES-GCM encryption for message and file payloads, with private keys stored in protected client storage.\n\nEncryption does not hide all operational information and does not prevent recipients from copying content. The service still processes participant, routing, key, delivery, attachment and moderation data. Some system or legacy content may not use the same encrypted path. Conversation deletion or “delete for me” can hide or mark data rather than erase every copy, particularly where another participant, a report, security need or backup is involved.

Community reports and moderation

A conversation or message report can include conversation and message identifiers, reporting and reported users, source, reason, details, request key, status, administrative note, decision information and timestamps. Account bans, message restrictions, group approval or suspension and administrative audit records may also be processed.\n\nThis information is used to review alleged abuse, enforce community rules, protect users, prevent repeated misuse and document moderation decisions. Report information is limited to authorised functions, but the reported person may infer that a review occurred. Do not submit knowingly false or retaliatory reports.

Support tickets and account-deletion requests

Support Tickets can contain user or external contact details, ticket number, subject, category, priority, status, message history, attachments, read and acknowledgement state, assigned administrator, AI-assistant state and timestamps. A profile account-deletion request creates a dedicated support ticket and can include the reason supplied by the user.\n\nNursezy uses this information to answer requests, investigate account or payment records, maintain continuity, notify participants and document action. The support assistant may use Together AI only when enabled for that ticket; an authorised administrator can take over. Do not include passwords, one-time codes, full card details, patient information or unrelated confidential material.

Tutor AI and Together AI

The audited AI provider is Together AI. Depending on the feature, Nursezy may send a prompt containing selected questions, answers, result context, book excerpts, learner-provided text or a support conversation needed to generate feedback, reader activities, a study resource or support-assistant response. The backend records provider, model, prompt hash, generated response, status, associated account or session, coin amount and timestamps.\n\nAI processing is optional to the extent that you choose whether to request a learner-facing generation, although a support ticket may use the assistant when that function is enabled. Do not submit highly sensitive or patient-identifying information. AI output is not guaranteed accurate, and you should independently verify clinical or educational information. Together AI processes submitted data under its own terms and privacy practices.

Notifications, Firebase and email

Nursezy uses Firebase Cloud Messaging for supported push notifications. Device-token records can include the token, platform, device name, app version, last-seen time, revocation time and timestamps. Notification records can include type, title, body, data payload and read time. Preferences can control push, in-app and email delivery, message previews, sound, topic categories, quiet hours, timezone and marketing email.\n\nFirebase receives the identifiers and technical information required to deliver push messages. The configured SMTP email service is used for verification, password recovery, support acknowledgements, service messages and newsletters. Marketing emails include a preference or unsubscribe mechanism; transactional account and support messages can continue when required to provide the requested service.

Advertising and consent

The project uses Google Mobile Ads for supported native advertising and can load Google web advertising when a web advertising client is configured. Rewarded advertisements can create task, verification and coin-credit records. Interstitial advertising exists but was disabled in the audited local settings; advertising configuration can change without changing this policy.\n\nGoogle and its partners may process advertising identifiers, device or browser information, IP address, consent state, ad interactions and anti-fraud signals under their own policies. On supported mobile platforms, Nursezy requests advertising consent and provides privacy choices when required by the Google consent SDK. Browser controls and provider consent interfaces may also apply. Refusing personalised advertising may affect ad personalisation or availability, not the core ability to read public pages.

Browser and application storage

Nursezy clients use protected application storage for session tokens, onboarding state, notification state, review prompts and chat encryption keys. On web, the underlying Flutter storage implementation can use browser storage and Web Crypto. The Flutter bootstrap also uses sessionStorage briefly to prevent repeated reloads while retiring an older service worker. Service workers and browser caches can store application code and notification resources.\n\nThis storage is used for security, continuity and requested functionality. Clearing browser data, removing the app or using private browsing can remove local state and may require sign-in, key registration or permission setup again. The Cookie Policy provides additional detail and browser controls.

How Nursezy uses information

Nursezy uses information to create and secure accounts; deliver public and authenticated pages; provide exams, books, videos, AI, conversations, wallets, payments, notifications and support; record requested progress; calculate results and rewards; verify access and payment; respond to privacy requests; prevent duplicate charging and fraud; investigate errors or abuse; moderate community activity; maintain audit trails; communicate service information; and improve reliability.\n\nWhere consent is the appropriate basis for a function, such as optional notifications or certain advertising choices, the service requests it through the relevant platform. Other processing is necessary to provide a requested service, protect the system, meet legitimate operational needs or comply with applicable obligations. This policy does not assign a specific legal jurisdiction that has not been established in the project.

When information is shared

Nursezy does not contain an audited workflow for selling lists of personal information. Information is disclosed when necessary to providers that support implemented functions: infrastructure and hosting; Paystack for enabled checkout; Together AI for enabled AI requests; Google Firebase for push messaging; Google advertising services for enabled ads and rewards; and the configured SMTP or email infrastructure for messages. External book or video links may take you to another service with its own practices.\n\nInformation may also be disclosed to authorised administrators, support and moderation personnel; to protect users and the service; to investigate fraud or security incidents; to establish or defend claims; or when disclosure is legally required. Providers process information under their own terms and may operate in different countries.

Retention and account deletion

Nursezy does not publish one fixed retention period for every record because different records support different functions. Account, learning, content, wallet, payment, support, moderation, notification, security and audit information is kept while needed to provide the service, maintain integrity, investigate disputes or abuse, satisfy applicable obligations and support authorised deletion or recovery workflows. Time-limited verification records and technical jobs have their own expiry or completion states.\n\nAn account-deletion request creates a support workflow. The current implementation normally soft-deletes an account and revokes access first. Permanent deletion is restricted to authorised system administration and can fail safely while linked records remain. Some payment, security, moderation, transaction, backup or legal records may therefore be retained or de-identified where immediate deletion is not appropriate. Nursezy will explain material limitations when responding to a verified request.

Security

Security measures in the audited implementation include password hashing, authenticated API tokens, refresh-token revocation, optional two-factor authentication, email verification, permission checks, protected client storage, server-side access checks, encrypted chat support, payment verification, audit records, upload validation and account or moderation controls. HTTPS is enforced for non-local production access by the backend configuration.\n\nNo system is completely secure. Protect your device and email account, use a unique password, enable available security features, review sessions, avoid unofficial payment links and report suspected compromise promptly. Email and ordinary support messages should not be treated as end-to-end encrypted.

Your choices and requests

You can choose whether to create an account, which optional profile information to provide, whether to request Tutor AI work, whether to join community features, whether to enable supported notifications, and whether to use optional paid or rewarded functions. Account settings provide controls for profile, password, two-factor authentication, sessions, notifications and advertising privacy where available. Browser and operating-system controls can manage storage, notifications, permissions and advertising choices.\n\nTo request access, correction or deletion, use an authenticated Support Ticket, the account-deletion action, the public Contact page or support@nursezy.com. Nursezy may verify identity and scope before acting. This policy can change when the product or legal requirements change; the public page will show the review date.