Availo

Availo lets visitors book meetings with you directly on your WordPress site.

• Event types — define meetings like “30-min Intro Call” with duration, location, buffers, minimum notice, rolling booking window, and a daily cap.
• Availability schedules — weekly working hours per host with date-specific overrides, all timezone- and DST-aware.
• Booking flow — a fast, responsive three-pane widget: pick a day, pick a time (shown in the invitee’s own time zone), enter details, done.
• Custom questions — collect extra information from invitees at booking time.
• Email notifications — confirmation, cancellation, and reschedule emails with calendar (.ics) attachments for both invitee and host.
• Self-service changes — invitees cancel or reschedule via a secure tokenized link. No account needed.
• Embed anywhere — Gutenberg block, [availo] shortcode (inline or popup button), or auto-generated booking pages at /schedule/{host}/{event}/.
• Bookings dashboard — filterable admin list of all bookings with one-click cancellation.
• Google Calendar — connect a host’s Google account so busy events block booking slots automatically, and new bookings are added to the chosen calendar.
• Google Meet — optionally generate a Meet link for each booking; the link becomes the meeting location in confirmation emails and calendar invites.

Availo stores all booking data in your own WordPress database. There are no Availo accounts and no tracking. The only external service is Google, and only if you choose to connect a Google Calendar — see External services below.

External services

Availo works entirely on your own site by default. Nothing is sent anywhere unless you explicitly connect a Google account under Availo → Integrations.

Google Calendar API (optional, off by default)

Used to keep a host’s availability in sync with their Google Calendar and, when enabled per event type, to create Google Meet links.

You supply your own Google OAuth client (created by you in the Google Cloud Console), so the connection is between your site and your own Google project. Availo does not proxy this traffic through any Availo or third-party server, and no credentials are bundled with the plugin.

Requests are sent to Google (accounts.google.com, oauth2.googleapis.com, www.googleapis.com) only when a host connects an account, when availability is calculated, and when a booking is created, rescheduled, or cancelled. Data sent:

• When checking availability: the time range being queried and the IDs of the calendars you selected. Availo reads only free/busy times, not event details.
• When a booking is added to your calendar: the event title, description, start and end times, and the email addresses of the host and the invitee, so Google can send the invitation.
• During connection: the OAuth authorisation code and your client ID and secret, exchanged for access tokens that are stored in your WordPress database.

Because the OAuth client belongs to you, Google may show an “unverified app” notice the first time you connect. You can continue past it, or verify the project in the Google Cloud Console.

Google’s terms and privacy policy apply to this data:

• Google Terms of Service: https://policies.google.com/terms
• Google Privacy Policy: https://policies.google.com/privacy
• Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy

Disconnecting a Google account under Availo → Integrations deletes the stored tokens and cached calendar list from your database.