Service and operator
This policy applies to Meeting Bell, a conference scheduling service operated by Azabu Insights. Meeting Bell helps authorized organization teams publish profiles and availability, check for scheduling conflicts, and create confirmed meeting invitations. Questions and privacy requests may be sent to info@azabuinsights.com.
Information we collect
- Account and contact information, including names and email addresses.
- Organization workspaces, team profiles, photos, availability, roles, and permissions.
- Meeting requests, guest details, confirmation status, and event details.
- For connected Google accounts: the verified account email and OAuth authorization tokens. During calendar imports and conflict checks, we receive event identifiers, titles, start and end times, busy or free status, and private Meeting Bell metadata from the connected account’s primary calendar, or its accessible calendars when the user chooses Show all Gcalendars and grants the additional read permissions. We use these fields to identify Meeting Bell events and derive busy time periods. Imported availability records contain time periods rather than unrelated appointment titles or descriptions.
- Basic technical and security records needed to operate and protect the service.
How we use information
- Operate organization workspaces and show authorized conference content.
- Offer meeting times, prevent scheduling conflicts, and confirm meetings.
- Create confirmed Meeting Bell events and send calendar invitations.
- Provide administration, security, support, and product maintenance.
Google Calendar permissions and data
Connecting Google Calendar is optional. Google account identity permissions let us verify the email address of the account you select. Calendar permissions let us provide the following functions:
- Free/busy availability: allows access to calendar availability. The current calendar import and conflict-check implementation also reads selected event fields using the owned-events permission described below. It does not request unrelated appointment descriptions, attendees, locations, or notes.
- Events on calendars you own: to read the selected primary-calendar event fields described above, check conflicts, recognize existing Meeting Bell events, and create or remove Meeting Bell’s temporary availability blocks. Direct creation of confirmed meeting events requires explicit opt-in for the executive. Email invitations remain available without enabling direct calendar writing.
Show all Gcalendars optionally requests read-only access to the calendar list and events on accessible calendars. Additional calendars are read for busy periods; this does not authorize writing to them. Imported records retain time periods, not unrelated appointment details.
Meeting Bell stores the connected Google account email, OAuth authorization tokens, imported busy time periods, and identifiers and time periods for its own calendar blocks. Identifiers and links for Meeting Bell events may also be retained to operate and support bookings. Calendar reads and writes are limited by the connected user’s Google permissions; Meeting Bell does not need access to Gmail or Google Drive for these calendar functions.
Limited use of Google user data
Meeting Bell uses information received from Google APIs only to provide or improve the Calendar features the user sees and requests. We do not sell Google user data, use it for personalized advertising, use it to determine creditworthiness, or use it to train general-purpose artificial intelligence models. Humans do not read Google Calendar data except when necessary for security, legal compliance, or user-requested support and only when permitted by applicable law.
Meeting Bell’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Data storage, retention, and deletion
Workspace data and Calendar connections are scoped to the organization that created them. Google authorization tokens are retained only while the Calendar connection is active and needed to provide Calendar functions. When an authorized administrator uses Disconnect & Revoke Access, Meeting Bell asks Google to revoke the token and deletes the stored token and connected-account setting. Users may also revoke access through their Google Account.
Disconnecting does not automatically clear imported busy time periods. An authorized administrator can explicitly clear those imported periods in Meeting Bell. Disconnecting also does not automatically delete temporary Google Calendar blocks or confirmed events; administrators can remove Meeting Bell blocks using the calendar controls before disconnecting. Confirmed meeting records and the Google events already created may remain so participants retain an accurate meeting history. A user or organization can request deletion of personal information or its Meeting Bell workspace by emailing info@azabuinsights.com. We delete or de-identify data when it is no longer reasonably needed to provide the service, meet legal obligations, resolve disputes, or protect the service.
Data sharing and transfers
We do not sell personal information or Google user data. We disclose data only:
- to hosting, database, storage, and security providers acting for Azabu Insights and needed to operate Meeting Bell;
- to Google when a user directs Meeting Bell to check availability or create a confirmed event;
- when a user or organization asks us to share it;
- when required by law or reasonably necessary to protect users, organizations, Azabu Insights, or the service.
Service providers may process only the data needed to perform their contracted services and must protect it appropriately.
Your controls and rights
Users can decline Google Calendar access without connecting an account. An authorized administrator can replace or disconnect a connected account on Meeting Bell’s Calendar Setup page. Users can also remove access from their Google Account’s third-party access settings. To request access, correction, export, restriction, or deletion of personal information, email info@azabuinsights.com.
Security
We use reasonable administrative and technical safeguards designed to protect information, including access controls, organization-level separation, secure transport, and restricted administrative access. No online system can promise absolute security. If we learn of a security incident that requires notice, we will notify affected users or organizations as required by applicable law.
Policy changes
We may update this policy as Meeting Bell changes. We will post the revised policy and its updated date on this page. Material changes affecting Google user data will be reflected here before the changed use begins.