Share availability without sharing your calendar
On this page
Can I offer available times without making Google Calendar public?
Yes. Connect your calendars privately to the scheduling app, then share a booking URL that exposes available times and the appointment you offer. Guests don't need calendar-viewing permission to choose a slot. Leave your calendar's sharing settings alone.
Think of a 30-minute consultation offered between 09:00 and 12:00. Your calendar contains a personal commitment from 10:00 to 10:30, so that interval isn't offered. The visitor can choose another time without learning why you're occupied.
We keep calendar authorisation with the host. If work and personal commitments live apart, combine their availability checks instead of making either calendar public so guests can inspect it themselves.
What will someone see on my booking page?
Visitors see available slots and the event details you've published, including its title and configured location. They don't see the names or contents of existing appointments used to remove busy times. Published information still deserves a review.
| Information | Guest visibility |
|---|---|
| Offered meeting title and description | Visible on the booking page |
| Configured meeting location | Guest-facing meeting information |
| Available start times | Visible in the selected display zone |
| Existing event titles and descriptions | Not exposed through availability |
| Existing event locations and attendee identities | Not supplied to the guest |
| Extra questions you add | Visible in the booking form |
A title such as "Project consultation" belongs on a public page. A location field containing your home address also becomes meeting information, even though the same address inside an existing private calendar event isn't read for conflict checking. Those are different sources of data.
We show what you publish. Hiding private calendar contents won't repair an event description into which you've pasted confidential notes, so preview the appointment before sending its link.
What calendar data does the connection read?
From existing events, Barq Meet reads start/end times, busy/free markings, status, event type and your own accept/decline response. We never read existing event titles, descriptions, locations or other attendees. Your own RSVP affects blocking.
Google's consent screen asks for broader calendar access than that field list might suggest. We need permission to create and update the booking events you arrange here; we write only those events. The consent wording and the fields fetched for conflict checking describe different things.
We also use event status and type to handle canceled events and working-location entries correctly, so a location marker isn't treated as a meeting you must attend. For the booking rules behind a missing or available slot, read how Google Calendar sync treats events.
- The meeting title and description you publish
- Available times after calendar checks
- Your configured meeting location and questions
- Titles and descriptions of current events
- Locations of those existing events
- Other attendees' identities
| Guests receive | Existing calendar details stay out |
|---|---|
| The meeting title and description you publish | Titles and descriptions of current events |
| Available times after calendar checks | Locations of those existing events |
| Your configured meeting location and questions | Other attendees' identities |
Source: the approved calendar field list and public booking behavior, checked 17 Nov 2026. The two columns distinguish your published meeting offer from events already in your calendars.
Is hiding an event enough to restrict who can book?
No. Enabling Secret event under Booking page removes the event from the public profile, but the direct URL still grants access. A forwarded address can reach someone you didn't invite. Treat the URL as shareable.
A single-use link limits reuse by closing after a successful booking. A one-off offer limits the available choices and can expire. Neither proves that the person opening it is the intended recipient; limited meeting links change how an offer can be used, not who a person is.
For appointments that need review, require approval before confirming a request. That's a human decision on the submitted details, not authentication supplied by the secret-link setting.
How can I test booking-page privacy myself?
Create a synthetic busy event called "PRIVATE TEST ORANGE" from 10:00 to 10:30 on a selected calendar, with a made-up location and description. Open the booking link in a private browser window on that date. Use test data only.
Confirm that the interval isn't bookable and that the distinctive title, location and description appear nowhere on the guest page. Your published consultation title should remain visible. Delete the synthetic event afterwards and allow the brief availability cache to refresh before expecting the time to return. The London-to-Sydney meeting planner compares dated working-hour overlap; confirm individual calendars after choosing a candidate window.
If the slot stays visible, check that the synthetic event is marked busy and its calendar is selected. The privacy test and the conflict test are related, but one verifies hidden details while the other verifies blocked time.
What happens when calendar access stops working?
When a required calendar connection can't be checked, affected booking pages become temporarily unavailable. Reconnect the Google account in Settings under Calendars and repeat the synthetic interval check, so you can verify that a known busy event removes the expected slot again. Reconnect before accepting more bookings.
| Symptom | Likely cause | Fix |
|---|---|---|
| Private test interval is offered | Unselected calendar or free event | Check selection and mark the event busy |
| Sensitive text appears on the page | Text was published in the event offer | Edit Basics or the configured location |
| Secret event still opens by URL | Direct-link access is expected | Share selectively or use an expiring offer |
| Page stops offering dates | Calendar authorisation failed | Reconnect before testing again |
Review pricing and account terms, then share your available times through a booking page after checking what you've published.
Steps
Connect Google in Settings
Authorise the calendars you need under Calendars. Keep Google Calendar sharing permissions unchanged; guests use the booking page.
Select only conflict calendars you need
Choose calendars whose busy events should remove slots. Set a writable destination for the appointments booked through your link.
Review Basics and Questions
Write the event title and location as guest-facing information. Remove personal details from descriptions and ask only for answers needed for the appointment.
Choose a sharing route
Share a normal event link or enable Secret event under Booking page to hide it from your public profile. Anyone holding that direct URL can still open it.
Run the synthetic privacy check
Add a temporary busy event with a distinctive test title. Confirm that its time disappears from the guest page while its title and details never appear.
Frequently asked questions
Do I need to change my calendar sharing permissions?
No. A booking page can offer available slots without making your Google Calendar public or adding the guest as a calendar viewer. You authorise the connection; guests open the published booking URL and supply booking details. Offer the public booking address instead of granting diary-viewing access, and test the guest view to check that the visible description contains only the appointment information you actually intend to share.
Can a forwarded secret link still be opened?
Yes. Someone receiving the direct URL can open a secret event even though it isn't listed on your public profile. Search exclusion reduces discovery; it doesn't verify identity or prevent a recipient from forwarding the address. Distribute it selectively and review requests when needed, remembering that hiding an event from the profile doesn't authenticate the person who follows the same direct address after someone forwards it.
Can I show clients the reason a time is blocked?
The availability page doesn't display the title or contents of the existing event that blocks a slot. If you want to explain a gap, communicate that yourself without placing private event details into a public booking description. Tell the guest directly if an explanation helps the arrangement, while keeping private reasons out of a public description that future visitors or forwarded-link recipients might also be able to read.
Related pages
- Google Calendar sync that checks work and personal time
Check several Google calendars, choose where bookings go, and learn which event fields we read. A fresh conflict check runs when guests book.
- How to check availability across Google calendars
Check work and personal Google calendars together: overlapping events from 10:00 to 11:30 block that whole period while bookings go to work.
- How to approve meeting requests before booking
Review meeting requests with Booking page > Requires approval. Set the 1,440-minute timeout and understand pending holds before Google invites.
- Custom times links and single-use links
Offer hand-picked times with a custom times link, or allow one booking from an event's normal schedule. See closure, expiry and secret-link differences.
- Best time to meet: London and Sydney (2026)
Compare London and Sydney: 0 shared office hours, clock changes and ranked meeting windows for 2026.
- What is a booking page?
A booking page displays available appointments and collects guest details. See its six parts, a 30-minute example and what stays private.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link