Documents
This software schedules inspection and maintenance work in people’s homes, so it holds their names, their telephone numbers and notes about how to get in. These pages say what that amounts to.
Privacy notice
For a tenant, an engineer, or anybody asking what is held about them.
Every category of personal information this system holds, why it is held, how long for, and whether it can be erased on request. It names the actual fields, and a test holds those names against the database so this cannot quietly go out of date.
What this does, and what it does not
For a firm deciding whether to rely on it.
The plain capabilities, and — more usefully — the eight things it deliberately does not do. The first of those is that the safety button tells the office and is not an emergency service.
Support, and what to do when something goes wrong
For whoever runs the system, and for an incident at two in the morning.
Where the data is, how to get a backup out, what to do about a suspected breach, and how somebody asks for their information or asks for it to be removed.
What is not here
There is no contract on these pages — no terms of service, no data processing agreement, no service level. Those are agreements between two companies with money and liability in them, and drafting one is a solicitor’s work. A generated contract that read as finished would be worse than none, because somebody would rely on it.
What a solicitor needs in order to write one is mostly annexes — what is processed, whose it is, who else touches it, how long it is kept and what protects it. Every one of those is a fact about this software rather than a term to be argued over, and they are on the privacy notice in the form the annexes want.
Anything else, including a request about your own information, goes to the office.