Guest Misuse of Your Wi-Fi: A Short Acceptable-Use Clause

The network in your listing is yours, and so is the liability that travels with it. Four sentences in the house rules do most of the work.

Last updated: October 24, 2026

Most house rules mention Wi-Fi once, to give the password. That's the one line that carries no protection at all. A usable clause is four sentences long: what the network covers, what guests may not do with it, what you'll do if they do, and how fast they have to tell you something looks wrong. Everything else is length.

Key Takeaways

• Four sentences, four jobs. Scope, prohibited conduct, your response, and the guest's duty to report.
• Write it to be read. A guest who can't follow the clause in one pass will ignore it, and an ignored clause is worse than none.
• Publish it three times. House rules, pre-arrival message, and a card beside the router.
• Suspend first, discuss second. The response has to be reversible and documented, not a confrontation at the door.
• Keep a dated record. Without dates and copies, the clause describes an intention rather than an incident.

What the clause needs to say

Start with scope. One sentence should say which network is covered, that it's for guest devices only, and that credentials aren't to be shared outside the party. That single sentence does more work than any warning about consequences, because it removes the most common defence: I thought it was fine to give the password to the people in the flat next door.

Then conduct. Not a list of crimes — a short statement that the network may not be used for unlawful activity, for resale, or to run a business from the property. Keep it to behaviours a reasonable guest could recognise in themselves. Long enumerations invite arguments about the ones you left out.

Then your response. Say what you'll do if the clause is broken: access suspended, and the booking may be ended under the platform's own terms. Being specific here matters, because a response you didn't announce looks arbitrary when you apply it.

Then the reporting duty. Guests should tell you within a stated window if the connection behaves strangely, if devices they don't recognise appear, or if someone asks them for the network details. This is the sentence hosts most often leave out, and it's the one that turns a silent problem into a same-day one.

A clause is not a legal shield in every jurisdiction. What it buys you is a stated expectation, accepted before arrival, which is useful in a conversation and occasionally useful in a dispute. Whether it binds anyone, and what you may lawfully do about a breach, depends on local rules. Check with a local adviser before you rely on it.

Where to put it

Three surfaces, and all three matter for different reasons.

The house rules field on each channel, because that's the version the guest accepts when they book. Keep the short form here — the four sentences, no annexes. If a channel caps the character count, cut adjectives, not sentences.

The pre-arrival message, because that's the version a guest actually reads. Repeat the clause in the same words, and put the reporting duty at the end where it's the last thing they see before arriving.

A card beside the router, because that's where the network physically is. This one can be plainer: the network name, the rule about sharing, and a number to message. It's the only copy that gets read at the moment it's needed.

Consistency is the whole point. A clause that appears in one place and not another is arguable, and a clause that appears in three slightly different versions is worse than one version, because the differences become the conversation.

localsbnb.com keeps your units and the four connected channels — Airbnb, Booking.com, Agoda and Trip.com — in one calendar, so when the wording changes you can see which listings are which before you start editing text. What the clause says is your call. Finding every listing that needs it shouldn't be.

What to do when it happens

Assume it will happen at eleven at night, and decide the sequence now rather than then.

Suspend the guest network, not the whole connection. This is the reason to run guest devices on a separate network from the start: it gives you a response that's proportionate and reversible, and it keeps your own access to the router while you work out what's going on.

Then send one written message. Describe the observation, not the accusation: what you saw, when you saw it, what you've done, and what happens next. "The guest network has been paused while I check something" is a sentence that survives being read by a platform, a guest and, later, an insurer. "Someone was downloading illegal material" is not.

Never investigate it yourself. If what you're seeing suggests unlawful use, stop, preserve what you have, and take advice — from the platform, from a local adviser, or from the authority that handles it locally. Reading a guest's traffic to find out more is its own problem, and in some places a bigger one than the original.

If the guest disputes it, don't argue at the door. Repeat the clause, name the response, and move the disagreement into writing where it can be read later by someone who wasn't there.

One more thing to decide in advance: what ends the suspension. A time, or a condition, or a person who can authorise restoring access. An indefinite suspension with no owner is how a small incident becomes a refund request.

Records that protect you

Keep four things, and keep them together.

The version of the clause the guest accepted, with the date you published it. Not the current version — the version that was live when they booked. If you've changed the wording since, that difference will come up, and having both makes it a versioning question rather than a credibility one.

A short extract from the router log covering the window, with timestamps. An extract, not an archive: take what's relevant, note when you took it, and don't keep more than you need. Retention limits differ by jurisdiction, and holding too much is its own exposure. Confirm what applies where you operate.

Copies of the messages you sent and the replies you received, in order. This is usually the most persuasive part of the file, because it shows a sequence rather than a position.

A single line of your own notes: what happened, what you did, when access was restored, and who decided. Write it the same day, while the details are still exact.

Then put a review date on the clause itself. Once a year is enough, and it's the moment to check that the house rules field, the message template and the card by the router still say the same thing.

FAQ

Can I just switch the Wi-Fi off if a guest breaks the rule?

If your clause says access may be suspended, that's the response you announced, and it's proportionate for a network problem. What you shouldn't do is cut something a guest needs for safety or accessibility, and you should say when access comes back. Check what local rules allow before you rely on suspension as a remedy.

Will the platform enforce my clause for me?

Partly, and not predictably. Platforms enforce their own policies, and a clear house rule makes it easier for a support agent to see your side. Your clause is a term between you and the guest; it isn't a policy the platform has agreed to police.

Do I need to keep guest ID to use the network?

That depends on local rules, and in some places guest registration is a separate duty from anything to do with Wi-Fi. Don't add an ID requirement to a network clause to solve a registration question. Check with a local adviser and keep the two obligations apart.

The clause is a small piece of writing that decides how a bad night goes. Four sentences, three surfaces, one dated record. When the wording has to change across several listings at once, localsbnb.com is where the units and the channels are already listed in one place, so you can see what needs the edit before you start.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Whether an acceptable-use clause is enforceable, what you may monitor and how long you may keep a log all depend on where you operate. Check with a local adviser, and confirm the current terms of each platform you use, before you act on a breach.