Privacy Policy

MyRoster — Google User Data

This section specifically addresses how MyRoster accesses, uses, stores, and shares Google user data across both platforms, in full compliance with the Google API Services User Data Policy and the Google APIs Terms of Service.

Data Accessed

MyRoster for iOS accesses the following Google user data via OAuth with your explicit consent through the Google Sign-In consent screen:

• Google Sign-In (OAuth scopes: openid, userinfo.profile, userinfo.email) — your Google account name, profile picture, and email address. This data is used to identify your account within the app and personalise your experience.
• Google Calendar (OAuth scope: auth/calendar) — read and write access to your Google Calendar, used to sync your shifts as calendar events. This includes event titles, dates, times, and descriptions that you have authorised the app to create.

MyRoster for Android accesses the following device-level permissions and Google services:

• Device Calendar (android.permission.READ_CALENDAR, android.permission.WRITE_CALENDAR) — read and write access to the device's local calendar, used to sync your shifts as calendar events. This accesses the on-device calendar database (which may be synced by Google Calendar on your device) and includes event titles, dates, times, and descriptions.
• Firebase Cloud Messaging — a Google service used to deliver push notifications (e.g., shift reminders) to your device. This uses an anonymous device registration token and does not access any personally identifiable information.
• Firebase Remote Config — a Google service used to deliver app configuration and feature flags. No personal user data is accessed or transmitted.
• Firebase App Check — a Google service used to verify that requests to backend services originate from genuine instances of the app. No personal user data is accessed.
• Firebase Cloud Functions — used to proxy AI-assisted features (e.g., roster interpretation). Requests may include shift-related text you submit within the app. No Google account data is included in these requests.

No other Google account data (such as Gmail, Contacts, Google Drive, or location data) is accessed on either platform.

How Google User Data Is Used

Google user data and Google services are used exclusively to provide the app's core features:

• Identifying your account and personalising your in-app experience using your Google name, profile picture, and email address (iOS)
• Writing your shifts to your Google Calendar so they appear across your devices (iOS via Google Calendar API; Android via device calendar)
• Reading existing calendar events to avoid duplicates when syncing
• Delivering timely shift reminders via push notifications (Android via Firebase Cloud Messaging)
• Applying app updates and feature configuration remotely (Android via Firebase Remote Config)
• Securing backend AI features against unauthorised access (Android via Firebase App Check)

Google user data is not used for advertising, profiling, analytics, or any purpose unrelated to the app's core rostering and wage calculation functionality.

AI Features & Google Data

MyRoster includes optional AI-assisted features (such as roster interpretation) that send user-submitted text to Firebase Cloud Functions for processing (Android). This data is not used to train, improve, or develop any AI or machine learning models — by Google or by me. Requests are processed transiently and not retained beyond the duration of the request.

How Google User Data Is Stored

All Google user data is stored locally on your device only. Specifically:

• Your Google account name, profile picture, and email address are stored locally on your device for in-app display and are not transmitted to any external server (iOS)
• Shift events are written to your Google Calendar (iOS) or device calendar (Android) and are subject to your device's own sync settings
• No calendar data is transmitted to or stored on servers owned or operated by me
• Firebase device tokens and configuration data are managed by Google's Firebase infrastructure and are not stored by me beyond what Firebase requires to operate (Android)
• Uninstalling the app removes locally stored app data; calendar events previously written to your calendar will remain unless deleted manually

How Google User Data Is Shared

I do not share Google user data with any third parties beyond what is required to operate the Google/Firebase services described above. Specifically:

• Your Google account name, email address, and profile picture are not shared with any third party
• Calendar data is not shared with advertisers, analytics providers, or data brokers
• Calendar data is not transferred to any external service or server operated by me
• Firebase device tokens are used only to deliver notifications to your device and are not shared with third parties
• No Google user data is sold, rented, or monetised in any way

Minimum Necessary Data

MyRoster requests only the minimum permissions necessary to deliver its features. On iOS, Google Sign-In and Calendar access is requested only when you choose to sign in with Google. On Android, calendar read/write access is requested only when you enable calendar sync in Settings. Permissions can be revoked at any time.

Revoking Access

You can revoke MyRoster's access to your Google data at any time:

• Google Sign-In & Calendar API (iOS): Visit your Google Account permissions page and remove the MyRoster app. This revokes access to your profile information and Google Calendar.
• Device calendar & notifications (Android): Go to Android Settings → Apps → MyRoster → Permissions to revoke calendar or notification access.

Previously written calendar events will remain in your calendar unless deleted manually. Locally stored profile data is removed when you sign out or uninstall the app.