---
title: "What can scheduling apps see in your Google Calendar?"
url: https://meet.barq.dev/guides/what-can-scheduling-apps-see-in-google-calendar
updated: 2026-11-17
author: "Hammad Ali"
---

# What can scheduling apps see in your Google Calendar?

> **Short answer:** A scheduling app's Google consent screen describes the access you grant, while its implementation determines what it reads. Barq Meet requests calendar read and event-edit access to check conflicts and create bookings. From existing events, we read timing and scheduling status, including your own RSVP, but never titles, descriptions, locations or other attendees.


## What does a scheduling app Google Calendar permission allow?

Calendar permission is authority granted by your Google account; it isn't a report of every field an app collects. To understand an app's behavior, compare its permission request with its documented data use, including the fields it reads from appointments that already exist. Ask about both before connecting it.


For Barq Meet, the requested scopes include `calendar.readonly` and `calendar.events`, alongside identity scopes for sign-in. We verified those scope names in our authentication code on 17 November 2026. They explain why the consent prompt asks for broader access than seeing a set of occupied hours.


We need event-edit access to create and maintain appointments booked through Barq Meet. We write only the events we book; granting a permission isn't a statement that we edit unrelated entries in your diary.


The [calendar connection explanation](https://meet.barq.dev/features/google-calendar-sync) distinguishes the Google calendars used to check conflicts from the calendar that receives new appointments. Selecting several calendars for conflicts doesn't mean every one receives a new event.


## Which fields do we read from existing calendar events?

We read start and end times, busy/free status, event status and type, and your own accept or decline response to decide whether an interval blocks booking. We never read existing event titles, descriptions, locations or other attendees' identities. Your appointment labels stay unread.


That is more precise than saying "free busy access only". The consent request is broad, and the implementation uses more scheduling information than two timestamps. Your own response matters because a declined event shouldn't occupy your availability. The [free and busy guide](https://meet.barq.dev/guides/show-as-free-or-busy-google-calendar) explains the other event exclusions that can affect a test.



**Existing event data used and excluded by our conflict checks**

| Read for scheduling | Never read from existing events |
| --- | --- |
| Start and end times | Event titles |
| Busy or free status | Event descriptions |
| Event status and event type | Event locations |
| Your own accept or decline response | Other attendees' names or email addresses |


Source: our calendar operations and authentication code, checked 17 November 2026. The diagram describes existing-event conflict checks; it doesn't describe the details you deliberately submit to create a new booking.


We request selected event fields from Google instead of requesting the title and then promising to hide it later. In a hypothetical example, a busy 10:00 to 10:45 appointment blocks 45 minutes without us reading what the appointment is called.


## Can a guest see my other Google Calendar events?

A guest sees the appointment times offered by your [booking page](https://meet.barq.dev/glossary/booking-page), not a view of your existing diary. Your selected calendars inform availability behind that page. Sending the booking URL doesn't give the recipient access to their titles or participant lists. Share the appointment page deliberately.


Suppose you offer 30-minute calls between 09:00 and 12:00, and an existing busy appointment spans 10:00 to 10:45. That interval removes conflicting candidate starts. The guest doesn't need the busy event's title to understand which times they can choose.


Read [how to share availability without sharing your calendar](https://meet.barq.dev/guides/share-availability-without-sharing-calendar) when you want a public booking route without inviting someone to browse the underlying calendars.


The timing still conveys that some hours aren't offered. Availability isn't a promise that a recipient can infer nothing about your schedule, especially if they repeatedly inspect the page. Publish the working hours you intend to make available.


## Does this prove Calendly or another scheduler is safe?

No. Our field selection describes Barq Meet and can't establish what another scheduling app reads, stores or writes. If you're checking Calendly calendar access or asking "is Calendly safe", examine that vendor's current permissions and disclosures directly. Product names aren't permission categories.


The approved research doesn't establish another scheduler's field-level reading behavior, so we won't fill that gap with assumptions. A pricing table isn't a privacy audit, and a broad Google prompt alone doesn't prove a particular collection practice.


Use these questions when comparing an app:


- Which Google scopes does it request, and why?
- Does it read event titles, descriptions or attendee identities?
- Which calendar receives new bookings?
- Does it explain how to disconnect and what happens to previously stored data?


Keep answers in context. Revoking a connection and deleting information already held by an app are different requests; don't assume one answers the other without a documented policy.


## How should I review calendar access before sharing my link?

Inspect the account you're connecting, choose the calendars that contain conflicts, and make a test booking to check the destination and guest view. Review the current consent wording before agreeing to it. Pause if it doesn't match your expectations. When access should end, [disconnect the intended Google calendar account](https://meet.barq.dev/guides/revoke-calendar-access) and inspect which conflict sources remain. The [Google Calendar time-finding guide](https://meet.barq.dev/guides/find-a-time-google-calendar) separates existing calendar access from an appointment page that lets an outside guest choose a host's opening.


1. Identify the Google account containing the calendar you intend to use.
2. Review the Google permission request during connection.
3. Select conflict calendars and a writable booking destination.
4. Open the public event page as a guest and inspect available times.
5. Make a test appointment with an inbox you control, then check its calendar event and confirmation.


We perform another busy-time check when a guest submits the appointment. That timing check can reject a newly conflicting slot; it doesn't reveal the conflicting event's name to the guest.


| Concern | What to inspect | What the test establishes |
| --- | --- | --- |
| Wrong account connected | Account selected at authorisation | Which account supplied calendar access |
| Personal calendar ignored | Conflict-calendar selection | Whether its busy time removes slots |
| Appointment written somewhere unexpected | Booking destination | Where the new event appears |
| Guest might see the diary | Public page in a private window | What the recipient's page displays |

A successful test confirms booking behavior, not every aspect of a privacy policy. For an organization's review, use the documented permissions and your own requirements alongside that test. Use the [Zeeg comparison](https://meet.barq.dev/compare/barq-meet-vs-zeeg) when privacy review and documented hosting requirements are part of the scheduling decision.


Check [the product scope and pricing terms](https://meet.barq.dev/pricing), then [connect a calendar for a controlled test](https://meet.barq.dev/app/sign-in) when you're satisfied with the access request.

## Steps

1. **Identify the Google account**: Choose the account whose calendars you intend to use. Keep any unrelated accounts out of the test.
2. **Read the consent request**: Review the calendar access Google asks you to grant. Our implementation uses read access and event-edit access for scheduling.
3. **Select calendars and booking destination**: Choose which calendars should count as conflicts and where new bookings should be written. These are different choices.
4. **Inspect the guest page**: Open the booking URL privately and compare offered times with known busy intervals. The page offers appointments instead of a diary view.
5. **Check a trial calendar event**: Book with an inbox you control and inspect the destination calendar and invitation. Remove the test appointment when you finish.

## Frequently asked questions

### Why does the consent screen mention editing events?

Creating and maintaining booked appointments needs event-edit access. That permission is broader than a read-only availability display, while our implementation writes only the appointments booked through the app, not unrelated entries in your calendar. Compare the consent wording with the documented conflict-checking fields, keeping permission to create booking events distinct from a claim that the app reads every detail of your existing diary for availability.

### Do you read the names of people on existing invitations?

No. Existing-event conflict checks exclude other attendees' names and email addresses. We use your own response status to avoid blocking time for an invitation you've declined, alongside the event's timing and scheduling status. We inspect your own accept or decline response for conflicts, while the names and contact details of the other invited people aren't part of the existing-event fields used for that check.

### Is a booking form answer part of the existing-event privacy promise?

No. Information you supply for a new booking is different from details of existing calendar entries. Keep sensitive material out of appointment questions unless you've reviewed where booking details are written and who receives them. Request only preparation information you're comfortable putting into the booking record, since details a guest submits for a new appointment are different from information read from unrelated existing calendar entries to remove busy time.

## Related pages

- [Share availability without sharing your calendar](https://meet.barq.dev/guides/share-availability-without-sharing-calendar)
- [Google Calendar sync that checks work and personal time](https://meet.barq.dev/features/google-calendar-sync)
- [Show as free or busy in Google Calendar: what it changes](https://meet.barq.dev/guides/show-as-free-or-busy-google-calendar)
- [How to remove a scheduling app's access to Google Calendar](https://meet.barq.dev/guides/revoke-calendar-access)
- [Zeeg vs free Google Calendar scheduling](https://meet.barq.dev/compare/barq-meet-vs-zeeg)
- [How to see someone's availability in Google Calendar](https://meet.barq.dev/guides/find-a-time-google-calendar)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
