Privacy

Updated 20 October 2026. This notice describes the information handled by the live GGP application and its account controls.

Public browsing

You can browse institution and programme records without an account. Search terms and filters are sent to GGP to return matching records. Programme searches are served from GGP's canonical Supabase programme-link archive; if it is unavailable, programme results may not load.

Information saved to an account

If you create an account and use saved tools, GGP stores the information you submit for those tools. This can include your name, nationality, residence and preferred language; qualification and academic results; shortlist and application tracker entries; application profiles and drafts; essays, honours, activities, checklists and transfer history; recommendation requests and invitation metadata; submission receipts; budgets, fee-waiver requests and deadline reminders; support, feedback and data-correction requests; notification settings and consent history.

Enter only information needed for your study planning. Do not put passwords, verification codes or another person's private information into study fields.

Browser storage and analytics

The browser stores a GGP sign-in access token and a random first-party browser identifier in local storage. Signing out removes the access token; the browser identifier remains until browser storage is cleared. Use a device you control and sign out on shared devices.

GGP records product events and technical error events using a random first-party browser identifier, event or error type, page or route, and a sign-in flag. When GGP's trusted hosting proxy supplies the visitor GGP uses the random browser identifier to estimate distinct browser profiles; it is not a hardware fingerprint, and clearing browser storage creates a new identifier. Since 20 October 2026, GGP traffic analytics no longer stores raw visitor IP addresses. Earlier traffic records may contain raw IP addresses; they are excluded from the traffic dashboard and have not yet been removed. For abuse prevention, catalogue search uses a keyed hash of the request address and route; these temporary rate-limit records are automatically removed within two hours. Analytics and rate-limit records are stored separately from account records and are not linked to an account user ID.

Service providers and external links

GGP uses Supabase for authentication, database and application hosting. Programme search is served from the canonical Supabase programme-link archive. Opening an institution or other official-source link takes you to that external site, which has its own privacy practices.

Access, export and deletion

Account records are protected by database row-level rules that restrict account access to the matching signed-in user. The account page provides an export of account-linked records and a control to delete learner and application records linked to your account. Deletion removes those records, including consent history, but does not delete your sign-in account or separately stored session analytics. Sign-in credentials and confidential recommendation submissions are not included in the account export. Recommendation records linked to your account are removed with the account-data deletion request.

To access, correct or ask about information, use the Support and data correction form in GGP. You can also sign out to remove the browser's stored access token.

Limits of this notice

This notice describes the current application behaviour. It does not promise a fixed retention period for separate operational analytics. GGP does not submit applications to institutions. Always check current requirements and privacy terms with the institution before sending it information.