Noise monitoring and what you may legitimately measure in a rented space
Measuring how loud a room is and recording what is said in it are entirely different things, legally and ethically. One is defensible; the other can end a listing.
Noise complaints are the most common serious problem in short-let hospitality. They damage relationships with neighbours, they attract the attention of local authorities, and in cities with licensing regimes they can cost a host their permission to let at all.
Noise monitoring addresses it, and it sits closer to the legal boundary than anything else discussed in this category. Doing it properly is entirely possible. Doing it carelessly can breach privacy law, violate platform rules and end a listing.
The distinction everything depends on
There is a fundamental difference between measuring how loud a space is and recording what is being said in it.
A decibel meter reports a sound pressure level — a number. It does not capture audio, cannot be played back, and reveals nothing about the content of a conversation. Properly designed devices for this purpose process sound locally and transmit only the level, with no audio leaving the device at any point.
A microphone that records, streams or stores audio is an entirely different proposition. In most of Europe, recording conversations without the consent of the participants is unlawful, and doing it inside private accommodation that someone has rented is a serious matter. It is also explicitly prohibited by the major booking platforms.
Never record audio in guest accommodation. Not in bedrooms, not in living areas, not “just in case”, not with a device that has recording capability disabled in software. Use devices that measure decibel level only and cannot record. This is a legal line in most jurisdictions, an absolute platform rule, and an ethical one. Devices marketed for this purpose should state explicitly that they capture no audio — if a supplier cannot confirm that plainly, choose another supplier.
What decibel monitoring actually tells you
Less than people expect, and enough to be useful.
It tells you that a space is louder than a threshold, for how long, and at what time. It does not tell you how many people are present, what they are doing, or whether the noise is a party or a television at an inconsiderate volume. Those inferences are yours to draw, and they are frequently wrong.
The practical value is in the pattern. Sustained elevated levels late at night, particularly rising over an hour or two, is the signature that precedes most complaints. A single spike is somebody dropping something.
Setting thresholds sensibly
The commonest mistake is setting a level that generates alerts for normal occupancy, which trains you to ignore them.
Rather than starting from a number, measure your own property empty and then normally occupied for a week, and set the threshold above ordinary use. A flat on a main road has a completely different baseline from a rural cottage, and a threshold copied from an article will be wrong for both.
Then apply time context, because the same level means different things at eight in the evening and one in the morning. And require duration: a threshold exceeded continuously for ten or fifteen minutes is meaningful, whereas an instantaneous peak is not.
Responding well
The response determines whether this helps or makes things worse.
Message first, and politely. A friendly note — noise levels seem high, please be mindful of neighbours, quiet hours are from eleven — resolves the large majority of cases. Most guests are not trying to cause a problem and respond well to a reminder.
Escalate slowly. A second message, then a phone call, then a visit if you or a local contact can attend. Involving the platform or authorities is a last step.
Do not accuse. You know a level was exceeded. You do not know what happened. A message asserting that a guest is holding a party, when they were watching a film loudly, produces an entirely justified complaint about you.
Never use it as surveillance. Checking levels out of curiosity, or mentioning to a guest that you noticed they were up late, is exactly the behaviour that makes guests hostile to monitoring in general.
Disclosure, in detail
Disclosure is not a formality and the standard is higher than many hosts realise.
Disclose before booking, in the listing itself, so a guest can decline to book. Telling someone on arrival that they are being monitored is not consent, it is a fait accompli.
Say what it measures. “A noise level sensor in the living room that measures volume only and records no audio” is clear, honest and reassuring. “Monitoring devices” is not.
Say where it is, and place it visibly. A device a guest can see and identify is a device they will not worry about.
Never in bedrooms or bathrooms. Even a level-only sensor. These are spaces where the expectation of privacy is absolute, and platform rules generally prohibit any device there regardless of function.
Check platform rules currently, because they have tightened over time and differ between platforms. What was acceptable three years ago may not be.
Data protection, briefly
In the EU and UK, a decibel level associated with a specific booking is arguably personal data about identifiable guests, so a few practices are worth adopting regardless of how you interpret the law.
Collect only what you need — level, not audio. Keep it briefly; there is no reason to retain noise data from two years ago, and a short retention period is easier to defend than a long one. Restrict access to yourself and any co-host who needs it. Be able to explain the purpose in a sentence: preventing noise disturbance to neighbours and protecting the property.
Neighbours and licensing
In an increasing number of cities, repeated noise complaints feed directly into a licensing or registration decision, and in some places a small number of substantiated complaints is enough to lose permission to let. That changes the calculation: noise monitoring is not only about protecting a deposit, it is about protecting the business itself.
It also means the record matters. Being able to show that levels were within normal bounds on a night a complaint was made is genuinely useful, and it is one of the few situations where retrospective data protects the host rather than the guest.
What else helps, often more
Monitoring detects; several cheaper measures prevent.
Be explicit in the listing. Clear house rules on quiet hours, maximum occupancy and no parties, stated before booking, deter the bookings you do not want. This is the single most effective intervention available.
Set expectations at booking. A short message confirming quiet hours and that neighbours live close by does more than any sensor.
Restrict the booking profile. Minimum-stay requirements, and declining one-night local bookings on weekends, remove a large share of party risk in the properties where it is a problem.
Talk to the neighbours. A neighbour with your phone number who knows you respond is worth more than any technology, and their goodwill is the thing actually at risk.
A defensible setup
- House rules and expectations first, stated in the listing and confirmed at booking.
- A decibel-only sensor in the main living area, from a supplier who confirms in writing that it captures no audio.
- Nothing in bedrooms or bathrooms.
- Disclosed in the listing before booking, with what it measures and where it is.
- Thresholds set from your own week of baseline data, with time context and a duration requirement.
- A polite-message-first response ladder, and a local contact who can attend.
Done this way, noise monitoring is uncontroversial with guests, genuinely effective with neighbours, and defensible if anybody asks. Done the other way, it is the fastest route to losing a listing.