GDPR-Compliant Data Capture

Summarygenerating…

Overview

Capturing guest data legally is the difference between a real marketing asset and a compliance liability. The login flow follows GDPR best practice: clear language on what data is collected, explicit opt-in for marketing, and an audit trail per guest.

How it works

Consent checkboxes are unticked by default; the wording is configured per venue; the moment a guest opts in (or out), the timestamped consent state is logged to their profile. Withdrawing consent via an unsubscribe link writes back to the same record.

Core concepts

Explicit opt-in

active tick required, never pre-ticked.

Consent record

timestamped, auditable, per-guest log of marketing permission.

Data minimisation

only asking for fields you'll actually use.

Usage & workflows

Every venue where GDPR applies — effectively every venue in the UK and EU.

Example

A group operator passes a DPO audit with the Stampede consent audit trail as evidence, avoiding the rework demanded by other vendors.

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