About this privacy policy
Monash University (ABN 12 377 614 012), Wellington Road, Clayton, Victoria 3800, Australia, operates Monash Guava and GIG HQ for the Global Immersion Guarantee (GIG) Program.
This privacy policy explains the personal information handled by the Guava mobile app and GIG HQ, including program location sharing and technical service data. Read it with the approved privacy collection notice and terms of use and Monash privacy information. It does not change the Program participation conditions.
Information we collect and why
Account and program information includes your name, email address, user ID, profile photo, phone number where provided, enrolment, program assignments and information supplied through your GIG application. We use it to sign you in, administer participation, manage access and communicate with you.
Program records include itineraries, attendance and check-ins, messages, photos and other content you submit. Health and wellbeing information is collected when you provide it, for example in a wellbeing check or message. We use these records to deliver the Program, respond to requests and support safety and wellbeing. Uploaded photos may also contain location or other embedded information.
Location collection and sharing
For real GIG programs, Guava collects student participants’ approximate or precise device location for program safety coordination, check-ins, attendance and emergency support. Automatic program location sharing is limited to the scheduled start and end dates of the student’s assigned program. With the required location permissions enabled, this sharing continues in the background, even when the app is closed or not in use.
Program location information is available to assigned supervisors, authorised Monash staff and Program administrators on a need-to-know basis. In an emergency, relevant information may be provided to emergency services, consular officials, in-country partners, insurers or other people assisting with the response, as described in the approved notice and terms.
Staff do not automatically broadcast their location to Guava’s program location service. A staff member or student can choose to send a one-off location in a chat. The confirmation identifies that all members of that chat can see the shared location. That message remains a chat record; it does not start ongoing chat location tracking. Manual chat shares are separate from the automatic program-date restriction and still require chat access and device location permission.
Guava explains student background location sharing before requesting Android location permission. Android displays an ongoing location-sharing notification while its service is active. For real programs, automatic sharing requires an admitted student with an active assignment and valid scheduled start and end dates. It does not start before the scheduled start or continue after the scheduled end; missing or invalid dates prevent automatic sharing. Guava rechecks eligibility as it handles location updates, and its server rejects automatic real-program location updates outside that window. Device scheduling and connectivity can delay local checks or starting sharing when a program begins. Changing device permissions can stop location collection.
Using a map or choosing a location can also access device location for map positioning or address lookup. This is separate from broadcasting a program location to staff. Demo programs use a separate data environment. Demo Student sharing works only while Guava is open, including outside scheduled dates for demonstrations; Demo Staff do not automatically share. Demo sharing does not run in the background. Mapping-provider processing is described below.
App activity, diagnostics and identifiers
Guava records app activity such as sessions, screens visited, program operations and their outcomes, together with time, app version and release information. Monash uses this information to understand use, investigate problems, maintain reliability and protect the service. Activity records use a project-specific pseudonym for the signed-in account.
Guava’s own error reports include error categories, generic error descriptions, limited stack and app-state context, operating-system information, and app/build/update versions. These reports are designed to exclude chat text, health details, passwords, precise coordinates and arbitrary error text. They can be sent before sign-in so startup failures can be diagnosed.
Guava creates a random app-installation identifier and includes it with check-ins, activity records and diagnostics to help investigate installations and account/device changes. It persists across sign-out and can reset when local app data is removed. Notification services also use registration tokens and service installation identifiers to deliver alerts.
Who processes information
Authorised University staff and organisations supporting the Program use information for program administration, participant support, safety, security and records management. Access is limited by account permissions and role. Information you choose to send in a chat is available to its members.
Google Cloud and Firebase provide application infrastructure, including authentication, databases, file storage, hosting, processing, technical logging and push messaging. These services process the account, program, content and technical data needed to provide those functions. Your sign-in provider also processes the information needed to authenticate you. See Google’s privacy information.
Mapbox provides maps and address lookups. Coordinates may be sent to Mapbox to display or label a location. Its native mapping service also processes location and usage information and related technical identifiers for mapping telemetry and service improvement, subject to its telemetry controls. This processing is separate from the people who can see your location in Guava. See Mapbox’s privacy policy.
Guava does not use this information to serve advertising. Monash does not sell, lease or disclose program location data for commercial purposes.
Your choices and device permissions
You can change location and notification permissions in your device’s settings. Affected features will stop or be limited, and changing permissions does not erase information already collected. Location sharing, check-ins and messaging are Program participation requirements; opting out can affect participation under the approved terms.
The attribution control on a Mapbox map provides access to Mapbox’s telemetry opt-out. That choice controls Mapbox telemetry; it does not by itself turn off Guava’s program safety sharing. Device location permissions and program access separately control Guava location collection.
Only share information needed for the Program. Avoid unnecessary sensitive information, information about other people or confidential material in chats and photos.
Storage, security and retention
University application storage is based in Australia. Some service-provider processing occurs overseas, including the United States for mapping, and may involve other countries used by the provider. Information can also be held on your device and accessed while you travel.
Guava uses encrypted network connections, authenticated access and role-based controls. Some information is stored on your device for offline use. Keep your device and sign-in details secure and report loss, suspected compromise or incorrect access to Monash.
Program location logs, messages and notifications are retained securely for one year after the Program ends for duty-of-care audit purposes. They are then de-identified, destroyed or archived under University records management policies. Other University records may have different legal or records-management requirements.
Monash’s detailed app-activity and diagnostic logging is configured with 30-day expiry. This does not set the retention period for separate Program records, platform service logs or data processed by Google or Mapbox. Service-provider information is handled under the applicable provider terms and privacy information linked above.
Access, correction and deletion
Contact Monash University’s Data Protection and Privacy Office to request access to or correction of personal information, or to raise a privacy concern: dataprotectionofficer@monash.edu.
You can request account and associated-data deletion through the Guava account-deletion page or the Monash feedback form (“I want to delete my app data”). Requests are handled under applicable privacy laws and University records requirements. Deletion is not immediate or unconditional: information needed for duty of care, audits, legal obligations or required records must be retained for the applicable period.
Contact and updates
For help using Guava, contact Monash eSolutions. Privacy enquiries can be directed to the Data Protection and Privacy Office above. This privacy policy will be updated when Guava’s information handling changes.