GULFHE Fellowship Privacy Notice
GULFHE Fellowship processes personal information to administer applications, conduct assessment and quality assurance, manage payments, issue credentials, handle enquiries and protect the integrity of the recognition scheme.
Who this notice covers
Applicants, supporters, verifiers, reviewers, moderators, institutional coordinators, recognised credential holders and people who contact the Fellowship Office.
Information we may process
Identity and contact information; organisation and professional context; application narratives and evidence; supporter and verifier information; payment and transaction references; reviewer and moderation records; accessibility information where voluntarily provided and necessary; complaints, appeals or integrity records; and credential/standing information. Raw payment-card details must not be stored by the Fellowship website.
Why information is used
To create and manage accounts; assess eligibility and applications; verify evidence; manage conflicts and quality assurance; process fees; communicate decisions; provide reasonable adjustments; issue and verify credentials; manage appeals, complaints and integrity concerns; meet legal and governance obligations; and improve the service using proportionate, non-sensitive analytics.
Sharing and access
Access must be role-based and limited to people or service providers who need the information for an authorised purpose. Institutional coordinators must not receive confidential application evidence or reviewer reports merely because an institution paid the fee.
Retention and international processing
Publish the approved retention schedule and any applicable international-transfer safeguards after legal/privacy review. Do not use indefinite retention wording. Assessment evidence, financial records and credential records may require different retention periods.
Your choices and rights
Provide the applicable privacy-rights route, correction process, directory opt-in/opt-out control and privacy contact. The exact legal-rights wording must be confirmed for the jurisdictions in which applicants are accepted.
Developer privacy controls
Do not place marketing pixels or session replay on application narratives, evidence, payment or reviewer screens. Minimise form fields, encrypt data in transit, enforce role permissions, maintain audit logs and keep evidence out of ordinary email.