Cookies

Last updated 10 August 2026.

This page is new, and the Board welcomes corrections: if anything here looks wrong or unclear, please tell us through the contact page and we will put it right.

The short version

If you are reading the public pages of this website, we put nothing on your device at all. No cookies, nothing stored, nothing counted. If you sign in, we use a small number of cookies to keep you signed in and to keep your account safe. If you pay, we leave one short note in the tab on the way back. That is the whole list, and it is all set out below.

We do not track you. There is no analytics on this site, no advertising, and no code from any other company running on these pages. We do not know how many people looked at a page, we do not know where you came from, and we do not build a picture of you.

Why there is no cookie pop-up

You will not be asked to accept or reject cookies here, because there is nothing to decline. The only cookies this site uses are the ones that sign you in and keep your account safe: turn them down and you simply cannot sign in. A box asking you to agree to those would be a question with one real answer, and it would cover the page you came to read. So we have written this page instead. If we ever add anything that counts or follows visitors, that changes, and you would get a proper choice.

What we set when you sign in

• Keeping you signed in. One cookie, named payload-token, set when you sign in successfully or when you set or reset a password. It lasts up to 30 days, or until you sign out, whichever comes first. Your browser will not let any page script read it.
• The extra sign-in step. If your account uses two-step sign-in, one more cookie, pba_mfa, remembers for 12 hours that you passed the check, so you are not asked again on every page.
• Board and staff only. An administrator who is viewing the site as a member to help them with a problem gets a cookie that lasts 30 minutes and cannot be extended. An editor previewing a page before it is published gets one for as long as the preview lasts. Ordinary members never receive either of these.

Things we keep in your browser, which are not cookies

Coming back from paying. When Stripe sends you back to us after a payment, we leave a short note in the tab you are using, recording where we have just sent you. It is there so that if anything goes wrong you get a page with a Continue button on it rather than a page that reloads over and over. It holds no information about you, and the browser throws it away when you close the tab. This is the one thing on this page that does not wait for you to sign in: anybody who arrives on our page after a payment gets it.

The conference check-in scanner. Board members who scan badges at the conference have the last 50 scans kept on their own phone, so that a drop in the venue Wi-Fi does not lose a check-in. It holds attendee names, organizations and badge codes, and it stays on that phone until it is cleared. If you have used the scanner, clearing your browser’s stored data for this website removes it.

The walkthrough in the administration area. Board and committee members who use it have their place in it remembered while they move between pages. The browser throws that away when the tab is closed.

When we send you to another company

• Paying. When you pay membership dues or a conference fee we send you to Stripe’s own secure payment page to enter your card details, and Stripe sends you back to us afterwards. Stripe sets its own cookies on its own site and its privacy policy applies while you are there. The Pass Bureau Association never sees or stores your card number.
• Saving your conference badge. If you choose “Add to Apple Wallet” or “Add to Google Wallet”, that hands you over to Apple or Google, who take it from there. The buttons themselves are stored on this site, so simply looking at the page contacts neither of them.

Turning cookies off

Every browser lets you block or delete cookies, and you are welcome to. Because the only cookies we use are the ones that sign you in, blocking them for this site means you will not be able to get into the members area. The public parts of the site will work exactly as before.

Where the rest of the picture is

This page is only about what we put on your device. What the Association holds about you, who else sees it, and what you can ask us to do about it are all in the privacy notice.

Questions

If anything on this page is unclear, or you would like to talk to somebody about it, please get in touch through the contact page. A member of the Board will answer.