This page is a practical summary for venues. It is not legal advice. The binding terms are in our Terms of Service and Data Processing Agreement. How we handle personal data ourselves is described in our Privacy Policy.
1. Who is responsible for what
| Data | Controller | Processor |
|---|---|---|
| Guest data collected through your WiFi login page: contact details, visits, consent, feedback | You, the venue | Us (under the DPA) |
| Your staff's admin panel accounts | You | Us |
| Your account, billing and support data | Us | — |
As controller, you decide what your login page asks for and how you use the data, for example for marketing. We process it only on your instructions: your settings, and the features you use. The Data Processing Agreement, which meets Article 28 of the UK GDPR, is part of our contract and needs no separate signature. A signed copy is available on request.
2. What the platform does for you
Consent and transparency
- Guests must accept your WiFi terms before they go online, and the time of acceptance is recorded. You write the terms in the editor; a default text is provided.
- Marketing consent is a separate, unticked box, so accepting the terms never counts as agreeing to marketing. The time consent was given, and any later withdrawal, are recorded.
- Bulk campaigns and automated marketing emails and texts go only to guests who gave marketing consent and have not withdrawn it.
- Marketing emails include an unsubscribe link that takes effect immediately.
- Social logins request only basic profile permissions, and provider access tokens are not stored.
Guest rights
- Every WiFi page links to a privacy notice that names your business as controller, using the details under Settings → Data protection, and to "Your data", where guests can request deletion of their data, confirmed by an email link.
- From the admin panel you can delete an individual guest, and export your guest list as a CSV file. Each export is recorded in an audit log.
- We help with requests that cannot be handled in the panel, such as access requests or guests who logged in without an email address. Send them to support@yumeeservices.com.
Minimisation and retention
- You choose which fields the login page asks for. Ask only for what you will actually use.
- Nothing about a new guest, including answers to your own questions, is saved until the guest accepts your terms. A guest who leaves before that leaves no record.
- Guest records are deleted automatically 24 months after the guest's last visit. Records used to let a device online are removed when the session ends.
Security and location
- Data is stored in the European Union (Google Cloud, Netherlands and Belgium), and emails are sent from the United Kingdom (AWS, London).
- Data is encrypted in transit and at rest. WiFi controller passwords are also encrypted with AES-256-GCM.
- Admin access is role-based and is checked on our servers for every request. Database rules deny access by default, and logins are rate-limited.
- We notify you of a personal data breach affecting your data within 48 hours of becoming aware of it.
3. Sub-processors
You give general authorisation for the following providers. We notify account administrators by email at least 30 days before adding or replacing one.
| Sub-processor | Purpose | Location |
|---|---|---|
| Google Cloud / Firebase (Google Ireland Ltd) | Hosting, database, application logic | EU (Netherlands, Belgium) |
| Amazon Web Services: Simple Email Service | Transactional and marketing email | UK (London) |
| Twilio Inc. | Login codes by SMS or WhatsApp | United States* |
| Anthropic PBC | AI feedback summaries and reply suggestions, only when your staff use them | United States* |
* Transfers are covered by the UK International Data Transfer Addendum or the UK Extension to the EU–US Data Privacy Framework.
Not our sub-processors: services you connect or run. These include your WiFi controller, your own SMS account for marketing texts, CRM and email-marketing tools (Mailchimp, Klaviyo, HubSpot), advertising platforms (Meta, Snapchat) and webhooks. We send data to them on your instruction, and you need your own agreements with them.
4. Your checklist as a venue
- Say who you are. Enter your business name, address and a contact email for data requests under Settings → Data protection, so that guests can see who the controller is.
- Review your WiFi terms. Make sure they name your business, explain what you collect and why, how long you keep it, and link to your own privacy notice.
- Market only with consent. Send marketing emails and texts only to guests who ticked the marketing box (PECR). Honour opt-outs. Marketing texts sent from a phone number end with "Reply STOP to opt out": add the incoming-message address shown in the SMS settings to your Twilio number, so that STOP replies withdraw consent automatically.
- Treat feedback requests carefully. A feedback email that also promotes offers counts as marketing. Keep feedback requests purely about the visit, or send them only to consenting guests.
- Keep reviews honest. Follow Google's and other platforms' review policies and the Digital Markets, Competition and Consumers Act 2024. Do not pay or reward people for reviews, and do not present reviews in a misleading way.
- Check your integrations. Before connecting a CRM, an advertising platform or a webhook, check that it has a lawful basis, that it is covered by your privacy notice, and that you have an agreement with the provider.
- Answer requests on time. Guests can ask for access, correction or deletion; you must answer within one month. Use the panel's tools, or forward the request to us.
- Pay the ICO data protection fee. Most UK organisations that process personal data must pay it (ico.org.uk).
- Consider a DPIA if you combine WiFi data with other sources, or use it for profiling at scale.
5. Questions
For data protection questions, a signed copy of the DPA, or help with a guest's request, contact support@yumeeservices.com.