Subprocessors
Draft for legal review. The production list depends on provider choices still being made. The prototype's own set-up is noted separately below.
These companies process Customer Personal Data for ROCC to run ROCC Tracker. ROCC gives notice of changes as set out in the Data Processing Agreement.
| Subprocessor | What for | Data | Where |
|---|---|---|---|
| Cloudflare, Inc. | Hosting: application, database, live journeys, photo storage, network and security | All Customer Personal Data | Stored in the EU jurisdiction; processed in transit on Cloudflare's global network |
| [Email delivery provider: Cloudflare Email Service, or Amazon SES, Postmark or Resend] | Sending customer and operative emails | Recipient name and email address, message content (including the tracking link) | [to confirm] |
Services that don't receive personal data
- Routing (production): ROCC hosts its own routing (OSRM or Valhalla on OpenStreetMap data), so operatives' positions don't leave Tracker to work out routes.
- Map tiles: served through Tracker's own tile proxy, so tile providers see Tracker's servers rather than customers' or operatives' devices.
- Postcodes and UPRNs: looked up in Tracker's own copies of open datasets.
Customers' browser notification services
If a customer turns on notifications on the tracking page, Tracker sends them through the push service their own browser uses, run by Google, Apple, Mozilla or Microsoft. The customer's browser chooses it, not ROCC. Messages are encrypted for the customer's device, so the push service sees only the address and when a message is sent.
Services you connect yourself
When you choose them, these are your providers, not ROCC's subprocessors:
- your webhook, for sending customer messages through your own SMS, WhatsApp or email provider;
- your GOV.UK Notify account [planned];
- your own sending domain for email [planned].
The prototype
The technical prototype isn't a production service, and differs in three ways:
- it calls the public OSRM demo server for routes, which receives operatives' start positions;
- it uses postcodes.io for address search;
- it shows OpenStreetMap's public tiles.
None of these would be used in production.