Calendar privacy

GymBuddy uses your schedule to keep workout recommendations out of busy periods.

Calendar files

Imported .ics files are processed in your browser. The original file, event titles, descriptions, and attendees are not uploaded. Remove the file or reload this page to clear it from this tab.

Google Calendar

Connecting Google grants read-only access to calendar availability. GymBuddy queries your primary calendar for busy times directly from Google. It does not request event contents or permission to edit your calendar. The access token stays in this tab’s memory and is cleared on reload; it is not saved to our servers or browser storage.

Recommendations

When you request a recommendation, GymBuddy sends only busy start and end times, workout duration, and gym preferences to its hosted API. Calendar files and Google tokens are never sent to that API or stored in Databricks. The application does not persist your busy times. Hosting providers process ordinary request metadata to operate the service.

Gemini explanations

When Gemini is configured, our API sends Google the validated workout options (gym, workout times, forecast occupancy, and confidence), your workout duration, gym preferences, and crowd tolerance to explain the recommendation. Your calendar events, busy blocks, original files, and Google access token are not included. Explanations may be reused briefly in server memory. Google processes these requests under its Gemini API terms; free-tier requests may be used to improve Google products. If Gemini is unavailable, the schedule-based recommendation still works.

Disconnecting

Use Disconnect Google to clear local access and request removal of Google’s saved permission. You can also remove access in Google Account connections. Reloading clears the local session but does not revoke Google’s saved consent.

This is a hackathon prototype. To report a privacy issue without sharing calendar contents, use the project issue tracker.