B-PASS Privacy Policy

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 each meeting begins. A venue administrator sets this up in the panel's settings, and the feature does nothing until they do.

The panel signs in with Google's device sign-in: it shows a code, and the administrator approves access on their own phone or computer at google.com/device. The panel asks for one permission only, read-only access to Google Calendar (https://www.googleapis.com/auth/calendar.readonly). It cannot create, change or delete events, and it does not ask for the user's email address, contacts or any other Google data.

Google user data the panel accesses

The list of calendars in the account (each calendar's name, identifier and time zone), read once while the administrator picks which calendar the panel follows.
Events in the chosen calendar that start in the next 24 hours. From each event the panel keeps three fields: its start time, its title and its event identifier. Any other details Google returns with an event, such as its description, location or guest list, are discarded as soon as the reply is read; they are never stored, shown or used.
An authorisation token issued by Google, which lets the panel keep reading the calendar without signing in again.

How the panel uses it

The start time tells the panel when to generate a new passkey for the room.
The title of the next meeting is shown on the panel's password-protected settings screen, so an administrator can confirm the right calendar is connected. Visitors never see it.
The event identifier makes sure one meeting cannot generate a passkey twice.
The calendar list is used only to let the administrator choose a calendar.

Calendar data is used for nothing else. We do not use it for advertising, we do not sell it, we do not use it to train AI or machine-learning models, and no person at Bettear reads it. Bettear's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sharing, transfer and disclosure

None. The panel talks to Google directly, and Google user data never leaves the panel: it is not sent to Bettear or to any server of ours, and it is not shared with, transferred to or disclosed to any third party. The only thing a panel does with it is change the passkey of the Bettear CASTER units in the same room, and nothing from the calendar is sent to them.

Bettear would disclose information only if the law required it, and because the data never reaches us, we have none to disclose.

How the data is protected

All communication with Google uses encrypted HTTPS (TLS) connections.
The authorisation token and the chosen calendar are stored in the B-PASS app's private storage on the panel, which Android keeps out of reach of other apps.
B-PASS panels run as locked kiosks: visitors can only use the join screen, the settings screen is protected by the administrator password, and the panel's USB debugging connection is switched off in normal use.
Because the data stays on the panel, there is no copy on Bettear systems that could be exposed.

Retention and deletion

Event details are held only in the panel's memory, and are never written to its storage. They are replaced every time the panel refreshes the calendar (every five minutes); the identifiers of meetings that have already generated a passkey are kept until the app restarts, so a meeting cannot do it twice. Everything is gone when the app restarts.
The authorisation token and the chosen calendar's name and identifier are kept on the panel until the administrator disconnects the calendar in the panel's settings, or the panel is factory reset. Either one deletes them.
To also withdraw the panel's access on Google's side, the account owner can remove it at any time from the Google Account permissions page. The panel then stops reading the calendar, and passkeys go back to being generated only by an administrator tap.
Bettear keeps no Google user data, so there is nothing for us to retain or delete. For any question, write to info@bettear.com.

Updates to the software

Panel software is updated by the venue from a USB drive, or by its administrator from the settings screen. When an administrator checks for an update, the panel downloads a version file and the update itself from Bettear's update server; it sends nothing about the venue, its visitors or its calendar. 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.