Privacy Policy

How Wiki CVAIL handles your data, including Google Calendar integration.

Last updated: September 2, 2026 · Controller: CVAIL Research Group — Universidad Industrial de Santander · Contact: [email protected]

Wiki CVAIL (https://wiki.cvail.co) is a research-group workspace for pages, seminars, calendars, and scheduling. This policy explains what we collect, why we collect it, and how you can control it — including when you connect a Google Account.

1. Data we collect

  • Account data: name, username, email, avatar, roles and groups you belong to. Stored in our PostgreSQL database.
  • Content you create: wiki pages, comments, calendar events, scheduling links and polls.
  • Google OAuth (only if you connect): openid, email, https://www.googleapis.com/auth/calendar.calendarlist.readonly, https://www.googleapis.com/auth/calendar.events, https://www.googleapis.com/auth/calendar.freebusy. We request offline access to keep your calendars in sync.
  • Calendar data (only mapped calendars): event summaries, start/end times, attendees, Meet links, busy blocks. We never import a Google calendar unless you explicitly map it in /calendar → Settings.
  • Technical logs: IP, user-agent, audit events (kept 7 days) and rate-limit counters.

2. How we use Google data

Google data is used only to provide the scheduling features you asked for:

  • Free/busy: to compute common available slots without revealing event titles, attendees, or descriptions to other users. The availability engine returns only positive free slots.
  • Two-way sync: to mirror events you create in Wiki to the mapped Google calendar and vice-versa, including Google Meet conference creation when you enable it.
  • Invitations: when you are the organizer, Google Calendar sends invites on your behalf via sendUpdates=all. The organizer address is your connected Google account (e.g. your Gmail).

We do not use Google data for ads, profiling, or any purpose beyond the Wiki scheduling experience. We do not sell it or share it with third parties except as described below.

3. Storage and security

  • OAuth tokens are encrypted at rest with a dedicated 32-byte GOOGLE_TOKEN_ENCRYPTION_KEY (Fernet, key versioned) — never with the JWT signing key. Only refresh_token and access_token are stored; code_verifier is PKCE-bound and discarded after exchange.
  • state and PKCE code_challenge expire after 10 minutes.
  • Communication with Google uses TLS and authorization_code flow with PKCE + offline consent.

4. Sharing

  • Other Wiki users: only free slots and aggregate vote counts are visible. Your private event titles/descriptions are never exposed via scheduling APIs.
  • Google LLC: as your calendar provider when you map a calendar (subject to Google Privacy Policy).
  • Resend (email): transactional mail (verification, password reset, scheduling notifications) is delivered via Resend from Wiki <[email protected]>. Resend sees only the recipient, subject and body you triggered.
  • We disclose data only when required by law.

5. Your controls

  • You can disconnect Google at any time in /calendar → Settings → Google Calendar → Disconnect. We revoke the OAuth token at https://oauth2.googleapis.com/revoke and mark local events as DISCONNECTED — local events stay in Wiki but stop syncing.
  • You can remove a single calendar mapping (events already imported remain) or delete events directly in either calendar; changes sync every few minutes and the most recent edit wins.
  • You can request export or deletion of your Wiki account by contacting [email protected]. Deleting your user soft-deletes your content per our retention policy.

6. Legal basis and retention

Consent for Google scopes is granted explicitly via the Google consent screen; you can withdraw it by disconnecting or by revoking access in myaccount.google.com/permissions. We retain mapped calendar data while the mapping is active and until you disconnect or delete events. Audit logs are deleted after 7 days. Booking requests awaiting approval expire after 24 hours.

7. OAuth consent screen — Google verification

When you click “Connect Google Calendar” we request the scopes listed in §1 via accounts.google.com/o/oauth2/v2/auth with access_type=offline and prompt=consent. The app is currently in External testing mode; only test users added in Google Cloud Console can consent until verification is complete. If you see “Access blocked — This app’s request is invalid”, ensure your Google account is listed as a test user or wait for verification.

8. Changes

We will post material changes here and update the “Last updated” date. For questions, write to [email protected] or open a ticket in the Wiki.

Compliance notes: Google API Services User Data Policy — use of Google Calendar data is limited to the use cases described in §2. For scope-specific details see developers.google.com/identity/scopes#calendar. This app does not request restricted scopes beyond those listed in §1.