Written for your IT review.
Before a single sensor goes on a wall, your security and data-protection colleagues will ask where the data lives, what personal data is involved, and how the network works. This page is the answer sheet - forward it as it stands, and send us your security questionnaire for anything it doesn't cover.
What we hold, and where.
The design principle: measure the home, not the household. Sensor readings are environmental - temperature and humidity against a property record, never a named resident, and the core monitoring needs no personal data at all. Two optional workflows do carry resident data, and only what your team enters: vulnerability flags used to prioritise cases (a child under five, a respiratory condition), and contact details plus message history where you switch on resident updates. Both sit under the Data Processing Agreement with you as controller - and you can run MouldWatch without either.
- Sensor readings
- Tied to a property, never a named resident
- Resident personal data
- None in core monitoring - optional vulnerability flags and resident updates hold only what your team enters, under the DPA
- Staff personal data
- Names and work contact details of platform users only
- Platform hosting
- Amazon Web Services, Sydney region
- Transfer safeguards
- UK International Data Transfer Addendum + standard contractual clauses
- Retention
- Set by you as controller, under the DPA
- Export
- CSV of any date range, any time - your data leaves with you
- Website analytics
- Cookieless (Plausible), no cross-site tracking
For your stock, the housing association or council is the data controller and TetherHQ Limited is the processor, under a written Data Processing Agreement that forms part of the Managed Services Agreement. The DPA and full sub-processor list are available on request.
How readings get from a bedroom wall to your dashboard.
What is the radio network?
LoRaWAN - the low-power, long-range standard used across UK smart-city and utility deployments. Traffic is encrypted end to end with AES-128, which is built into the LoRaWAN specification itself. Sensors never touch a resident's Wi-Fi or broadband, because they never need to.
Does it work with our existing LoRaWAN network?
Yes. MouldWatch sensors run on shared public LoRaWAN networks, including community networks such as The Things Network. If your authority already operates gateways, we deploy onto that coverage rather than building a parallel network - and any gateway we add strengthens the shared coverage.
What is the gateway, physically?
A small unit mounted externally on a gable end, roof, or communal building - installed by an electrician in around half a day. It draws roughly 6 watts (about the cost of a router to run) and connects over wired power with a SIM-backed connection where needed. Communal and public buildings need no tenant permission.
What happens if a sensor goes quiet?
Sensors are monitored continuously for connectivity, signal quality, and battery health. If one stops transmitting for more than 48 hours we diagnose remotely and coordinate replacement. Batteries are replaceable, and a 2-year warranty covers early failures.
Fits your stack. Leaves cleanly.
How does data get into our systems?
Three ways, all standard: a REST API and webhooks for event-driven integration (an alert can raise a job in your housing management system without anyone re-keying it), MQTT for authorities already running IoT stacks, and CSV export for everything else.
Can alerts create jobs in our repairs system?
Yes - that is the intended pattern. An alert fires a webhook carrying the property, the risk state, and the statutory clock; your system raises the job. The alert history keeps its own audit trail of who was notified and what was done, independent of your job system.
Who are the contracting parties?
You contract with TetherHQ Limited, with Quidos Group delivering field operations under the same agreement. A written Data Processing Agreement forms part of the Managed Services Agreement; you are the data controller for your stock, we are the processor.
No exit lock-in by design: your sensor history exports as CSV across any date range, so the record you build with MouldWatch stays yours - including through a future competitive procurement.
Send the questionnaire. We answer in full, in writing.
Every deployment starts with your information-governance review, and we treat the questionnaire as part of the job - not an obstacle to it. Direct technical questions welcome.