Bookzui Privacy Policy

Last updated: October 5, 2026

Bookzui operates bookzui.com, a scheduling service for hosts and meeting guests. This policy explains how we access, use, store, and share personal information, including information received from Google APIs. Contact Help@bookzui.com for privacy questions and data requests.

Information we collect

Google sign-in provides your Google account identifier, name, email address, and profile picture. We store account information, username, bio, timezone, availability, meeting types, booking questions, settings, social links, and uploaded profile media. For bookings, we collect guest names, email addresses, timezone, chosen meeting times, phone numbers required for phone meetings, and answers to booking questions. We store booking status, calendar event identifiers, meeting links, and selected extra invitees. Hosting infrastructure also processes request information, such as IP addresses, browser information, timestamps, and error logs, for operation, security, and troubleshooting.

Google Calendar access and use

With your authorization, we access your calendar list and selected calendars’ availability to prevent conflicts. When needed for rescheduling, we read event information to distinguish the Bookzui meeting being changed from other busy events. We create, read, update, and delete Bookzui booking events, add attendees, request Google Meet links, and send invitations and calendar updates through Google Calendar. Additional connected Google accounts are used for conflict checking; new events are created on the original account’s primary calendar. Guests see available times, not unrelated event titles or descriptions. We do not store a full copy of your unrelated calendar events.

We store encrypted Google refresh tokens to check availability and manage bookings while you are offline. Access tokens are used for authorized API requests. These credentials are not displayed publicly.

Optional Google Contacts

With separate authorization, we read contact names and email addresses through the Google People API so you can choose extra booking invitees. We do not read Gmail messages or store your entire contacts list in our database. Selected invitees’ details are stored with the booking and sent to Google Calendar for invitations. Contacts are not used for advertising, marketing lists, or unsolicited messages.

Public profiles and guest information

Your public profile displays the information you publish, including name, photo, bio, social links, meeting options, introduction video, and background image. Uploaded profile media uses public storage and can be accessed by its URL. Public pages may be indexed by search engines. Do not publish confidential information in your profile or media.

Guest details and booking answers are shared with the host and included where applicable in the Google event. Calendar information may be visible to attendees or others according to calendar sharing settings. Anyone holding a private booking management link can view, cancel, or reschedule that booking; keep these links private.

Reminders, Calendly imports, and HubSpot

When a host enables email automations, Resend processes recipient email addresses and message content to send transactional reminders and follow-ups. Content may include names, booking details, meeting links, and management links. These messages do not subscribe guests to marketing.

If a host connects HubSpot, we transfer booking guest contact details and meeting records to that host’s CRM and update them for Bookzui cancellations and rescheduling. HubSpot tokens are stored encrypted. This optional integration does not automatically subscribe contacts to marketing.

Calendly imports access scheduling settings, meetings, and guest details to populate Bookzui settings and booking history and prevent conflicts. Calendly access tokens are used during import and not retained. Imported bookings remain private to the host and do not trigger duplicate invitations.

Sharing and service providers

We use Vercel for hosting and public media storage, Turso for database storage, Google for authentication and calendar services, and Resend for enabled email delivery. These providers process information needed for the relevant features. HubSpot receives information when the host connects it. We may disclose information when necessary for legal obligations, security, abuse investigations, or enforcing our terms. A transfer of Google user data following a change in ownership will follow Google’s applicable consent and Limited Use requirements.

Google API Services User Data Policy

Bookzui’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is used only to provide or improve the scheduling and contact-selection features described here. We do not sell Google user data, use it for advertising or credit decisions, or use it to train generalized artificial intelligence or machine-learning models. Humans do not read Google user data except with your affirmative agreement, for necessary security investigations, to comply with applicable law, or as otherwise permitted by Google’s Limited Use requirements. Transfers are limited to authorized user-facing features, security, legal obligations, or an ownership transfer with the required prior consent.

Referral links

If you visit through a host’s referral link, we use a 30-day referral cookie to attribute a new Google signup to that host. We count sharing actions and referral-link visits, which may include repeat visits or automated link previews. We store the referral relationship and show the referring host aggregate signup, profile-completion, and booking counts, not referred users’ names or email addresses. Referral data is retained with account records and can be included in deletion requests. Sharing buttons open your chosen sharing service; Bookzui does not access your contacts for promotional invitations.

Security and cookies

We use HTTPS, encrypted stored integration and Google refresh tokens, hashed session tokens, and authentication for account features. No storage or transmission method is completely secure. Essential session and sign-in cookies authenticate users and protect the authorization process.

Retention and deletion

We retain account settings, profiles, media, and booking history while accounts remain in use unless deletion is requested. Connection credentials remain while connected; disconnecting an additional Google account or HubSpot removes its stored credentials. Delivery and error records are retained for operation and troubleshooting. We do not currently apply automatic age-based deletion to booking history or delivery records.

You can revoke Google authorization in your Google Account connections settings. Revocation stops future authorized access but does not automatically delete information already stored by Bookzui.

For access, export, correction, or deletion requests, email Help@bookzui.com from the account or booking email address. Requests are handled manually, and we may verify identity. We will explain any information that must be retained for legal, security, or dispute-resolution purposes. Deleted information may remain in provider backups until those backups expire under provider retention practices.

Deleting Bookzui data does not automatically remove invitations, emails, or CRM records already delivered to Google, recipients, or a host’s HubSpot account. Manage those records with the relevant service or host. Contact the meeting host about guest information they hold independently.

Changes and contact

We update this policy as the service changes. The date above identifies the latest revision. We provide additional notice or obtain consent when required for material changes in data use. Send questions or privacy requests to Help@bookzui.com.