Skip to content
Last updated

The iHub aims to deliver Standard Data Model payloads in near real-time. All Single Online Home (SOH) submissions that are submitted via Standard API are aimed to be delivered to client forces within 1 minute of the form being submitted.

Information on this page has been derived from section 8.6 of the iHub ODD document.

Average and Peak Message Sizes

ServiceAverage Delivery TimeAverage Message SizePeak Message Size
Online Crime Reports< 1 Minute150 kb210 kb

Figures above do not include public-provided media in Single Online Home.

Rate Limiting

For Standard APIs, we can limit the number of requests the iHub makes per unit of time. This prevents the overloading of the target service and prevents the iHub as being identified as the potential source of a denial-of-service (DoS) attack.

Information Management

All data should be protected in compliance with the Data Protection Act (DPA) 2018 and General Data Protection Regulations (GDPR).

The IHub Service Responsibility

In this model, the iHub is a data processor acting on behalf of, and under the authority of, the relevant data controllers within each force. The service is responsible for applying the relevant security, integrity and retention elements required to support the delivery of the service.

For full details of the iHub service responsibilities, refer to section 8.6.5 of the iHub ODD documentation.

Ownership and accountability

Each client force will be the data controller for the personal data input to SOH, and that flows through the iHub, for their specific organisation.

If a client force considers it appropriate, they are able to complete their own DPIA (Data Protection Impact Assessment) or append information to the provided DPIA if the current version is deemed unsuitable for their force’s Data Protection Officer to sign.

Lawful basis for processing data

Each client force is expected to establish the lawful basis for all processing of personal data.

It is the responsibility and accountability for individual client forces to determine if SOH achieves their lawful purpose.

For full details on the lawful basis for processing data, refer to section 8.6.5 of the iHub ODD documentation.