Draft for review — not approved for operational reliance. This notice must be checked by the service owner and a UK data protection officer or solicitor before it is treated as final. Supplier contracts, legal roles, contact routes, transfer details and retention periods are not all verifiable from application code.
AnuAssure privacy notice
This draft covers the AnuAssure public website and mobile app, including data entered by care organisations, staff and service users. It expands the attached policy pack’s website-only draft; it is not a substitute for an organisation’s own privacy information.
Last reviewed: Draft prepared 5 November 2026. Notice version: Draft 1.
Who is responsible
The care organisation using AnuAssure generally decides why and how its care and workforce information is used. AnuAssure provides the software and processes information to operate the service. AnuAssure may also handle account, service-security and website information for its own purposes. The exact controller, processor or joint-controller roles depend on the processing and signed customer agreements; those roles have not been verified for this draft.
The legal entity name, registered address, data-protection contact and whether a DPO is appointed must be confirmed by the owner before approval. The draft policy pack proposes notifications@anuassures.co.uk for privacy requests; verify that this inbox is monitored and authorised before relying on it.
Whose information and what information
- Organisation representatives: organisation and account details, names and business contact details, account roles, sign-in/session and security records.
- Staff: identity and contact details; employment, role, training, qualification and compliance information; rota, leave, availability, assigned visits, self-reported attendance, work-related notes and files; and, only under the conditions below, duty-location evidence.
- Service users: identity and contact details, care needs and plans, health and other sensitive care information, risks, visits, daily records, consent or feedback records and files. Some of this may be special-category data. It is a separate data category from workforce information.
- Website and service security: sign-in, device/session, audit and technical event information needed to operate, protect or troubleshoot the service.
- Optional mobile features: a device push-notification registration if enabled, and a photo, video or other attachment only when a user chooses to capture or select it for a care record.
Why information is used
Depending on the user and organisation, the service supports account administration, staff and service-user records, care coordination, rotas and visits, training and compliance oversight, leave and cover decisions, communication, audit, security and support. The organisation and AnuAssure must each confirm their purposes and appropriate UK GDPR lawful basis. Where health or other special-category data is used, the relevant condition and any safeguards must also be confirmed. This draft does not assert a lawful basis or condition.
Staff duty location
Location is a staff-only operational feature; service-user accounts are not tracked. The app can send a staff device location only when all of these apply: the person is signed into an authenticated staff account; the organisation has enabled its location policy; the staff member explicitly starts an active duty session that has not ended or expired; and the staff member has granted the relevant operating-system location permission.
- Foreground location is supporting evidence for assigned-care operations during active duty. It is not used for general sign-in and is not a condition of access to care records.
- Background permission is optional. It permits location delivery during the active duty session when the phone and operating system allow it; the operating system can interrupt delivery.
- Staff can stop duty or stop collection on the device and can change or revoke device permission in operating-system settings. The organisation policy is disabled by default. Disabling it ends active duty sessions and clears stored positions.
- Location is not proof of attendance, continuous supervision or an exact device position. Managers see bounded duty evidence for their own organisation; the code does not provide them a raw continuous location feed.
The code removes stale coordinates and ends expired or otherwise invalid sessions, but a complete approved retention schedule for duty, audit and related records remains to be confirmed. Do not infer a fixed retention period from this draft.
Who may receive information
Access is intended to follow organisation, account-role, assignment and sharing permissions. The care organisation may make relevant records available to authorised staff, managers, service users or representatives through role-limited views. The exact sharing responsibilities must be confirmed by each organisation.
Application code uses configurable email delivery (Brevo API or SMTP), private file storage, Expo’s push service when native notifications are enabled, Google Maps for explicitly requested or policy-enabled route estimates, and OpenAI for an explicitly requested, bounded cover-ordering assist. The route request sends coordinates only; the AI ranking request contains short-lived candidate identifiers and allow-listed operational features, not names, notes or GPS coordinates. Which providers are enabled in a given environment, their contracts, subprocessors, processing locations and transfer safeguards have not been verified here. The owner must reconcile those details with current contracts before approval.
Some signed-in web pages load interface resources from the jsDelivr content-delivery network (Bootstrap Icons and Tablesort). This can disclose routine connection metadata to that provider when those pages load. Its current terms, processing locations and any applicable transfer safeguards must also be checked by the owner. These resource requests are separate from cookie consent.
Native notifications are optional and require a separate device permission and registration. The current notification message is generic; it does not include names, care details, destinations or staff positions. A push token is stored for the device registration.
Cookies and browser storage
Essential first-party cookies support sign-in, authenticated sessions, security and short-lived navigation. A versioned first-party preference cookie remembers whether optional custom event analytics are allowed. If accepted, the website may use a short-lived analytics receipt and session storage to prevent duplicate event delivery. No advertising cookies are deliberately added by this application code.
The code also contains organisation-limited custom event analytics. Those scripts and receipts are now withheld until optional analytics is accepted. A separate hosting-platform publishing analytics setting may inject its own tracker outside this application; that setting cannot be verified or controlled by this code and must be checked by the owner before public release. See Cookies and manage cookie choices.
How long information is kept
Care, workforce, safeguarding, employment, account, security and audit records have different purposes and retention needs. The application includes retention and cleanup behavior for some short-lived technical data, but code inspection does not establish a complete, approved retention schedule for all records. The relevant care organisation and AnuAssure must confirm retention periods, deletion rules and any legal holds before this notice is approved. This notice does not create an automatic deletion promise.
Security
The service uses authentication, role and organisation checks, private file handling, session controls and audit records. No software can guarantee security. The owner must confirm the deployed hosting, storage, backup, incident-response and supplier arrangements; this draft is not an audit or compliance certification.
Your choices and rights
For care, service-user, family or employment information managed by a care organisation, contact that organisation first. It decides how to handle requests about those records; AnuAssure can assist it under the applicable service agreement. For information AnuAssure handles for its own purposes, use the verified AnuAssure privacy contact once the owner has confirmed and published it. You may have rights to access, correct, erase, restrict, port or object to certain processing, or withdraw consent where consent is the basis. The right and response depend on the purpose and legal role; deletion is not automatic where records must be retained.
You can reject optional website analytics or change your choice at any time on the Cookies page. Native operating-system permissions are separate from website cookie choices. You can complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint.
Review points before approval
The owner/DPO or legal reviewer must verify the legal entity and contacts; controller/processor roles and customer agreements; each lawful basis and special-category condition; actual active suppliers and contracts; hosting and storage regions and international transfers; the publishing analytics configuration; complete retention schedules; security/backup/incident facts; and request-handling procedures. Until those points are resolved, this remains a draft and must not be represented as approved legal advice or proof of compliance.
Early access and demo requests
Organisation, contact name, work email, job role, service type, optional staffing or compliance response and requested access type are used to review early-access sign-ups or demo requests and deliver a welcome email. Only authorised platform operators can review this information. Submitting a waitlist sign-up creates no account or session.
The optional marketing checkbox is separate from the access request. If selected, the consent timestamp and wording version are recorded and the welcome email includes Founding Circle updates. You can withdraw that marketing consent using the unsubscribe link in the email; withdrawing consent does not change an access request.
Unactivated reviewed-access requests, invitation and access records are eligible for deletion after 90 days; activated request and access history after one year. Cleanup runs during intake and HQ review; a daily maintenance command is available for idle periods. You may ask AnuAssure to delete your request sooner. Deleting request history does not delete an established account or its organisation records. The owner must confirm the waitlist retention period before launch.
Waitlist and demo sign-ups are retained separately from login accounts and reviewed-access records. Failed administrator sign-ins are aggregated into 15-minute windows using a keyed IP-derived value, approximate request country metadata and a count. Old summaries are removed in batches when new failed sign-ins are recorded or the HQ summary is opened. Raw IP addresses, submitted usernames and passwords are not added to this summary. Turnstile by Cloudflare is used for bot protection and receives browser/network information when you complete the security check; its terms, processing location and transfer safeguards must be verified by the owner before launch.
Operational access events contain internal references and timestamps, not applicant details, credentials, raw IP addresses or browsing profiles. They are not joined to optional marketing analytics. Demo workspaces use synthetic examples, never real care data.