Sub-processors
The outside services we use that receive personal data. Businesses get 30 days' notice of a new one, with the right to object.
Draft: needs legal review
A starting point written for a UK software service. It has not been checked by a lawyer and is not yet in force.
| Service | What it receives | Why | Where |
|---|---|---|---|
| Hosting: Hallie's own server | Everything in the app | Running Hallie | United Kingdom |
| Google (Gmail SMTP) | Recipients' email addresses and the message text: sign-in links, invitations, and client messages once switched on | Sending email | Google data centres (UK, EU, US) under Google's data processing terms |
| Google and Microsoft sign-in | The person's name, email address and an account number, when they choose that way of signing in | Signing in without a password | Google; Microsoft |
| postcodes.io (Ideal Postcodes) | A postcode on its own, with no name attached | Turning postcodes into map positions for planning | United Kingdom |
| OpenStreetMap Foundation map servers | The viewer's IP address and which map squares they look at, which can show the area around a client's home | Drawing maps of routes | United Kingdom and worldwide caches |
Not sub-processors
- The route server that works out drive times: we run our own copy.
- The walker's own maps app: directions open in it at the walker's choice.
- Browsers and phones: they belong to the people using them.
Changes we'll tell businesses about before they happen
- Moving email to a sending service, such as Amazon SES (London) or Resend.
- Moving hosting to a rented server, such as Hetzner in Germany or Finland.
- Moving map pictures to a paid or self-hosted source.
- Adding card payments through Stripe, which is a separate controller for card data.