Data processing agreement

Last updated 9 Nov 2026

Every customer has a data processing agreement with Stedwise. The full agreement forms part of the terms of service: email hello@stedwise.co.uk for a signed copy.

In short

Your organisation decides how the data about residents, staff and other people is used. We handle it only on your instructions.
We keep it secure, and we store it in the United Kingdom.
We never send resident personal data to an AI model.
We tell you before we add or replace a company that handles data for us (a sub-processor).
If there is a data breach, we tell you without undue delay.
When the contract ends, you can export your data. Then we delete it.

This is a short summary in plain English. The full text below is what applies.

Roles

The customer is the controller for the records it keeps in Stedwise about residents, staff, key people, referrals and incidents. Stedwise is its processor. This means the customer decides why and how the data is used, and Stedwise handles it for the customer. Roles are assessed activity by activity: for account and billing data, Stedwise is the controller (see the privacy notice). Doffy Labs Ltd is on the data protection register, reference ZC268927.

What we process

People: residents, staff and volunteers, directors and service managers, referrers and other contacts the customer records.
Data: contact and role details; support records, referrals and incidents, which are special category data (extra-sensitive data that the law protects more strongly); and fit-and-proper check outcomes and dates, which are criminal offence data. We never store the contents of a criminal record certificate.
Purpose: only to provide Stedwise to the customer, on its documented instructions.

Our commitments

Process personal data only on the customer’s instructions, and tell it if we think an instruction breaks data protection law.
Make sure everyone with access is bound by confidentiality, and that support access is audited.
Keep appropriate security: UK hosting for the database, files and backups, TLS in transit (data is encrypted while it travels), encryption at rest (and while it is stored), field-level encryption for special category fields (the most sensitive fields are each encrypted separately), roles scoped to schemes, two-step verification for owners and managers and for anyone who can open resident, referral, safeguarding or criminal record check records, and an audit log of every view and change to resident, staff and incident records.
Never send resident personal data to an AI model.
Use sub-processors only under written terms that give the same protection, and name them to customers in Stedwise (Settings, Data protection), with the kind of service and region on the public sub-processor page. We tell customers before adding or replacing one, so they can object.
Help the customer respond to people exercising their rights, with a subject access export and an erasure workflow for each person.
Tell the customer without undue delay after becoming aware of a personal data breach, with the information it needs to meet its own duties.
Help with data protection impact assessments and consultations with the regulator where our processing is involved.
At the end of the contract, let the customer export its data, then delete it, unless the law requires us to keep it.
Make available the information needed to show we meet these commitments, and allow for reasonable audits.

A managing agent, a housing association and a support provider are usually separate controllers. Stedwise shares nothing between them without a recorded consent and a data sharing agreement. A housing association sees counts and statuses, never resident records.

International transfers

Customer data is stored in the United Kingdom. Where a sub-processor processes data outside the UK, it is named on the sub-processor list with its region, and the transfer is covered by UK transfer safeguards.

Getting the full agreement

Email hello@stedwise.co.uk for a signed copy.