Network Owner Removal

Our commitment

The WiFi Map community map is contributed by users. Our Community Guidelines restrict it to venue and public networks whose operators offer them to customers or the public, and every contributor must attest that they have permission to share what they submit.

Moderation is imperfect. Somebody may have listed your network without your consent, or listed it correctly and then you changed your mind. Either way, the answer is the same: we take it down. You do not need to be a lawyer, quote a statute, or explain your reasoning.

1 Who Can Request Removal

Any of the following:

• The network owner — the person or entity that pays for the connection or operates the access point.
• An authorised representative — an IT administrator, facilities manager, franchise operator, or anyone acting for the operator.
• The occupier of the premises, where the network is at a private residence.
• A legal representative acting on behalf of any of the above.

We ask you to confirm your relationship to the network. We do not ask for identity documents, incorporation certificates, or utility bills. A statement made in good faith is enough — the cost of removing a legitimate entry in error is far lower than the cost of leaving a wrongly-listed network up.

2 What We Can Remove

We can also remove an entry's free-text notes while leaving the rest, if the problem is something a contributor wrote rather than the listing itself.

3 Removal Request

Fill this in and it will compose an email in your mail app, pre-filled and addressed to us. Nothing is transmitted from this page — it builds a message you send yourself, so no data reaches us until you press send in your own mail client.

4 What Happens Next

1. We acknowledge within 24 hours. You get a reply confirming we have your request and what we are going to do.
2. We locate the entry. Usually from the SSID and city alone. If we cannot find it, we come back to you rather than closing the request.
3. We remove it, within 72 hours. The record is deleted from our database and any stored credential is destroyed.
4. The map rebuilds. Tiles are regenerated and replaced atomically, so the entry disappears from users' devices rather than surviving in a cached tile. This completes within hours of the deletion.
5. We blocklist the network. See §5.
6. We confirm to you that it is done, and we act against the contributor where the contribution breached our rules.

5 Preventing Re-listing

A removal that another user can undo the next day is not a removal. So when we take an entry down at an owner's request, we also:

• Blocklist the network against future contributions. A subsequent submission matching it is rejected at the server rather than entering the moderation queue.
• Do not restore it on the basis of votes, corroboration or a later contribution.
• Record the takedown so that if you contact us again about the same network, we can see the history.

If you later change your mind and would like your venue mapped — many venues do, because it brings customers in — email us and we will lift the block.

Reducing your exposure generally

Independent of this map, if you operate a venue network and are concerned about credential sharing:

• Separate your guest network from your internal and POS networks, on different VLANs.
• Rotate the guest passphrase on a schedule, or use a captive portal with per-session access.
• Enable client isolation on the guest SSID so connected devices cannot see each other.
• Do not use the same passphrase for guest and staff access.

These are good practice regardless of whether your network ever appears in a directory like this one.

6 Other Kinds of Takedown

7 Contact

Publisher

Epsilon Developers

Operated by

Satyam Kushwaha & Anurag Mahajan

Country

India

Takedown contact

contact@epsilondevelopers.xyz

Acknowledgement

Within 24 hours

Removal completed

Within 72 hours