How our office sensor network works, and how it keeps your data secure
OpenSensors designs, installs and runs your office sensor network as a managed service. Our sensors stay off your corporate network, and only anonymous occupancy and room readings reach our cloud platform.
This page explains how it all fits together: what is installed in your building, how data travels, how each step is protected, and what your team needs to do. It is written for IT and information security reviewers, but facilities and real estate teams should find it easy to follow too.
Certified to ISO/IEC 27001:2022 since June 2019.
On this page
The four things IT teams usually ask first
If you only read one section about our office sensor network, read this one.
Independent of your Wi-Fi
In your office sensor network, battery sensors talk to OpenSensors gateways over LoRaWAN radio. Gateways connect out over cellular by default, or over your Ethernet if you prefer. Nothing joins your corporate network unless you choose wired backhaul.
Encrypted at every step
Sensor messages are encrypted from the sensor to the network server. Gateways reach the cloud over mutually authenticated TLS. Every user connects over HTTPS.
Anonymous by design
Sensors report presence, counts and room conditions. They don’t capture images, video or audio, and they don’t identify people. That’s why we call it anonymous occupancy data.
ISO/IEC 27001:2022 certified
Our information security management system is independently audited. The certificate and supporting documents are available on request.
In plain words, for facilities and real estate teams: the sensors work like a separate, sealed network that we run for you. They count and detect presence, they never see faces, and your IT team doesn’t have to support another set of devices.
From sensor to dashboard: how data moves through the office sensor network
Data from your office sensor network travels one way, outbound, through four stages. No inbound connections are opened to your building or your network.
1 · Sensors · Your building
Desk, room and footfall sensors
Battery powered. They report presence, counts, room conditions and battery health. No images, no identities.
Sensor → gateway: licence-free LoRaWAN sub-GHz radio, on the right band for each region: EU868 (Europe and UK), US915 (North America), AS923 and AU915 (Asia and Pacific). Each device’s messages are encrypted with its own AES-128 session keys.
2 · Gateway · Your building
LoRaWAN gateway
Supplied and run by us. It forwards encrypted messages but can’t read what’s inside them. Needs a mains socket.
Gateway → cloud: outbound only, over cellular or your Ethernet. TLS on port 443, with certificates on both ends.
3 · Platform · AWS Ireland
Network server, processing and storage
AWS IoT Core for LoRaWAN handles device join and authentication. Data is checked, mapped to floors and spaces, and stored encrypted.
Inside the platform: AWS-managed services, AES-256 encryption at rest, access logged and monitored.
4 · Observe · Your users
Dashboards, reports and API
Web dashboards, reports, API and CSV/JSON export for your authorised users.
Platform → people: HTTPS only, SSO (SAML / OIDC) where required, multi-factor authentication and role-based permissions.
On site: power, placement and installation
Sensors in your office sensor network need no cabling. Gateways are the only devices that need power, and we agree their positions with you after a coverage check.
Sensors: battery-powered LoRaWAN occupancy sensors
Mounted under desks, on ceilings or above doorways, depending on what you want to measure. Batteries typically last 2 to 10 years, depending on the sensor type and how often it takes a reading. We monitor battery levels remotely and plan replacements. Battery replacement is part of the managed service, so there is no extra cost to you.
Powered counters are used only where a location suits them and power is available. We confirm these in the design. Every device is recorded in our inventory and mapped to its building, floor and space.
Gateways: mains powered, a few per site
Each gateway needs one standard mains socket, or a PoE port. How many you need depends on your floor layout and construction, so we size them from your floor plans and a coverage check.
We supply, configure, label and maintain every gateway. Cellular gateways carry an OpenSensors-managed SIM, so no customer network port is needed.

Desk mounted sensors

Ceiling mounted sensors

Gateways
What we need from you to design it: floor plans, a list of the spaces in scope, a site contact and installation access.
Network options, ports and firewall rules
You choose how your office sensor network’s gateways reach our cloud. Both options use outbound connections only.
Option A: cellular (default)
The gateway uses an OpenSensors-managed SIM. It never joins your LAN or Wi-Fi, so no firewall changes are needed. Its Ethernet port is set to local-only.
Option B: your Ethernet (on request)
If you prefer wired backhaul, or the cellular signal is poor, the gateway connects to a port you provide, ideally on an isolated IoT VLAN or guest network segment.
Firewall rules for option B
| Direction | Protocol / port | Destination and purpose |
|---|---|---|
| Outbound | TCP 443 (TLS) | AWS IoT Core for LoRaWAN endpoint, Ireland (eu-west-1). Gateway to network server over secure WebSocket (LoRa Basics Station). |
| Outbound | UDP 123 | Your NTP servers or public NTP, for clock sync. |
| Outbound | UDP/TCP 53 | Your DNS servers, for name resolution. |
| Local | DHCP or static | Your LAN, for IP addressing. |
| Inbound | None | No inbound ports, port forwarding or VPN are needed. |
We confirm exact endpoint hostnames during the design, so you can allow-list them. Users reach the Observe web app over HTTPS (TCP 443) from any browser. Learn more about LoRaWAN from the LoRa Alliance.
What anonymous occupancy data we collect, and what we don’t
Your office sensor network only protects privacy if you can see exactly what it sends. Here is the full list.
Collected
- Desk and room presence (occupied or unoccupied)
- People counts at rooms and entrances
- Room conditions where measured: temperature, humidity, CO₂, light and noise level
- Device health: battery, signal and last seen
Never collected by sensors
- Images, video or audio recordings
- Names, badge IDs or any other identity
- Phone, laptop or Wi-Fi identifiers
Where data is stored and for how long
| Item | Detail |
|---|---|
| Hosting | Amazon Web Services in Ireland (EU). Data stays in the UK and EEA unless you agree otherwise in writing. |
| Encryption | AES-256 at rest. TLS 1.2 or higher in transit. |
| Backups | Encrypted, taken hourly and kept for 14 days. |
| Security and access logs | Kept for 12 months. |
| When you leave | 30 days to request a copy. Deleted from live systems within 30 days, then from backups within a further 14. |
| Ownership | You own all your data, and we permanently delete it at your request. |
Accuracy you can check
Sensor accuracy is between 95% and 99.8%, depending on the sensor type and the space. During installation, our deployment engineers test and confirm each measurement manually before handover, and we run data quality checks before anyone relies on the findings.
If you use Orbit for desk and room booking, booking records are named, and they are held separately from the anonymous sensor data. The exact readings depend on the sensor models agreed for your site.
Data protection: GDPR compliant occupancy sensors, with clear roles
Our standards are set out in Schedule 1 (Data Protection) of our Master Services Agreement, and run under our ISO 27001 data protection policy.
Clear roles
You are the data controller and OpenSensors is the processor. We process personal data only to provide the service, and only on your documented instructions.
Minimal personal data
Sensor data is anonymous. Personal data is limited to user accounts, sign-in, support records, security logs and, if used, Orbit bookings.
Classified and encrypted
Information is classed as Confidential, Internal or Public, with handling rules for each. Confidential data is encrypted and access is need-to-know.
Transfers and sub-processors
No personal data leaves the UK or EEA without a lawful mechanism, such as the UK IDTA or EU SCCs. Sub-processor list on request, with 14 days’ notice of changes.
Breaches and your rights
We tell you about a personal data breach without undue delay and within 72 hours. We help with data subject requests and DPIAs.
Deletion, AI and audit
Secure deletion, confirmed in writing on request. We never sell your data or use personal data to train AI models.
Who can reach the devices and the data
Access is limited at every layer of the office sensor network: your users, our staff and the devices themselves.
Your users
HTTPS only. Single sign-on via SAML or OIDC, for example Microsoft Entra ID, where required. Multi-factor authentication, role-based permissions by site and function, and token-based API access.
OpenSensors staff
Only named staff with a support role. MFA and role-based access, every access logged, and access reviewed every year under our ISMS.
Devices
Unique admin credentials for every gateway, held in a password vault. Vendor cloud management is turned off, and sensors can only join if they are registered to our network server.
Monitoring, support and incident response
We watch every device on your office sensor network and the platform behind it, so your team doesn’t have to run another device estate.
Devices and network
Remote health monitoring for every sensor and gateway: online status, battery and signal. Our operations team follows up on any device that goes offline. We manage firmware and configuration, and coordinate maintenance, moves and replacements with your site contact.
Platform
AWS-managed services running across multiple availability zones, with metrics, logging and threat detection (Amazon CloudWatch, AWS CloudTrail and Amazon GuardDuty). Encrypted backups and a tested recovery plan. Email alerts are sent from opensensors.com and signed with SPF and DKIM.
Security incidents
Reported to our Information Security Group at once, then contained, investigated, fixed by severity and documented.
Fix times by severity
Critical within 48 hours. High within 7 business days. Medium within 30 business days. Low within 35 business days.
Personal data breaches
Notified to you within 72 hours.
Who does what
Your IT team decides who gets access. We do almost everything else. Final responsibilities are confirmed in the proposal and order form.
| Activity | OpenSensors | Your team |
|---|---|---|
| Sensor and gateway selection, supply and configuration | Leads | |
| Coverage check, gateway positions and mapping devices to spaces | Leads | Floor plans, space list |
| Mains socket at each gateway location | Leads | |
| Cellular SIM and data plan (option A) | Leads | |
| Ethernet port, outbound 443, DNS and NTP (option B) | Leads | |
| Site access, mounting approvals and a site contact | Leads | |
| Installation, commissioning and data validation | Leads | Access |
| Platform hosting, security, backups and monitoring | Leads | |
| Device health monitoring, batteries and replacements | Leads | |
| Deciding who gets access, and SSO set-up in your identity provider | Roles set-up | Leads |
| Telling staff about workplace sensing | Materials | Leads |
Documentation for your security review
Scope: supply and installation of sensor equipment, and analysis of data on the use of building and office spaces. First certified June 2019.
Certification
| Item | Detail |
|---|---|
| Certification | ISO/IEC 27001:2022 |
| Certificate number | 304212019 |
| Certified by | Citation ISO Certification Ltd |
| Valid until | 13 June 2029 |
Available on request
- ISO 27001 certificate
- Information Security Policy
- Data Protection Policy
- MSA Schedule 1: Data Protection
- Solution architecture
- Device data sheets
- Sub-processor list
Questions from IT, security and facilities teams
No. Sensors use LoRaWAN radio to reach our gateways, and gateways use cellular by default. Only if you choose Ethernet backhaul does a gateway use your network, and then only for outbound connections.
No. They report presence, counts and room conditions. They don’t capture images, video or audio, and they don’t collect names, badge IDs or device identifiers.
No. All connections are outbound. No inbound ports, port forwarding or VPN are needed.
With Amazon Web Services in Ireland (EU). It stays in the UK and EEA unless you agree otherwise in writing.
You are. OpenSensors is the processor, and acts only on your documented instructions.
With the default cellular option, your office sensor network needs very little from you: a security review and, if you want it, SSO set-up in your identity provider. We supply, install and monitor the devices.
Your team leads the message, and we provide materials explaining what the sensors measure and what they don’t.
Our operations team is alerted and follows up. Gateway redundancy is designed for each deployment, and we coordinate any repair or replacement with your site contact.
Yes. We are happy to complete your questionnaire or join a call with your reviewers.