Skip to content

beespace Data Processing Agreement

Last updated 19 November 2026

This Data Processing Agreement (DPA) forms part of the beespace Software as a Service Supply Agreement (the Agreement) between the customer named in the Agreement (the Customer or the Controller) and beespace Technologies Ltd T/A beespace, company no. NI646408 (the Processor). Where this DPA and the Agreement conflict on Personal Data, this DPA prevails.

1. Definitions

  • Data Protection Laws: the UK GDPR, the Data Protection Act 2018, the EU GDPR (Regulation 2016/679) and any national law implementing it, as applicable to each party.
  • Personal Data, Data Subject, Controller, Processor, Personal Data Breach: as defined in the Data Protection Laws.
  • Processing: any operation performed on Personal Data, by automated means or not, including collection, recording, organisation, structuring, storage, alteration, retrieval, consultation, use, disclosure, combination, restriction, erasure or destruction. The Processor processes only on the Controller's direct instruction and makes no decisions about the purpose of processing.
  • Sub-processor: a third party engaged by the Processor to process Personal Data under this DPA.

2. Roles and the Controller’s obligations

2.1 The Customer is the Controller and beespace is the Processor of the Personal Data described in Annex 1.

2.2 The Controller is responsible for identifying a lawful basis for the processing before it begins. Where consent is relied on, the Controller will ensure it is a clear indication of agreement, and will tell the Processor promptly when consent is withdrawn so that processing stops.

2.3 The Controller will give Data Subjects appropriate notice of the processing (for example, privacy notices and signage where sensors are installed), so that it is within what they would reasonably expect.

2.4 The Processor’s data protection contact is Andy Low (andy@bee.space).

3. Processor’s obligations

3.1 Instructions. The Processor will process Personal Data only on the Controller's documented instructions, as set out in the Agreement, this DPA and Annex 1. It will tell the Controller if it believes an instruction breaks Data Protection Laws.

3.2 No own use. The Processor will not use Personal Data for its own purposes. Any rights the Processor has in Collected Data under clause 5.2 of the Agreement apply only to anonymised or aggregated data that is not Personal Data.

3.3 Confidentiality. Staff with access to Personal Data are bound by confidentiality obligations.

3.4 Security. The Processor will apply the technical and organisational measures in Annex 2.

3.5 Sub-processors. The Controller has authorised Sub-processors (Annex 3). The Processor will give 30 days' written notice of any new Sub-processor, and the Controller may object on reasonable grounds. Each Sub-processor will be bound by equivalent data protection terms, and the Processor remains liable for their performance.

3.6 Data Subject rights. The Processor will help the Controller respond to Data Subject requests, including access, rectification, erasure, objection and restriction of processing. On instruction to restrict, the Processor will mark the relevant data and stop processing it except for storage until told otherwise. Requests received directly will be passed to the Controller within 5 working days and not answered by the Processor.

3.7 Breaches. The Processor will notify the Controller of a Personal Data Breach without undue delay and within 48 hours of becoming aware of it, with the information the Controller needs to meet its own reporting duties.

3.8 Assistance. The Processor will give reasonable help with data protection impact assessments and any consultation with a supervisory authority.

3.9 Transfers. Personal Data will be stored and processed in the UK, the EEA, or countries with an adequacy decision under the Data Protection Laws. Any other transfer will be made only with appropriate safeguards in place, such as the UK International Data Transfer Addendum or the EU Standard Contractual Clauses.

3.10 End of contract. Within 30 days of termination the Processor will delete or return all Personal Data, at the Controller's choice, unless law requires it to be kept, and will confirm deletion in writing on request.

3.11 Audit. The Processor will provide the information needed to show compliance with this DPA, and allow an audit by the Controller or its auditor on 30 days' notice, no more than once a year unless following a breach or at a regulator's request.

3.12 Liability. Each party's liability under this DPA is subject to clause 7 of the Agreement.

Annex 1: Processing description

ItemDetail
Subject matterProvision of occupancy and environmental sensing and the beespace dashboard under the Agreement
DurationThe term of the Agreement plus the 30-day deletion period
NatureCollection, storage, aggregation and presentation of sensor data; hosting of dashboard user accounts
PurposeReporting space utilisation and environmental conditions to the Controller
Data SubjectsController staff who use the dashboard; employees, occupants and visitors in monitored spaces, to the extent sensor data relates to them
Personal DataDashboard users: name, work email, login credentials, access logs, IP address. Sensor data: occupancy status and environmental readings, which do not identify individuals.
Special category dataNone

Annex 2: Security measures

  • Encryption of data in transit (TLS) and at rest
  • Role-based access, least privilege and multi-factor authentication for staff and admin access
  • Hosting with AWS, in the UK/EEA
  • Access logging and monitoring
  • Regular backups and tested restore
  • Staff data protection training and confidentiality terms
  • Certification: Cyber Essentials certified; ISO 27001 in progress

Annex 3: Authorised Sub-processors

  • Amazon Web Services (AWS): cloud hosting, London region (eu-west-2)
  • Laravel Cloud: application hosting platform, running on AWS
  • Tigerdata Cloud: managed database platform, hosted in AWS London (SOC 2 Type 2)
  • Loriot: LoRaWAN network server (routes encrypted sensor data)
  • Auth0 (Okta): user authentication and MFA