B-PASS Privacy Policy
Last updated: 5 October 2026
This policy covers the software running on a B-PASS access panel. For the Bettear website, see our Privacy & Cookie Policy.
A B-PASS panel is installed by a venue. It shows visitors how to join an Auracast™ broadcast — a QR code to scan, or a receiver to tap — and it is operated by the venue, not by Bettear.
Who we are
The B-PASS software is made by Bettear – Accessibility Technologies Development Ltd. (company no. 515665842), 33 Habarzel Street, Tel Aviv 6971049, Israel, together with its subsidiary Bettear Inc., 1430 Broadway RM 1503, New York, NY 10018, United States ("Bettear", "we").
For any question about this policy, write to info@bettear.com.
The panel does not collect information about visitors
People who use a B-PASS panel do not sign in, and the panel does not ask them for anything. It does not collect names, email addresses, location, or any identifier of the phone or receiver used to join a broadcast. Nothing a visitor does at the panel is sent to Bettear.
What the panel keeps on the device
A panel stores the settings a venue administrator enters, on the device itself:
- the addresses of the Bettear CASTER units it controls, and the network settings of the panel;
- the administrator username and password for the panel's own settings screen;
- the identifiers of any admin tags used to generate a new passkey;
- a background image, if the venue uploaded one for branding.
These stay on the panel. A factory reset erases them.
Google Calendar, when a venue connects one
A panel can be connected to a Google Calendar so that it generates a new listening passkey when a meeting begins. A venue administrator sets this up in the panel's settings, and the feature does nothing until they do.
When it is connected, the panel asks Google for read-only access to calendars. It reads the events starting in the next 24 hours, and uses three things from each one:
- the start time, which is what tells the panel when to generate a new passkey;
- the title of the next meeting, shown on the panel's settings screen so an administrator can confirm the right calendar is connected;
- an event identifier, so one meeting cannot generate a passkey twice.
The panel talks to Google directly. Calendar information stays in the panel's memory while it is running: it is never sent to Bettear, never shared with anyone else, and never read by our staff. The only things the panel saves are the authorisation token and the identifier of the calendar you chose, both held on the device itself.
We do not use calendar information for advertising and we do not sell it. Bettear's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Other ways a panel can read a schedule
Instead of signing in to Google, a venue can connect a panel to a calendar using a service account key, or a published calendar address (an .ics link). These are read in the same way and used for the same purpose, and the information is handled exactly as described above.
Disconnecting
A venue can disconnect the calendar at any time in the panel's settings. Where Google sign-in was used, access can also be withdrawn from the Google Account permissions page. Either way the panel stops reading the calendar, and passkeys go back to being generated only by an administrator tap.
Updates to the software
Panel software is updated by the venue from a USB drive, or by its administrator from the settings screen. A panel does not send usage data, diagnostics or analytics to Bettear.
Changes to this policy
We may update this policy from time to time. The date at the top of this page shows when it last changed.