ViyoraViyora← Back to home
Legal

Google API Services — Limited Use

Last updated: 10 February 2026

This page describes how Viyora (operated by Viyora Tech) uses data received from Google APIs when a clinic connects their Google Calendar to Viyora. It is published in compliance with Google’s Google API Services User Data Policy, including the Limited Use requirements for Workspace and consumer Google accounts.

1. Which Google scopes we request

When a doctor or clinic administrator clicks “Connect Google Calendar” inside Viyora, we request only the narrowest scopes needed for two-way appointment synchronisation:

  • https://www.googleapis.com/auth/calendar.events — view, create, edit and delete events on the calendars the connecting user chooses. This is a sensitive scope. We do not receive or store any events from calendars the user does not explicitly select in Settings → Google Calendar.
  • https://www.googleapis.com/auth/calendar.calendarlist.readonly — read the list of calendars the user is subscribed to, purely so the “Which calendar should Viyora write to?” picker can populate. This is a non-sensitive scope.
  • openid, email, profile — to display the connected Google account’s email in Viyora Settings so doctors can verify they linked the right account.

We do not request full auth/calendar access, gmail.* scopes, drive scopes, contacts scopes, or any other Google user data scope.

2. How we use Google Calendar data

  • Push (Viyora → Google): When a receptionist books, reschedules, or cancels a chairside appointment in Viyora, we mirror that change to the doctor’s selected Google Calendar so their personal calendar stays in sync with the clinic.
  • Pull (Google → Viyora): Every five minutes we import events the doctor added directly to Google (e.g. holidays, conference days, personal appointments) into a private google_busy_events table. Viyora uses those events only to strip conflicting slots from online-booking availability — so patients never book a slot when the doctor is unavailable.
  • Event titles & descriptions pulled from Google are shown to the doctor and receptionists inside their own clinic only. They are never shown to patients, never rendered publicly, and never used to train models.

3. Limited Use

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

Specifically:

  • We use Google user data only to provide and improve the calendar synchronisation feature described above.
  • We do not transfer Google user data to third parties except (a) as necessary to provide the feature (e.g. our own Kubernetes-hosted MongoDB, which is subject to the same Limited Use terms), (b) when required by applicable law, or (c) as part of a merger or acquisition where the acquirer commits to the same Limited Use terms.
  • We do not use Google user data for serving advertisements, retargeting, or building any advertising profile.
  • We do not allow humans to read Google user data unless (a) we have the affected user’s explicit written consent for a specific message, (b) we require access for security purposes such as investigating abuse, (c) we require access to comply with applicable law, or (d) the data (including derived data) has been aggregated and de-identified.
  • We do not use Google user data to train, fine-tune or evaluate generalised or third-party AI/ML models. Claude Sonnet 4.5 (via the Emergent LLM proxy) is used for clinical reasoning on Viyora-native data (patient notes, treatment plans) only — never on data received from Google APIs.

4. Storage & encryption

  • Google OAuth refresh tokens are encrypted at rest using Fernet (AES-128-CBC + HMAC-SHA256) with a per-deployment secret derived from our JWT signing key. A MongoDB dump alone is not sufficient to replay a token.
  • Imported busy events are scoped by both clinic_id and doctor_id, and are only served to authenticated members of that clinic.
  • Transport is TLS 1.2+ end-to-end between Viyora, Google APIs, and the connecting user’s browser.

5. Revocation & deletion

A doctor can disconnect Google Calendar at any time from Settings → Integrations → Google Calendar → Disconnect. On disconnect we immediately:

  • Delete the encrypted refresh token from our database.
  • Delete all imported google_busy_events rows for that doctor.
  • Stop all scheduled sync jobs for that doctor within five minutes.

You can additionally revoke Viyora’s access from your Google account at myaccount.google.com/permissions.

6. Contact

For any questions about how Viyora handles data received from Google APIs, or to file a Limited Use compliance concern, please contact:

Viyora Tech
Email: admin@viyora.co.in
Website: https://viyora.co.in