Skip to content
Legal

Data Processing Terms

When you use iPO One to manage tenants, clients or contractors, you are the controller of their personal data and we process it for you. These terms are the contract for that processing, under UK GDPR Article 28.

Version 1.0, 21 November 2026

Parties

These terms are between the customer that holds a iPO One account (the Customer, the controller) and iPO Hub Limited, company number 17587035, 30 Scott Hall Place, Leeds, LS7 3JR, ICO registration ZC306057 (iPO Hub, the processor). They form part of our Terms of Service (the Main Agreement). If the two conflict on data protection, these terms prevail.

1. Definitions

“UK GDPR”, “personal data”, “processing”, “controller”, “processor”, “data subject” and “personal data breach” have their meanings in UK data protection law, including the Data Protection Act 2018. Customer Personal Data means personal data the Customer, its staff or its clients put into iPO One, or that iPO One creates for the Customer in providing the service. A sub-processor is a third party we engage to process Customer Personal Data.

2. Roles

2.1 For Customer Personal Data, the Customer is the controller and iPO Hub is its processor.

2.2 iPO Hub is a controller in its own right for its own account, billing and security data, as set out in our Privacy Notice. The Customer instructs iPO Hub to create anonymised, aggregated statistics from Customer Personal Data. iPO Hub does not use Customer Personal Data for its own purposes in any other way, and never publishes statistics from which a person or property can be identified.

2.3 A landlord who holds their own iPO One organisation and gives a letting agency access to it is a separate controller of that organisation's data, under their own terms with us. Schedule 3 applies.

3. Details of processing

Subject matter
Providing iPO One: property, tenancy, compliance, rent, repairs and communications management for the Customer's lettings business.
Duration
The term of the Main Agreement, then clause 4.7 and, for agencies, Schedule 3.
Nature and purpose
Hosting, storage, organisation, retrieval, sending (email and in-app messages), automated reading of documents and triage of repair reports, generation of notices and reports, and deletion.
Data subjects
Landlords (including an agency's clients), tenants and household members, guarantors, contractors, and the Customer's staff.
Personal data
Names, contact details, addresses, tenancy and rent records, payment and arrears records, Right to Rent check records, deposit records, repair reports and messages, uploaded documents (which may contain any of these), and sign-in identifiers.
Special category data
Breathing Space (debt respite) records, which can include a mental health crisis moratorium, are processed by design, seen only by the Customer's users who manage that tenancy. Other health information may appear in messages, repair reports or documents; it is not requested.

4. Our obligations

4.1 Instructions. We process Customer Personal Data only on the Customer's documented instructions: the Main Agreement, these terms and the Customer's use of the service's features (including automated reading of documents and triage of repair reports), including for transfers outside the UK (clause 7), unless UK law requires otherwise; in that case we tell the Customer first unless the law forbids it. We tell the Customer straight away if we believe an instruction breaks data protection law.

4.2 Confidentiality. Everyone at iPO Hub with access to Customer Personal Data is bound by confidentiality. Access is limited to named people who need it, uses two-step verification and is logged.

4.3 Security. We keep the measures in Schedule 2 (Article 32) in place and under review.

4.4 Sub-processors. Clause 6.

4.5 Data subject rights and complaints. We help the Customer answer requests from data subjects (access, rectification, erasure, restriction, portability and objection) and complaints, including under section 164A of the Data Protection Act 2018. The service includes tools for subject access bundles and erasure. We pass on any request we receive directly, without answering it ourselves, unless the Customer asks us to.

4.6 Assistance. We help the Customer with security, personal data breach notification, data protection impact assessments and prior consultation with the ICO (Articles 32 to 36), taking into account the nature of the processing and the information available to us.

4.7 End of processing. When the Main Agreement ends, the Customer can export its data for 30 days. We then delete Customer Personal Data, and existing copies, within a further 60 days, unless UK law requires us to keep it. Backups expire on their normal cycle. For agencies, Schedule 3 applies first.

4.8 Demonstrating compliance. We make available the information needed to show we meet Article 28, and allow for and contribute to audits, including inspections, by the Customer or an auditor it appoints: on 30 days' notice, at most once a year unless a breach or a regulator requires more, at the Customer's cost unless the audit finds a material breach by us, and subject to confidentiality. We may first answer an audit request with documents (these terms, our security summary and test results).

5. Personal data breaches

5.1 We notify the Customer of a personal data breach affecting Customer Personal Data without undue delay, and in any case within 72 hours of becoming aware of it, so the Customer can notify the ICO where Article 33 requires.

5.2 The notice includes, as far as then known, the nature of the breach, the categories and approximate numbers of data subjects and records, the likely consequences, the measures taken or proposed, and a contact. What is not yet known follows as soon as it is.

5.3 We do not notify the ICO or data subjects about Customer Personal Data on the Customer's behalf unless the Customer asks us to or the law requires it.

6. Sub-processors

6.1 The Customer gives general authorisation for the sub-processors on our sub-processor list (Schedule 1).

6.2 We give at least 30 days' notice, by email to the Customer's account administrator and on that list, before adding or replacing a sub-processor. The Customer may object on reasonable data protection grounds within that time. If we cannot resolve the objection, the Customer may end the affected service without penalty.

6.3 We bind each sub-processor by written contract to data protection obligations at least as protective as these terms, and remain liable to the Customer for its sub-processors' performance.

7. Where data is processed

We use European regions, in the UK or Ireland where the provider offers them. Where Customer Personal Data is processed outside the UK, we make sure the transfer is covered by UK adequacy regulations or, otherwise, by the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, with a transfer risk assessment.

8. Liability and general

Liability under these terms is subject to the limits in the Main Agreement. These terms are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

Schedule 1: Sub-processors

The current sub-processor list, with what each provider does, the data it handles and where.

Schedule 2: Security measures

  • Access: passwordless sign-in (passkeys, Google, one-time email codes with rate limits); short sessions with renewal that detects reuse; our staff console limited to named people, with two-step verification and sign-in alerts.
  • Encryption: in transit (TLS) and at rest; sensitive personal details also encrypted by us in a separate vault, with the key held apart from the database.
  • Separation: every request is checked against the Customer's organisation, and the database enforces the same separation.
  • Integrity and audit: an append-only audit trail with regular integrity checks, and a log of sign-ins.
  • Resilience: protection against denial-of-service attacks, database backups with point-in-time restore, and an incident response procedure.
  • Development: code review, automated tests, secret scanning and dependency alerts on every change, and security reviews.

Schedule 3: Letting agencies (offboarding)

This schedule applies when the Customer is a letting agency managing properties for landlord clients, when its appointment by a landlord ends, or when these terms end:

  • The landlord keeps their organisation. The landlord's own iPO One organisation (properties, tenancies, documents, compliance and rent records) stays live and usable by the landlord. The agency's access to it ends. From then on the landlord is the controller of that data, under their own terms with us.
  • The agency keeps a frozen archive. The agency keeps read-only access, for its administrators, to a fixed copy of the records it created or handled while managing that landlord's properties: tenancy records, rent and arrears history, notices served, compliance evidence, repairs and messages. Nothing in the archive can be changed, and it does not follow later changes in the landlord's organisation. The agency is the controller of the archive.
  • End of the archive. We keep the archive for 6 years from the end of the appointment (the period in which legal claims can usually be brought), then delete it after 30 days' notice to the agency, unless the agency asks for an export first.
  • Requests from data subjects. The agency handles requests about the archive, with our help (clause 4.5). Requests about the live organisation go to the landlord.
  • Leaving altogether. When the agency leaves iPO One, this schedule applies to each landlord it manages, and clause 4.7 applies to any other Customer Personal Data.

Questions about these terms: [email protected]. Agency subscribers: see also the Agency subscribers schedule in our Terms.