Reframe Zacal — Data Practices

Last updated: March 20, 2026

Reframe Zacal is a coaching session management platform operated by Glucobit, Inc. (“Reframe”). It enables coaches to configure their availability, accept bookings from clients, and sync with external calendars to prevent scheduling conflicts. This page describes the data Reframe Zacal collects, how it is used, and how it integrates with Google Calendar.

This page supplements the Reframe Privacy Policy and Terms of Use, which govern your use of all Reframe services.

What Data Reframe Zacal Collects

Coach Account Data

When a coach signs in, we store their name, email address, and organizational role to identify them within the platform and associate them with their bookings, availability rules, and calendar connections.

Booking Data

When a client books a coaching session, we collect the client's name, email address, timezone, selected time slot, and any responses to intake questions configured by the coach. This data is used to confirm the booking, send notifications, and create the coaching session.

Availability & Scheduling Rules

Coaches configure their weekly availability windows, date overrides (holidays or custom hours), event types (session templates with durations and buffer times), and booking rules. This data is stored to generate available time slots for clients.

Payment Data

For paid sessions, payment is processed through Stripe. Reframe Scheduling stores the booking's payment status and Stripe transaction identifiers. We do not store credit card numbers or full payment credentials.

Google Calendar Integration

Coaches may optionally connect their Google Calendar to Reframe Scheduling. This integration serves two purposes:

  1. Prevent double-booking — We read your existing Google Calendar events to determine when you are busy, so those times are automatically blocked from your available slots.
  2. Automatic event creation — When a coaching session is confirmed, rescheduled, or cancelled, we create, update, or remove the corresponding event on your Google Calendar.

OAuth Scopes Requested

What Google Calendar Data We Store

We store only the minimum metadata necessary to calculate availability:

We do not store event titles, descriptions, attendee lists, locations, attachments, or any other event content.

How We Sync Your Calendar

When you connect your Google Calendar, we register a webhook so Google notifies us when your calendar changes. On each notification, we fetch the updated event metadata for a rolling 60-day window and refresh our stored records. We also run periodic background syncs to ensure data stays current. A 60-second debounce prevents redundant fetches.

Data Retention & Deletion

Synced calendar event metadata is retained only for the duration necessary to provide scheduling services (a rolling 60-day window). Events that no longer appear in your calendar are automatically removed during each sync cycle. When you disconnect your Google Calendar from Reframe Zacal, all stored calendar event metadata for that connection is deleted.

No Third-Party Sharing

Your Google Calendar data is not shared with any third parties. It is not used for advertising, analytics, market research, or any purpose unrelated to the scheduling functionality described above.

Google API Services User Data Policy

Reframe Zacal's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Revoking Access

You can disconnect your Google Calendar at any time from the Calendar Sync page in your Reframe Zacal dashboard. You can also revoke access directly from your Google Account permissions.

Contact

If you have questions about Reframe Zacal's data practices, please contact us at support@reframeapp.com