Cheddify is the link creators put in their bio to give their community live access to them — per-minute 1:1 video and audio calls, booked sessions, and paid DMs. Creators who accept booked sessions can optionally connect a Google Calendar so that the availability Cheddify offers buyers reflects their real schedule.
What the integration does
This integration is optional. Cheddify’s core features — per-minute calls, DMs, and booked sessions — all work without it. Creators connect it themselves from Go Live → Scheduling on the web, or the Scheduling screen in the mobile app, and can disconnect at any time from the same screen. Buyers are never asked to connect a calendar.
When a creator connects their calendar, Cheddify:
- Reads free/busy times only. Before showing a buyer which slots are open, Cheddify asks Google for the busy intervals on the creator’s primary calendar over the window being displayed, and hides slots that overlap. Cheddify does not receive event titles, descriptions, locations, guests, or attachments.
- Creates one event per booking. When a buyer books a session, Cheddify creates a single calendar event with the session time and details. If the booking is rescheduled or canceled, Cheddify updates or deletes that same event.
- Shows the connected account. The Google account email address is displayed in scheduling settings so the creator can confirm which account is connected.
Permissions we request
| Permission | What Cheddify does with it |
|---|---|
See your availability (calendar.freebusy) | Reads only busy/free time intervals on the creator’s primary calendar, so buyers are never shown a slot that conflicts with an existing commitment. Cheddify does not receive event titles, descriptions, locations, guests, or attachments. |
View and edit events (calendar.events) | When a buyer books a session, Cheddify creates a single calendar event with the session details. If the booking is rescheduled or canceled, Cheddify updates or deletes that same event. Cheddify stores the ID of every event it creates and acts only on those IDs — it never reads, lists, or modifies events it did not create. |
Your email address (userinfo.email, openid) | Displayed in scheduling settings so the creator can confirm which Google account is connected. |
Why we request calendar.events
Narrower scopes cannot create events. calendar.freebusy is read-only, and calendar.events is the least-privileged scope Google offers that permits creating, updating, and deleting an event. Cheddify requests no other Calendar scope, and does not request access to Gmail, Drive, Contacts, or any other Google service for this integration.
How the data is handled
Google OAuth refresh tokens are stored encrypted at rest and are used only to perform the actions described above on the creator’s behalf. Free/busy intervals are used at the moment availability is rendered and are not retained beyond that. Cheddify does not copy the contents of a creator’s calendar into its systems.
Disconnecting
A creator can disconnect Google Calendar at any time from Go Live → Scheduling on the web or the Scheduling screen in the mobile app. Disconnecting deletes the stored refresh token and the stored Google account email from Cheddify, and Cheddify stops reading availability and stops creating events. Access can also be revoked directly from your Google Account permissions page. Calendar events Cheddify already created remain on your calendar for you to keep or delete.
Limited Use
Cheddify’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, do not use it for advertising, and do not use it to train machine-learning models.
Questions: cheddify.com/contact · Full Privacy Policy