Policy document
Notifications and delivery
Edition fingerprint
SHA-256: 1296031568725593ce0e73d98597f9614f30c02075cfa2247e483af5147e9765
5.1 Purpose
This section describes how AnuAssure delivers operational notifications to care organisations and their users, what channels are available, what content is permitted, and what checks apply before any notification is sent.
5.2 Channels
Channel | Current state | Provider | Content permitted In-app notification | Available | ANUASSURE LTD | Full operational detail within the app surface Email | Available | Brevo | Notification stub only; no care, clinical or location content Native push | Blocked | Expo | Non-identifying payload only; blocked until Expo DPA and push token are in place Risk or rounds email alerts | Separately enabled per organisation | Brevo | Follows the stub rule above
5.3 Rules that apply to every channel
Recipient must be an authorised account holder for the organisation or a named recipient recorded for a specific purpose. Recipient addresses are checked for validity before send; failed deliveries raise an operational alert. Approved fallback: if the primary channel fails, the system does not silently retry through another channel. Sending is always triggered by an operational event (rota change, cover request, overdue task). No automatic marketing or round-robin messaging. Human review is required for drafts intended for external recipients (for example, escalation drafts going outside the care organisation). Drafts do not auto-send.
5.4 Email content
Subject: a short description of the type of notification. No care, clinical, or location content. Body: a stub of the form "There is an update. Sign in to view." Sender identification. Footer: ANUASSURE LTD contact, unsubscribe where applicable, and a link to the privacy policy.
5.5 Push content
When enabled, push payloads carry only the minimum needed to route the user to the right place in the app. They do not display care details on the lock screen.
5.6 Preferences
Each account holder can set their own notification preferences within the limits permitted by the care organisation. Statutory and safety-critical alerts cannot be opted out of.
5.7 Delivery monitoring
Delivery success, bounce, and complaint rates are monitored. Repeated failure to a recipient triggers a check of the stored address and a prompt to update it.
Service scope
A submitted notification is not proof of receipt. Notifications are not an emergency response service.