Clear information
for a considered decision.
Understand the purpose, service boundaries and assurance material relevant to your deployment.
Purpose and proportionate collection.
Each deployment should define the property question, the information needed and the operational decision it supports. Standard environmental monitoring does not require cameras or recorded conversations.
Specialist inputs need an explicit purpose, an appropriate assessment and clear information for residents or occupants.
Data flows, roles and access.
Discuss processing roles, data flows, hosting, subprocessors, access control and retention. Customer access is described as role-based, with technical administration separated from ordinary operational use.
Confirm the actual deployment arrangements in the service documentation, including authentication and any SSO requirements.
Service operation and continuity.
The service includes supervision of expected device reporting, with equipment-health conditions such as lost connectivity, low battery and power interruption identified where supported.
Agree support hours, update responsibilities, incident handling, backup and recovery arrangements, equipment ownership, replacement and contract exit.
Interfaces and integration.
Discuss API, webhooks, SSO and workflow connections against your existing systems. The proposal confirms current availability, data formats, implementation work and ongoing responsibility.
An integration should support a defined process. Where the handoff is manual, that should be clear too.
Request the relevant assurance material.
- Service scope, data flows and processing roles.
- Access, authentication, logging and security controls.
- Hosting, subprocessors, retention and data export.
- Support, continuity, incident handling and exit.
- Information to support privacy and impact assessments.