Barq Meet
Create your free link

How to make Google Calendar events private

On this page

What does making a Google Calendar event private mean for bookings?

Treat detail visibility and appointment availability as separate decisions. Decide both. You may want the topic of an appointment kept private while its occupied time stays unavailable to clients, and changing the name or visibility of an event shouldn't be used as a substitute for checking its blocking status.

For Google's exact event and sharing controls, use Google Calendar Help. Our research checked the platform material as of 17 November 2026 but doesn't establish the current event-privacy menu sequence or its complete permission rules, so we don't supply an unverified path.

You'll need to know which calendar contains the event, who may already have access to that calendar and which calendars your scheduler checks. Keep those questions separate from what a guest sees on a public booking page.

We read selected calendars for conflicts as described in our Google Calendar sync explanation. That connection gives the booking engine timing information; it doesn't turn the public page into a view of your existing event details.

Which privacy question should I answer first?

Identify who you want to keep information from before changing a setting. Be precise. A colleague with calendar access, a person opening your booking URL and an app authorised through Google are different audiences, so a single visibility choice shouldn't be assumed to cover all three. The calendar-access removal guide distinguishes revoking a connection from canceling meetings already accepted through it.

AudienceReviewDon't assume
People with calendar accessGoogle's sharing and event controlsBooking-page behavior describes their permissions
Visitors to the booking linkWhat the public appointment page displaysThey can see the underlying event list
A connected scheduling appConsent and documented data useA privacy label narrows every granted capability

Use Google's help to check the first audience for your account. We haven't verified every sharing-role exception or administrator rule, and shouldn't claim that an event marked private defeats every kind of calendar access.

For the second audience, open the booking URL without the host session. For the third, read what scheduling apps can see in Google Calendar and distinguish our documented behavior from claims about other apps.

We never infer private details from an event title because we don't read that title. Calling an entry "Personal" isn't required to keep its existing title out of our conflict checks.

Does an event need to be free to hide its details?

No. In our scheduling model, busy/free controls whether the interval can block appointments; it isn't a label for the sensitivity of the topic. Keep busy commitments blocking. A private consultation still occupies the time even when the person opening your booking link shouldn't know what you're doing.

For a computed example, imagine normal meeting hours from 09:00 to 11:00, thirty-minute meetings, half-hour starts and no buffers. A busy commitment from 09:30 to 10:00 removes that one start, leaving 09:00, 10:00 and 10:30 if no other rule excludes them.

Making that interval free removes that particular conflict in our engine. Other rules still apply. That is a behavior of our booking checks, not a statement that Google's privacy setting changes an event's busy/free value automatically.

The multiple-calendar availability guide explains how a personal calendar can protect time alongside a work calendar. Keep the personal calendar selected if its commitments should count.

What do we read from an existing private event?

We read start and end times, busy/free state, status, event type and your own acceptance or decline response from existing calendar entries. Private topics stay out of those reads: existing titles, descriptions, locations and other attendees are never read. The title isn't a privacy signal. We don't decide which topics look sensitive before excluding those details from existing event reads. The comparison with Zeeg keeps unverified hosting claims out of a choice that may depend on a particular data location.

Google's consent screen still asks for broad calendar access because we need to create bookings. We write only the events we book. What the permission screen says an app can access and what it reads from existing entries are different facts worth checking.

We use your own response so declined events don't block your time. That's why "we never read any attendee-related field" would be inaccurate even though other attendees' details aren't read.

Don't transfer this account of our implementation to a competitor. If another scheduler's handling of private events is the concern, check its documented data use and permissions instead of relying on our answer.

How do I test privacy and availability together?

Use a temporary timed entry inside normally offered hours, then compare the public page before and after its blocking status changes. Keep other settings fixed. A controlled thirty-minute interval makes it easier to spot whether the intended conflict is active without editing a real confidential appointment.

Check the following separately: the calendar's own visibility using Google's instructions, the guest page's available starts, and the conflict calendars selected in the scheduler. Seeing a start disappear establishes a booking conflict; it doesn't prove anything about a colleague's Google sharing permissions.

Unexpected resultCheck next
Busy private time remains bookableSelected conflict calendar and event status
Whole day is unavailableAll-day preference and other conflicts
Guest sees the wrong clock timeGuest zone and schedule zone
Colleague sees details in GoogleGoogle's sharing and account-specific rules

For a new offer, follow the Google-connected booking-link setup. Review current account features and terms, then create an offer that shares appointment choices while keeping your underlying calendar details out of the public page.

Steps

  1. Identify the detail you want hidden

    Decide whether you are reviewing an existing event, calendar sharing or app permissions. These are different exposure paths and need separate checks.

  2. Use Google Calendar privacy help

    Follow current Google Calendar Help for the event and sharing controls available to your account. This guide does not establish a current desktop or mobile visibility-menu path.

  3. Keep availability status deliberate

    Decide whether the commitment should still block appointments. Hiding its details and freeing its time are different intentions.

  4. Review selected conflict calendars

    In the booking app, check that the calendar containing the commitment is included for conflicts. Review other connected calendars for overlapping entries.

  5. Test a timed private commitment

    Use a 30-minute test interval inside normally offered hours. Confirm that the busy period remains unavailable without exposing existing event details through the booking page.

Frequently asked questions

Can I hide an appointment topic while keeping its time blocked?

That's the intended separation to test: private details shouldn't require making an occupied interval bookable. In our scheduler, keep the relevant calendar selected and preserve a blocking busy interval, then inspect the page as a guest. Keep its blocking status and calendar conflict selection intact, then inspect the public page for that interval without expecting a privacy label alone to define whether it removes available starts.

Will the booking page show the names of my other guests?

Our conflict checks never read other attendees from existing calendar events. They use your own response status alongside timing and availability fields, so the existing event's guest list isn't part of the information used to offer appointments. A guest can see eligible appointment choices without learning which person or subject occupies the rest of your diary, provided private information isn't copied into your public description yourself.

Does this page confirm the mobile privacy-setting labels?

No. We haven't verified the current mobile event-visibility labels in the supplied research. Use Google's current Calendar Help for that interface, then test the resulting booking availability instead of relying on an assumed menu path. Use the official instructions for the client and device in front of you, and avoid assuming the desktop control names quoted here establish the exact labels of every mobile version.

Create your free booking link

Sign in with Google, create an event and share your link.

Create your free link