Privacy Policy

Who is responsible for your data?

NURSE at the-nurse-app.com is operated by Digital Fairy Studio SRL, the controller responsible for the personal data described here.

For privacy questions, rights requests or account support, use the NURSE support portal or write to the postal address above. The portal works without signing in. It provides a private tracking code to check your reply; signed-in users can also view their own requests. Contact email is optional and we do not send automatic email confirmations. Include only the information needed to handle your request. Never send passwords, recovery codes, private account setup links or patient records.

What this policy covers

This policy covers the public NURSE website and the educational simulation platform. It also covers information you provide when contacting us about the service.

Scenarios use fictional patients and educational clinical information. When you use AI patient conversation, your message, a limited recent conversation history and the fictional scenario context are sent to Cloudflare Workers AI to generate the patient's reply. This context includes the clinical time, patient state and observations already available in your scenario. Your account profile, credentials and session notes are not included in the model request. Free-text messages may still contain information you choose to enter. The conversation screen identifies AI replies and links to this policy before you send a message. NURSE does not use this feature to make automated decisions about clinical competence, grades or eligibility.

Please use fictional information in messages and notes. Do not enter real patient details, health records, confidential workplace information or another person's personal data. If you believe such information has been entered, contact us so that we can assess and remove it as appropriate.

The information we process

Account and professional profile

We store your username, the name entered in your account profile, a password hash, account identifiers and account creation/update dates. Registration asks for your full name, including your given names and family name. Passwords are hashed for verification; they are not displayed to administrators.

For new public registrations, we also record the time you agree to the Terms & Conditions and the versions of the terms and Privacy Policy presented to you. This records the account agreement and privacy notice acknowledgment; it is not blanket consent to additional data processing.

Your profile includes your selected professional or educational role and the related study year, teaching experience or clinical experience, where applicable. Country and your primary reason for using NURSE are optional.

Registration with a NURSE username creates an internal technical email address ending in @accounts.nurse.invalid. It is not an inbox and is not used to send email or recover your account. Google or Apple sign-in, where available, uses the verified email supplied by that provider.

Optional Google or Apple sign-in

Where enabled, you can choose Google or Apple to sign in. We receive a verified email address, which may be an Apple private relay address, a provider account identifier and your name when supplied. We do not receive your Google or Apple password. We request identity information only, without access to your Gmail, Drive or other account content. Provider access, refresh and identity tokens are verified during sign-in and are not retained in the NURSE account record. The provider identity binding is kept with your account.

Google or Apple handles authentication under its own privacy policy. NURSE sends the provider the login request and callback information; it does not send your patient conversations, learning records or notes to these providers. Existing NURSE accounts are connected only through an explicit action in your signed-in profile. Matching an email address does not automatically merge accounts.

Google Privacy Policy · Apple Privacy Policy

Guest practice

You can use Practice and Assessment without an account. Guest sessions include patient messages, actions, notes, clinical time and language preferences. They are saved separately on Cloudflare under an opaque browser identifier. The guest cookie contains only a random identifier, not your conversation. Clearing that cookie loses access to the guest history. Signing in or creating an account opens separate account history; guest conversations are not automatically copied into that account.

For guest AI abuse prevention, a one-way identifier derived from the request IP address is used to enforce conversation rate limits. It is separate from your profile and guest history. Guest and account AI requests share the existing service allowance.

Learning activity

We store activity linked to your account so that you can return to a scenario: messages, selected actions, session notes, requested or viewed fictional reports, scenario time, session status and dates, saved history, language and guidance preferences. A deterministic educational checklist records which case criteria were explored; it does not certify clinical competence or produce an academic grade.

Language selection

NURSE uses the approximate country supplied by Cloudflare for the current request to select Romanian for Romania, German for Germany, Austria and Liechtenstein, and English for other countries. If country information is unavailable, it uses a supported browser language or English. This feature does not store your IP address or add it to your account profile. You can always select Romanian, English or German yourself.

When you explicitly change language, a functional preference cookie stores only ro, en or de for up to one year in this browser. Your manual choice overrides country detection, applies to the website and platform, and does not change existing patient conversation messages. The cookie is not used for advertising or analytics. Clearing it restores automatic selection.

Authentication and security

Sign-in sessions may include your IP address, browser/device user-agent, creation and expiry dates and a session identifier. Rate-limit records help prevent repeated or abusive account requests. Hosting and security services also process request information such as IP addresses, requested URLs and technical errors.

Administration and support

We store your assigned access level and account status. Administrative changes are recorded with the acting administrator, target account, action, reason, time and relevant before/after account details. Private setup/recovery links have an expiry and a stored token hash. If you contact us, we process any username/contact details you supply, request text, ticket status, administrator reply and dates. A hash of your private tracking code limits access to the reply. Recovery codes are shown once, stored only as hashes and linked to your current credential for invalidation. When you voluntarily join a study group, we store your group membership, sharing choice/version and joining date, alongside teacher-created assignments. Clinical review records include the expert name, qualification, notes, content version/hash, recording administrator and date.

Technical traffic and guest references

Technical traffic records include the connection IP address, request time, a generalized route, response status, response duration and a coarse browser/device category. Approximate country and city are included only when supplied by the hosting edge. These records are available only to the master administrator and are kept for up to 30 days, with a maximum of 200,000 recent requests.

For requests using the existing guest history cookie, the traffic log stores a separately derived cryptographic reference to distinguish guest browser histories. It does not retain the raw cookie or create another cookie. Authenticated account requests do not retain this guest reference. Requests without a guest history cookie remain anonymous connection records; historical records without this classification remain unknown. IP addresses and guest references do not establish a person’s identity. Request bodies, passwords, raw authentication cookies and URL query parameters are not stored in this traffic log.

Why we use this information

Provide your account and saved practice — Article 6(1)(b) GDPR

We use account, profile and learning data to provide the service you request, keep your saved activity and support your account.

Optional study-group reporting — Article 6(1)(a) GDPR

Joining a teacher’s group is optional and requires an affirmative sharing choice. While you remain enrolled, the group’s authorised teacher can see your name/username and completed assigned case activity created after joining: case, mode, completion date, clinical time and educational checklist counts. You can withdraw future report access by leaving the group. Withdrawal does not make earlier lawful processing unlawful; any copies already obtained by a teacher must be addressed through the operator.

Protect and administer NURSE — Article 6(1)(f) GDPR

Our legitimate interests are preventing misuse, controlling access, investigating technical problems and keeping administrative actions accountable. Session, request, rate-limit and audit information supports these purposes. You can object to processing based on legitimate interests.

Handle rights requests and legal duties — Article 6(1)(c) GDPR

We process information needed to meet applicable data protection obligations and respond to lawful requests.

Required registration fields are needed to create and configure an account. Without them we cannot register you. Optional profile fields can be left blank, and you can view the introduction, case library and legal pages, and use guest Practice and Assessment without creating an account.

We do not use the current application for targeted advertising or sell personal data. This policy is an information notice; it is not a request for blanket consent. If an additional feature needs consent, we will explain it and request that choice separately before using it.

Access, hosting and international processing

Authorised administrators can view and manage account details within their assigned permissions. The head administrator can manage account roles and status across NURSE. Selecting an educator profile does not itself give teacher or administrator access. Study-group reporting is limited to the group’s authorised teacher and the head administrator, with your affirmative choice when joining. Teachers do not receive your conversations, session notes, passwords or unrelated/unassigned activity. Membership and reporting are disabled if the teacher loses access. Selecting an educator profile or knowing an assignment link does not grant report access.

Cloudflare provides hosting, request delivery, the account database, technical security services and AI inference for patient conversation through Workers AI. The model is Qwen, an open model published on Hugging Face; inference runs through Cloudflare, and the application does not send your messages directly to Hugging Face. Cloudflare states that it does not use Workers AI customer content to train models or improve its or third-party services without explicit consent. See Cloudflare's Workers AI data information. The account database is configured with EU jurisdiction. Website requests are delivered through Cloudflare's global network, and service or support processing may take place outside the European Economic Area.

Cloudflare's published Data Processing Addendum describes its processing obligations, subprocessors and safeguards for restricted transfers, including the EU Standard Contractual Clauses where applicable. You may contact us for information about the safeguards applicable to NURSE. An EU database location does not mean that every hosting operation takes place only in the EU.

We may disclose information when required by applicable law, a valid authority request, or to establish, exercise or defend legal claims. We limit any disclosure to the information needed for that purpose.

How long information is kept

Guest session records expire from active storage 30 days after the last saved session activity. Opening a new guest session starts a new history if the previous records have expired. Hosting-provider recovery copies may remain for their separate recovery period and are not a guest history feature. An account retains its saved sessions and conversations under the account retention rules above.

Account, profile and saved learning records are retained while your account remains open and they are needed to provide your account and practice history. You can request account closure and deletion through the contact above. There is currently no self-service account deletion button or automatic inactivity deletion schedule.

We assess a deletion request individually. Where limited information must be retained for a specific legal duty, an unresolved security incident or a legal claim, we restrict its use and keep it only while that reason remains applicable. Administrative audit information is retained only as needed to investigate access changes and protect the service; it is reviewed alongside account closure and security issues.

A sign-in session is valid for up to seven days without automatic renewal. Signing out revokes the current session; password changes and administrator actions can revoke sessions earlier. A private account setup or recovery link is valid for up to 24 hours and can be used only once. Saved self-service recovery codes expire after 90 days. Using a code to reset a password invalidates the entire set and all previous sign-in sessions. A password change, administrator access change or a new set of codes also revokes the previous codes. These limits expire access, rather than automatically deleting every associated database record.

Temporary browser storage and the sign-in cookie are described in the Cookie Policy. Group memberships and assignments are retained while needed to provide the requested teaching activity and resolve relevant requests; leaving a group immediately ends future teacher report access. Support requests are retained while needed to handle the request and relevant follow-up. Local database recovery snapshots are encrypted and access-restricted; their continued need is reviewed with account closure and privacy requests. If an older snapshot is restored, applicable deletion or restriction decisions must be reapplied before service resumes. Hosting-provider technical records follow the applicable service retention settings. We review the need to retain records and remove information when its purpose no longer applies.

Your rights and how to make a request

Depending on the circumstances and the applicable law, you can request access to your data, correction, deletion, restriction of processing and portability of data provided under a contract or consent. You can also object to processing based on legitimate interests. If we later rely on consent for a feature, you can withdraw it without affecting earlier lawful processing.

You can update your profile from your account. For other requests, use the contact in Who is responsible for your data? We may ask for proportionate information to confirm that the account belongs to you. We will not ask for your password.

We normally respond within one month. If a request is complex or numerous and an extension is permitted, we will explain the reason within that first month. Requests are generally free of charge, subject to the exceptions provided by law.

You can complain to a data protection authority, including the authority where you live or work or where the issue occurred. In Romania this is the National Supervisory Authority for Personal Data Processing (ANSPDCP). You do not have to contact us before making a complaint.

How we protect your account

The service uses HTTPS, hashed passwords, protected sign-in cookies and account-based access checks. Administrators receive assigned permissions, and administrative changes are audited. These measures reduce risk, but no online service can guarantee absolute security.

Keep your password, recovery codes, support tracking codes and private setup links confidential. If you suspect an account has been compromised, contact us and change your password through your signed-in account where possible. You can save recovery codes from your account and recover at Account recovery. If you have no saved code, an authorised administrator can assist after checking ownership independently. A support ticket alone does not prove ownership.

Changes to this policy

The date at the top identifies this version. We will update the policy when the service or its data use changes. Material changes to data use, new recipients or AI processing will be explained before the new processing begins, with an additional choice where legally required.

See also the Terms & Conditions and Cookie Policy.