Calendar privacy policy

Information we access and store

• Account and connection information: your connected Google email address, a hashed Google account identifier, the identifier and display name supplied by your scheduling service, connection status, and your consent settings and timestamps.
• Appointment calendar: the identifier of the dedicated calendar created by Et Cetera, event identifiers, event times and status, and synchronization records. When full-detail sharing is enabled by the scheduling service and you consent, event data can also include titles, descriptions, locations, and attendees in that dedicated calendar.
• Calendar selection and availability: names and identifiers of calendars available to your account, your selected calendar identifiers, and free/busy intervals from those calendars for the requested date range. Your primary calendar is selected by default; you can choose up to ten calendars. This access does not provide personal event titles, descriptions, locations, attendee lists, or event identifiers.
• Connection credentials and operational records: encrypted Google access and refresh tokens, notification-channel and synchronization identifiers, pending delivery and retry records, and records of service requests and their outcomes.

How the integration uses your Google data

Et Cetera uses this information to identify the connected account, check availability, manage appointments in its dedicated Google calendar, synchronize changes with your scheduling service, and maintain the connection. The integration reads free/busy times from your selected calendars and writes appointments only to the dedicated calendar.

The default sharing mode provides event times and status without event titles, descriptions, or attendees. Full-detail sharing requires the requesting service’s configuration and your consent on the connection page. This setting applies to events in the dedicated calendar; it does not expand access to the contents of your personal calendars.

Et Cetera’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

Who receives information

Your scheduling service receives connection information, including the connected account email and calendar names used in the calendar picker, and calendar information allowed by your consent. Et Cetera delivers that information through authenticated service requests and the scheduling service’s configured notification endpoint. Google receives requests needed to operate the calendar connection. Et Cetera uses Base44 infrastructure to run the service and store its connection and operational records.

Access to stored integration records is restricted to authorized service operations and administrative access. Your scheduling service’s own handling of appointments and personal information is covered by its policy, which is linked on the connection page when supplied by that service.

Storage and protection

Google access and refresh tokens are encrypted before storage. Production connections use HTTPS. The integration retains connection and operational records to provide synchronization, process retries, record consent and usage, and handle reconnects or deletion requests. A simple disconnect and a request to delete connection data have different effects, described below.

Disconnecting, revoking access, and deleting data

You can ask your scheduling service to disconnect Et Cetera. A completed disconnect clears that connection’s stored Google tokens, email, and selected personal-calendar identifiers, cancels its pending synchronization and notification deliveries, and disables the connection. Some linking, event-mapping, and usage metadata remains to support a deliberate reconnect.

You can also remove Et Cetera’s access in your Google Account’s third-party connections settings. This can affect every connection using the same Google account and Et Cetera authorization. When a scheduling service disconnects only one of several active links for the same account, Et Cetera preserves the Google authorization used by the other active links.

To delete the integration’s data for your connection, ask the scheduling service to delete it or contact us below. The deletion process removes the provider connection, tokens, event mappings, connection tickets, pending synchronization and delivery records, and provider-specific usage records. A one-way hashed deletion marker remains to prevent old requests from recreating the deleted connection. This request does not delete data separately held by your scheduling service.

Disconnecting or deleting connection data does not remove existing events or the dedicated calendar from Google Calendar. You can remove those directly in Google Calendar.

Contact

For questions about this integration or help with a data-deletion request, contact Et Cetera at erodin10@gmail.com. Please identify the scheduling service you connected through so we can direct the request appropriately.