Privacy
Privacy, in plain language
What is stored, where, for whom, and the four cookies. If something here is unclear, that is our mistake: write and we will fix the page.
Who we are
AttendBeacon is made and run by Power Pete. When you register for an event, the organiser of that event decides what is asked and what it is used for. We keep it for them, use it for nothing else and sell it to nobody.
Where it is kept
In Microsoft Azure, in the EU. The database runs in the Sweden Central region; the app and the service that answers it run in West Europe, in the Netherlands.
What is stored about an attendee
Only what the event needs and what the organiser chose to ask:
- Your name and email address, because the ticket is for a person and is sent to them
- Your company and job title, when the event asks for them
- Your answers to the event's own questions, such as dietary requirements or consent to appear in photos
- Your ticket and order, and for a paid ticket whether it was paid, as your payment provider reports it
- When your ticket was scanned at each door, in and out
- The sessions you starred for your own agenda, and the language you registered in
- Your points, and your answers to session feedback and surveys
Paying for a ticket
You pay on the page of the organiser's own Mollie or Stripe account, so your card or bank details go to the provider and never to AttendBeacon. We keep the payment's reference and its status.
What others can see
The leaderboard shows your first name and the first letter of your last name, such as "Anna B.", and you can leave it and keep your points. Room screens show arrivals as counts, never names. The organiser sees feedback and survey results per question, without names.
Signing in without a password
Attendees have no passwords. To see your ticket on another phone, you ask for a six-digit code, which is sent to the email address on your ticket and works for fifteen minutes.
After that, a cookie keeps you signed in on that phone for sixty days, renewed while you use the app. Signing out removes it.
Organisers
Organisers sign in to the workspace with their Microsoft account, or another provider the deployment offers. We keep their name, email address, the workspaces they belong to with their role, and a log of the changes they make, so a workspace can see who changed what.
We send the emails the event needs: the confirmation with your ticket, and a sign-in code when you ask for one. No newsletters and nothing for marketing.
At the door
To keep checking people in when the venue's network fails, the scanner holds the event's ticket list in the memory of the crew's phone while the scanner is open. It is gone when the page is closed.
On your phone
The attendee app keeps a copy of the event, the agenda and your ticket on the phone, so they still open without a network. It remembers the language you chose in the browser's own storage. Removing the app or clearing the site's data removes all of it.
Cookies
Only functional ones: to keep you signed in, and to remember your language and your choice of light or dark.
| Cookie | What it is for | How long |
|---|---|---|
ab-attendee | Keeps an attendee signed in to the event app on that phone | 60 days, renewed while used |
| The workspace sign-in | Keeps an organiser signed in to the workspace, with the short-lived ones the Microsoft sign-in sets while it happens | 8 hours, renewed while used |
ab-lang | The language you picked on this site | One year |
ab-theme | Light or dark, when you chose one on this site | One year |
No analytics, no advertising, no tracking pixels, and no cookies from anybody else.
This website
This site has no analytics. Its fonts, stylesheet and script come from the same address as the page, so reading it tells no other company that you did.
Seeing, correcting or removing your data
Ask the organiser of your event, or write to us. We answer within a month, and until the workspace has a button for every request, we do it by hand.
Contact
Questions about this page or about your data: peter@powerpete.com