SNAPguard

Summarygenerating…

Overview

Hospitality venues have specific Wi-Fi risks: public connections, high device churn, legal obligations around acceptable use and data logging. SNAPguard handles the filtering, logging, and delivery so you don't have to hire a network engineer per venue.

How it works

SNAPguard sits between the captive portal and the internet: it filters inappropriate content per UK/EU hospitality guidelines, logs session metadata for the required retention period, and manages secure delivery of splash and control traffic to the Stampede cloud.

Core concepts

Content filtering

blocks categories inappropriate for a guest environment.

Session logging

regulator-aligned metadata retention per jurisdiction.

Secure delivery

encrypted control-plane for splash updates and guest data.

Usage & workflows

On every Stampede Guest Wi-Fi deployment — included by default.

Example

A multi-venue hospitality group passes a licensing-authority Wi-Fi audit without additional tooling thanks to SNAPguard's built-in logging.

Note

Where to find it

Configure this in the Stampede admin app under Admin → Wi-Fi. Permissions are role-gated — contact your account owner to request access if you don't see it.

Tip

API reference

The Stampede API exposes guest, booking, and campaign data programmatically. See developer.stampede.ai for authentication, base URL, rate limits, and endpoint reference.

Note

Need help?

Contact support via the Stampede admin app or your account manager. The knowledge base at help.stampede.ai has guided walkthroughs for common tasks.

Want to see it live?

Book a 20-minute walkthrough and we'll show you the feature in your own admin.

Book a demo