Skip to content
AnuAssure

AnuAssure / public documents

Policy centre

Read policy documents and their edition details.

Policy document

External providers and AI assistance

Version 2026-11-11.3 Scope: AnuAssure platform; each organisation retains its own operational approvals Published · owner approved Owner approval recorded: 16 November 2026
Edition fingerprint

SHA-256: f77fd3d4317ac4eb6881d2fddd94dd9568801f5e159e1ba50dfeb598ce6a7963

Document editions

4.1 Purpose

This section identifies every external provider ANUASSURE LTD uses to deliver the platform, the role each plays, the data they receive, and the mechanism relied on for international transfers.

4.2 Providers

Provider | Role | Data received | Jurisdiction | Transfer mechanism Replit, Inc. | Processor: application hosting and private file storage (pre-launch) on Google Cloud infrastructure | Platform data at rest and in transit | USA | UK Addendum to EU SCCs (confirmation in progress) Brevo (Sendinblue SAS) | Processor: transactional and notification email | Recipient email address; notification stub content only (see 4.3.3) | EU (France) | Adequacy (EU-UK) Expo, Inc. | Processor: push notification delivery (feature currently blocked, see 4.3.4) | Push token; non-identifying payload | USA | UK Addendum to EU SCCs (DPA in flight) Google LLC (Maps Platform) | Independent controller for routing | Coordinates or address strings only | USA | Google Controller SCCs with UK Extension Anthropic PBC (Claude API) | Processor: optional AI cover-ordering assist | Pseudonymous worker identifiers and operational features only; zero data retention enabled | USA | UK Addendum to EU SCCs jsDelivr | Public CDN (no personal data) | None | Global | Not applicable

4.3 Provider-specific rules

4.3.1 AI cover-ordering assist (Anthropic) Shortlist capped at eight eligible workers per call. Inputs are pseudonymous worker identifiers and operational flags only. Worker names, care notes, and GPS coordinates are never sent. Zero data retention is enabled on the Anthropic API account. The assist produces an explanation; it cannot assign a shift. A human makes the assignment. 4.3.2 Routing (Google Maps) Requests contain coordinates or address strings only. No worker names, no service user identifiers, no care content. A per-organisation routing enable is required before any call is made for that organisation's data. Calls are cached at platform level to reduce request volume. 4.3.3 Email (Brevo) Notification bodies contain no clinical or care content. Standard body: "There is an update. Sign in to view." Plus sender identification. Distribution lists must not include any special category attributes. Delivery monitoring is active; bounces are logged and surfaced to the sending organisation. 4.3.4 Push (Expo) Feature currently blocked: `EXPO_PUSH_TOKEN` is not present in the workspace Secrets and the Expo Data Processing Agreement is in flight. When enabled, payloads carry no personal data beyond what is necessary to route the notification to the user's device. Opt-in by the staff member and OS permission are both required.

4.4 Sub-processor changes

Changes to this list are notified to care organisation customers with at least 30 days' written notice. The customer may object within 14 days under clause 7.2 of the Data Processing Agreement.

Service scope

Provider use depends on the applicable agreements and authorised configuration. AI assistance is advisory, not automatic assignment or clinical judgement.