Privacy Policy

Workday to Google Calendar (the “App”) converts a course schedule file (XLSX) into Google Calendar events in your account. The App is a client-side web application; it does not run a custom backend or database and does not sell or share personal information.

1) What Google user data the App accesses

The App uses Google OAuth and the following Google Calendar scopes:

• https://www.googleapis.com/auth/calendar – needed only to create a new calendar when you choose “Create new calendar.”
• https://www.googleapis.com/auth/calendar.events – needed to create events on the calendar you select.

Using these scopes, the App may access the following Google user data strictly to perform the requested actions:

• Calendar list metadata: calendar ID, summary (name), primary flag, time zone (via calendarList.list) to let you choose a target calendar.
• Created calendar metadata: the ID and summary of a calendar you ask the App to create (via calendars.insert).
• Event fields the App writes: title, location, start/end time, and recurrence rule for the class meetings (via events.insert).

The App does not read the contents of your existing events. It only lists calendars to display options and writes new events you explicitly request.

2) Other data the App uses

• Your XLSX file: The file you select is processed locally in your browser to parse course times and locations.
• OAuth tokens: Google’s client libraries obtain an access token in your browser to call the Calendar API on your behalf.

3) How data is used

• All parsing of your XLSX and construction of calendar events occurs in your browser.
• When you confirm, the App calls Google Calendar APIs from your browser to create a calendar (optional) and insert the class events you requested.
• No server-side storage: The App does not send your XLSX contents, calendar data, or tokens to any server we control.

4) Data protection & security

• Transport security: The site is served over HTTPS.
• Least-privilege access: Only the scopes listed above are requested; the App uses them solely to create calendars and insert events.
• No persistent backend storage: We do not store Google user data or tokens on our servers (we do not operate a custom backend).
• Token handling: OAuth tokens are managed by Google’s client libraries within the browser runtime and are not transmitted to us.
• No human access: We do not allow humans to read Google user data obtained through the App.
• Limited Use Compliance: The App’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

5) Data sharing

We do not sell, rent, or share your personal information with third parties. Google is the processor of Calendar API requests you authorize.

6) Data retention & deletion

• We do not retain personal data. Your XLSX is processed in-browser only. Events are created in your Google account.
• You can delete the created events or the entire created calendar at any time in Google Calendar.
• You can revoke the App’s access at any time at myaccount.google.com/permissions.

7) Children’s privacy

The App is intended for general use by students and is not directed to children under 13. If you believe we have interacted with information from a child under 13, please contact us and we will assist with revocation instructions.

8) Changes to this policy

We may update this policy from time to time. We will post the updated version at this URL and update the “Last updated” date above.

9) Contact

Questions or requests: wyattjamesogle@gmail.com

Publisher: Workday to Google Calendar • Website: workday2googlecalendar.com