Data Processing Agreement (DPA)
Our data processing agreement with care homes
Effective date: 30 October 2026 | Version 2.0
This agreement is between More Days Limited, 120 Cavendish Place, Eastbourne, East Sussex BN21 3TZ (the "Processor", "we" or "us"), and the organisation that asks us to set up a More Days Studio account (the "Customer" or "Controller").
1. What this agreement covers
This agreement sets out how we handle personal information on the Customer's behalf when it uses More Days Studio ("Studio").
2. Agreeing to it
When the Customer asks us to set up a Studio account, it confirms that it has read and agrees to this agreement. This agreement forms part of our Terms of Use.
3. What we process and why
We provide an online service that helps care homes plan activities, record how residents take part and evidence their wellbeing. We only process what we need to provide that service.
| Element | Details |
|---|---|
| Subject matter | Activity planning, activity records, wellbeing reporting and family updates for care homes |
| Duration | For as long as the Customer uses Studio, then as section 7 sets out |
| People the data is about | Residents, care home staff and managers, and family members the Customer invites |
| Types of data | Names and contact details; resident profiles and life stories; photos and videos; activity records, moods and engagement; wellbeing scores; sign-in and usage records; information from the Customer's care record system (PCS) where the Customer links it |
| Special category data | Health and care information about residents, such as care level, cognitive level, mobility, risks, placement type and wellbeing observations |
4. What we will do
We will:
- process personal information only on the Customer's documented instructions, including for any transfer outside the UK
- tell the Customer straight away if we think one of its instructions breaks data protection law
- make sure our team keeps it confidential
- keep it secure, as Schedule 2 describes
- tell the Customer about any personal data breach without undue delay, and within 72 hours of finding it
- help the Customer respond to people who use their data protection rights
- help the Customer with its security and breach duties, its data protection impact assessments and any consultation with the ICO
- keep records of our processing and give the Customer the information it needs to show it complies with the law
- make sure every subprocessor signs data protection terms at least as strong as these
5. Subprocessors
The Customer allows us to use the subprocessors in Schedule 1. We will tell the Customer before we add or replace a subprocessor, so it can object. We remain fully responsible for our subprocessors.
6. Where we process data
We host Studio's database, files, app and backups in the United Kingdom (London). Some subprocessors in Schedule 1 may process data outside the UK. Where they do, our contracts with them include the safeguards UK law requires.
7. When the agreement ends
When the Customer stops using Studio, we will return or delete its personal information, as the Customer chooses, within a timescale we agree with it, unless the law requires us to keep it. We will confirm in writing when we have done so.
Today, Studio can replace a resident's name with random characters and clear their personal details. It does not yet remove related records, such as activity records, wellbeing score history and photos the resident is tagged in. Customers cannot remove residents themselves yet, so the Customer asks us to do it.
8. The Customer's responsibilities
The Customer will:
- act as the controller of the personal information it puts into Studio
- have a lawful basis for that processing, including a condition for health information
- tell residents, staff and families that it uses Studio, including its use of AI
- record residents' choices about photos and keep them up to date
- enter only the information it needs, lawfully and fairly
9. Audits
The Customer may ask for a summary of our security and compliance documents once a year, or after a serious security or privacy incident. If the summary is not enough, the Customer (or an auditor it appoints) may audit us, with reasonable notice and at a time we agree.
10. Governing law
The law of England and Wales governs this agreement.
Schedule 1: Approved subprocessors
| Subprocessor | What they do | Where they process data | Safeguards |
|---|---|---|---|
| Xano | Database and backend services | United Kingdom (London) | Not needed (UK) |
| Amazon Web Services (AWS) | File and photo storage; removes personal details from text before AI requests | United Kingdom (London) | Not needed (UK) |
| Vercel | Hosts the Studio app and website; briefly holds family video uploads | United Kingdom (London) | Not needed (UK) |
| OpenAI | AI: activity plans, record reviews, resident summaries and matching | May be outside the UK | Covered by our contract |
| OpenRouter (passing requests to Google Gemini) | AI: activity plans, activity suggestions and anonymising text | May be outside the UK | Covered by our contract |
| MailerSend | Service emails, such as invitations and password resets | May be outside the UK | Covered by our contract |
| Slack | Internal alerts about the care record system connection, carrying home names, counts and errors but no personal information | May be outside the UK | Covered by our contract |
Expo sends updates to the Moments app on Android. When the app checks for an update, Expo receives the device's IP address and a random installation ID, but nothing about users or residents. This may happen outside the UK, under our contract with Expo.
Google Analytics and Google reCAPTCHA only run on our public website. They do not process the Customer's Studio data.
Where the Customer links Studio to PCS, we exchange information with PCS on the Customer's instructions. PCS is the Customer's own supplier, not our subprocessor.
To object to a new subprocessor or ask for this list, email talktous@moredays.co.uk.
Schedule 2: How we keep data secure
This schedule sets out the technical and organisational measures we take to keep data secure, as UK data protection law requires.
1. Access and sign-in
- Every user has their own account.
- Role-based permissions control what staff, managers, care group managers and family members can see and do.
- Staff on shared tablets switch user with a personal PIN. Studio locks after a period of inactivity, and only a valid PIN or password unlocks it.
- Sign-ins expire after 8 hours at most.
- Family members only see the residents they are linked to.
- Our developers (to investigate a fault) and customer success managers (to help a care home manager) can view Studio as a customer user, but only when the Customer has a technical problem. Each session lasts no more than 2 hours, never covers a platform administrator and is recorded.
2. Encryption
- We encrypt all data in transit.
- We store PINs in a scrambled (hashed) form, and we encrypt the cookie that keeps users signed in.
3. Hosting
- Xano, AWS and Vercel host Studio in the United Kingdom (London).
- Photos sit in private storage and open only through signed links that Studio creates for signed-in users.
4. Backups and recovery
We back up Studio's data and keep the backups in the United Kingdom.
5. Logging
- Studio records key security events, including PIN set-up and changes, password confirmations, support access by More Days staff, care record system syncs and changes to staff accounts, homes and groups.
- We keep these records for 2 years.
6. Our team
- Only authorised team members can access personal information, under confidentiality agreements.
7. Privacy by design
- Studio collects only what care homes need to plan and evidence activities.
- Studio checks each resident's photo choice before any photo reaches families, and staff must cover the faces of residents who have not agreed to photos.
- Before any AI request, a scrubbing step removes names, places, dates and contact and ID numbers from the text. If it fails, nothing is sent.
8. Incidents
- We have procedures to find, report and investigate incidents.
- We tell the Customer about personal data breaches without undue delay, and within 72 hours.
- We look into the cause of every incident.
9. Suppliers
- We check subprocessors before we use them and put data protection terms in place.
- We keep the subprocessor list in Schedule 1 up to date.
10. Certification
- We hold Cyber Essentials certification (certificate 09ce4ed6-1044-4b28-a355-5a90f3281664, valid until 2 December 2026).
For questions about this agreement, our subprocessors or our compliance documents, email talktous@moredays.co.uk.