Telos Booking

Privacy Policy

This policy explains how Telos Ops accesses, uses, stores, shares, and deletes calendar data when an authorized client connects a calendar account to Telos Booking.

Effective and last updated: August 4, 2026

1. Who We Are And When This Policy Applies

Telos Ops ("we," "us," or "our") provides websites, operational tools, and scheduling integrations for client businesses. This policy applies to connected calendar information processed through a Telos-built scheduling tool when an authorized client connects a supported account.

The client business controls its customer and appointment records. Telos Ops processes that information as a technology and hosting provider for the client. This policy supplements our applicable client agreements and the client business's own privacy disclosures.

2. Calendar Data We Access And Store

The integration requests only the permissions needed to operate calendar synchronization:

  • Calendar list access: read-only access to calendar names and identifiers so an authorized user can select the calendar to connect.
  • Calendar event access: permission to view and edit events on calendars the user authorizes.

Depending on how the integration is used, we may process or store:

  • The selected calendar's identifier and display name.
  • Event identifiers, titles, start and end times, all-day status, availability status, color, update time, cancellation or deletion status, and synchronization metadata.
  • Appointment details that Telos places into linked calendar events, such as service details, customer and pet-care information, address information, requested add-ons, owner notes, and secure Telos action links.
  • Encrypted OAuth access and refresh tokens, token expiration information, connection status, and connection errors.
  • Incremental synchronization tokens and provider notification-channel identifiers, resource identifiers, and expiration times.
  • Limited security, audit, and troubleshooting records related to the connection.

When Google Calendar is connected, Telos Ops does not request access to Gmail, Google Drive, contacts, photos, or other unrelated services.

3. How We Use Calendar Data

We use connected calendar data only to provide and support the calendar features requested by the client, including to:

  • Display calendars available for the authorized user to connect.
  • Read existing events from the selected calendar and treat relevant events as unavailable time.
  • Create, update, color-code, and synchronize booking, travel, and availability events.
  • Recognize event moves or deletions made in the connected calendar and reflect those changes in Telos Booking.
  • Detect scheduling conflicts, renew synchronization channels, recover interrupted synchronization, and troubleshoot errors.
  • Protect the integration, prevent misuse, and maintain required audit records.

We do not use connected calendar data for advertising, credit decisions, unrelated profiling, or training general-purpose artificial intelligence models.

4. Sharing, Transfer, And Sale Of Data

Telos Ops does not sell connected calendar data. We do not share it for targeted advertising or with data brokers. Information may be transferred only as needed to operate the requested integration, including:

  • With the connected calendar provider when the integration reads or writes calendar information at the user's direction.
  • With the connected client business and its authorized Telos portal users.
  • With infrastructure, hosting, backup, security, and communications providers acting for Telos Ops under appropriate confidentiality and data-protection obligations.
  • When required by law, legal process, or a good-faith need to protect users, the public, Telos Ops, or its systems.
Telos Ops's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. Human Access To Calendar Data

Authorized Telos Ops personnel may access provider-derived information only when needed to provide requested support, investigate a security or synchronization issue, comply with law, or when the user or client has given specific permission. We do not allow personnel to read connected calendar data for unrelated purposes.

6. Security

We use HTTPS for data in transit, encrypt OAuth tokens at rest, limit portal and system access by role and tenant, and maintain audit and error records. No method of electronic storage or transmission is completely secure, but we use administrative, technical, and organizational safeguards appropriate to the nature of the data.

Users should protect their calendar-provider and Telos credentials and promptly report suspected unauthorized access.

7. Retention And Deletion

We retain OAuth credentials and synchronization state while the integration is connected and for only as long as needed to provide, secure, support, or document the service. Appointment and audit records follow the retention terms applicable to the connected client's Telos service.

Disconnecting or revoking access stops future synchronization after Telos receives and processes that change. To request deletion of stored calendar connection credentials and related synchronization data, email contact@telosops.com. We may retain limited security, transaction, legal, or audit information where required, and residual copies may remain in protected backups until they cycle out under our backup schedule.

Disconnecting the integration or deleting Telos data does not automatically remove historical events already written to the user's connected calendar. The calendar owner can remove those events through the calendar provider. Past events are otherwise governed by the user's provider account settings and policies.

8. Your Choices And Controls

  • Choose which authorized calendar is connected.
  • Disconnect the integration through Telos Ops or ask us to disconnect it.
  • Revoke Telos Ops access through your Google Account's third-party connections.
  • Ask to access, correct, or delete applicable calendar connection data by contacting us.

Revoking access may prevent calendar synchronization and related scheduling features from working.

9. Children's Privacy

This business integration is not directed to children under 13, and we do not knowingly connect calendar accounts belonging to children.

10. Changes To This Policy

We may update this policy when the integration, applicable requirements, or our data practices change. We will post the revised policy here and update the effective date. Material changes may also be communicated through the Telos portal or directly to affected clients.

Website managed by TelosOps