Privacy Policy

Global SDGs Alliance participant app · Last updated 8 October 2026

Who we are

This app is run by Global SDGs Alliance (全球永續發展聯盟), an incorporated association registered in Taiwan, unified business number 26879192, at 8F., No. 42, Xuchang St., Zhongzheng Dist., Taipei City, Taiwan.

For anything in this policy, contact us at privacy@sdgs-alliance.com. Website: www.gsa.ngo.

What we collect

Account: your email address, a password (stored only as a salted hash by our authentication provider), and the language you choose for the app.
Events you join: which events you belong to, your role in each, how you joined (invite code, link or accepted request), when you joined or left, and when you agreed to that event’s terms.
Requests to join: if you ask to join an event that accepts requests, the message you write with it (up to 500 characters), when you sent it, and the organising team’s decision and any note they add. The organising team of that event sees your request together with your name and photo, even if your directory card is switched off. Before deciding, the organising team may ask you to complete that event’s registration form. Do not include health or other sensitive information in this message.
Reports: if you report another participant, their card or a comment they posted, we record who made the report, who it is about, the event, the reason you choose, anything you write (up to 500 characters) and the time, together with what the organising team did about it. When the report is about a comment, we also keep a copy of the comment as it was when it was reported, even if it is later edited or deleted. If someone reports you, that record is about you as well. Do not include health or other sensitive information about anyone in a report.
Profile: name, preferred name, gender, date of birth, nationality, city, phone number, job title, organisation, biography, profile photo and cover photo.
Contact links: any LinkedIn, Instagram, LINE, WhatsApp or website details you choose to add to your directory card. These fields are optional and start empty.
Health and access: food allergies, dietary restrictions, health notes and accessibility needs, asked for again for each event. These fields are optional.
Travel and safety: flight details, and your emergency contact’s name, phone number and relationship to you, asked for separately for each event.
Event activity: check-in records, saved agenda and bookmarks, form answers, files and photos you submit, poll and vote records, mentor bookings, announcement read receipts, room and group assignment, lost-item reports, and certificate records. Votes in polls are recorded with your name. Other participants cannot see how you voted, but the organising team can, and we keep the record.
Assignments: for assignments that an event’s organising team sets, your answers, the files and photos you upload, the links you add, and when you, or someone in your team, turned the work in or took it back. Where an assignment is graded, the grade (pass or fail, or points) and any note the organising team writes when they return the work or ask you to resubmit it. The organising team may also keep notes about your work for themselves; those notes are not shown to you in the app.
Comments on assignments: questions and replies you post in an assignment’s public Questions section, and private comments between you (or your team) and the organising team, together with when each was posted, edited or deleted.
Device: if you allow notifications, a push notification token, whether your device is iOS or Android, and, where the app records it, the language the app is set to on that device, so that notifications reach you in that language.
Guardian link: for participants under 18, the link to a guardian’s account where one has been created.
Error diagnostics: when a screen in the app stops working, the app writes a record to our database so that we can find and fix it. That record contains the error message, the technical stack trace, which screen failed, whether you were on iOS, Android or the web, how many times it happened, and your user ID. It is not designed to contain anything you typed, and it does not contain your device model or browser fingerprint.
Abuse protection: to limit repeated attempts at check-in codes, invite codes, account claiming, reports and comments, we keep counts of attempts, keyed to your user ID or, if you are not signed in, to a hashed form of your network (IP) address rather than the address itself.

We do not collect your location. We do not use advertising, analytics or tracking services of any kind, we do not sell or trade your data, and we do not use it for automated decision-making.

How we use it

We use this data to run the events you join: to register you, let you join events by code, link or request and let an event’s organising team review requests, check you in, publish the agenda, assign rooms and transport, handle forms, assignments and submissions — including grading and returning work, and the comments on it — handle reports about participants, their cards or their comments, send you event notifications, cater for your dietary and accessibility needs, reach your emergency contact if something happens, report attendance totals to the partners who funded each event, and keep a long-term record of who took part and what they contributed so that we can measure the difference our programmes make. We process it to perform our agreement with you as a participant, and to keep participants safe. Your health and accessibility information we use on the basis of your consent. The participant directory we run because connecting participants to each other is one of the reasons our events exist — your card is on unless you switch it off, which you can do at any time under Profile › Settings › Digital card.

Telling you about future events. When you sign up you can tick an optional box to hear about future Global SDGs Alliance events. This is separate from running the events you join, so we do it only if you tick it, and we record that you did along with the date. Leaving it unticked changes nothing else. You can change your mind at any time by emailing privacy@sdgs-alliance.com and we will stop; every message we send will also tell you how to stop. We have not sent any such message yet.

Most fields are optional, but some things will not work without them: without dietary or accessibility information we cannot cater for you or arrange adjustments, and without flight details we cannot arrange airport pickup.

Health, dietary and accessibility information

Food allergies, dietary restrictions, health notes and accessibility needs are sensitive personal data under Article 6 of Taiwan’s Personal Data Protection Act and Article 9 of the GDPR. These fields are optional — you can leave them blank. We ask for your consent for each event: when you register for the event where registration is used, and in the app when you give us your details for that event. That consent covers that event only.

We use this information to run that event safely for you: to brief caterers so that meals are safe and suitable for you, to arrange accessible rooms, venues and transport, and to respond if you need medical help. In a medical emergency we may pass the relevant details to medical or emergency personnel — the law permits this to protect your life or health, and we will do it whether or not we can reach you at the time. It is available to that event’s organising team, and the relevant parts are passed to the partners who help them run the event — such as caterers, venues, and accommodation and transport providers. It is never shown to other participants.

While the event is open you can change or clear it in the app — clearing the fields is the simplest way to withdraw your consent — and at any time you can ask us to remove it. If you do so before or during the event, we may no longer be able to accommodate the need it described.

Who can see it

Other participants. Your directory card is on by default, so that participants can find each other — that is a large part of why our events exist. While it is on, people taking part in an event you have also joined can see your name, photo, cover photo, biography, nationality, role, job title, organisation, and any contact links you have added (LinkedIn, Instagram, LINE, WhatsApp, website). Your job title and organisation are shown by default — you can switch either of them off individually under Profile › Settings › Digital card. Contact links are optional and start empty, but once added they are shown whenever your card is on — they are not covered by those per-field switches. Your phone number is the one field that starts switched off; it appears only if you turn it on. You can switch the whole card off at any time. Whether or not your card is on, the other people taking part in the same event can see your name and the group you have been placed in — that is how groups find each other. Nothing else is shown unless your card is on.

Roommates. If you are sharing a room, the people in it can additionally see your room number. They can see your phone number only if you turn on the separate “share my phone with roommates” setting on the Accommodation screen, which starts switched off.

Assignments. Your answers, files, links, grade and the notes the organising team gives you on your work are seen by you and that event’s organising staff — and, for a team assignment, by the other members of your team — but not by other participants. The organising team may grade your work before returning it; until they return it, the grade is seen only by them. Notes the organising team keeps for themselves are seen only by them. Private comments are seen only by you (or your team) and that event’s organising staff. Questions and replies in an assignment’s public Questions section are seen, with your name, by everyone in that event who can see the assignment — including people who are not asked to hand it in, such as staff and guardians. People taking part in an event may include participants under 18, so do not post your own or anyone else’s contact details or other personal information there. The organising team can remove any comment in their event; a removed comment, like one you delete yourself, is replaced by a note that it was deleted.

Anonymous assignments. If an assignment is marked anonymous, your answers to its questions are stored without your name or user ID, so the organising team cannot see which answers are yours. They can still see whether and when you turned it in. Files or links you attach, and comments you post, are not anonymous. In a small group, or from what you write, an answer may still be traced back to you. Because these answers are not linked to you, we cannot find or delete them for you later, including when you close your account.

Organising staff. Accounts that an event has marked as staff, organiser or administrator can see and update the records of that event’s participants, including the health, dietary, travel and emergency-contact information described above, and the requests sent to join that event. A small number of platform administrators, who run the app itself, can see and manage the records and files of every event. The web admin site is restricted to event organisers and administrators and to platform administrators; the other staff-level roles work through the app. We do not want to overstate the separation: within an event, these roles are not separated from one another by what they can read — with one exception, reports, described next.

Reports are seen only by the organisers and administrators of that event and by platform administrators — not by other staff, and never by the person the report is about. We do not tell the person who was reported who made the report, unless the law requires it.

Your health, dietary, accessibility, travel, emergency contact and form data is never shown to other participants. Your assignment work and grades are not shown to other participants either, apart from the members of your own team for a team assignment.

Who we share it with

We use Supabase, Inc. (database and sign-in), Cloudflare, Inc. (file storage and web hosting), Resend (delivery of account emails such as address confirmation and password resets), and Expo, Apple and Google (push notifications and app distribution). They process data on our behalf under their service terms and data-processing terms, and may use it only to provide those services to us. Their servers are outside Taiwan, including in Singapore, the United States and the European Union, so your data is transferred internationally. We may also disclose data where the law requires it or where necessary to protect someone’s safety.

Beyond these service providers, the relevant parts of the information you give for an event are passed to the partners who help run that event — such as caterers, venues, and accommodation and transport providers — and, in an emergency, to medical or emergency personnel.

How long we keep it

Your account is designed to carry across events, so that you do not have to register again for the next one. That means two different things happen to your data:

Your account — sign-in details, name, contact details, directory card, profile photo, language setting and the list of events you have joined — is kept for as long as you have an account with us, so that you do not have to register again for the next event. If you do not sign in for five years we treat the account as finished and delete it. You can delete it yourself at any time.
Information we collect for a particular event — food allergies, dietary restrictions, health notes, accessibility needs, flight details and your emergency contact — is deleted one year after that event ends. The year is there so that anything arising from the event — an accident, an insurance claim, a dispute — can be dealt with while the records that explain it still exist. We ask again for each event rather than carrying it forward, because these things change and out-of-date information is worse than none: a kitchen with no allergy record will ask you, but a kitchen with the wrong one will not. Leaving an event does not change this: the information you gave for that event is kept, and deleted, on the same timetable as everyone else’s for that event. If you want it deleted sooner, email us or delete your account.
Requests to join an event — the message and the decision — are deleted together with the information we collect for that event, one year after the event ends, or when you delete your account if that is sooner.
Reports — deleted with the other information for that event, one year after the event ends, together with any copy of a reported comment. They are kept until then even if the person who made the report, or the person it is about, deletes their account first.
Comments on assignments — kept until five years after the event ends, then deleted or de-identified. You can delete a comment you posted at any time while you are still in that event, or ask us to. If you close your account, the comments you have not deleted stay where they are, shown as written by “Deleted account” instead of your name.
Grades and the organising team’s notes on your work — the grade and any note the organising team gave you when they returned your work or asked you to resubmit it, and the notes they kept for themselves, are kept until five years after the event ends, then deleted or de-identified. Until then they stay with your name attached even if you close your account.
What you took part in and what you submitted — check-in records, your answers to forms, surveys, assignments and questions, a record of the work you submitted (the uploaded files themselves are deleted when you close your account) — is kept as part of our long-term programme record, with your name attached. We use it to account for events to our partners and funders, to measure the difference our programmes make over the years, to reissue certificates, and to credit contributions to the people who made them. We may keep it for as long as we run this programme, unless the organising team removes the task or form it belonged to. This layer survives closing your account — your name stays attached to it, because a programme record that cannot say who did what is not a record. Work for a team assignment, including its files, belongs to the team: it stays with the team when one member closes their account, without that member’s name on it. Everything else about your account is deleted, apart from the technical records described above (error diagnostics and abuse-protection counts), which may still carry your user ID, any reports you made or that were made about you (described above), comments you posted on assignments and did not delete (described above), and the record of consent described below. If you want this layer removed as well, email privacy@sdgs-alliance.com and we will do it; you will not be able to have a certificate reissued afterwards.
Push notification token — while you have notifications enabled on that device. It is removed when you sign out.
Error diagnostics — we delete these after each event and its follow-up are finished, and we hold at most 5,000 records at any time. They are not part of the programme record, so they are not kept long-term. We do this by hand rather than on a timer, so we are not going to promise you a specific day.
Record of consent — when your account is deleted, we keep a record that it agreed to our terms and to each event’s use of its details, and whether it agreed to hear about future events: the account’s internal ID, the versions agreed to and the times, without your name or email address. We keep it for five years after the account is deleted so that we can show that consent was given if that is ever questioned, and then delete it.

We may keep records for longer where the law requires it, or where they are needed to establish or defend a legal claim.

Your choices, and deleting your account

You can change or clear most of your information yourself in the app at any time.
You can withdraw your agreement to the optional fields by clearing them, and turn off notifications in your device settings.
You can ask us to see, correct or delete your data, or to stop using it, by emailing privacy@sdgs-alliance.com. This includes asking for a copy of the notes the organising team has kept about your assignment work, including notes they keep for themselves and do not show you in the app.
To leave a single event without closing your account, open Profile › Settings › This event and choose Leave this event. You stop being a participant of that event and stop appearing in its directory; your account and your other events are not affected. After you leave an event, that event’s organising team can still see your records for that event until they are deleted, one year after the event ends. If the organising team removes you from an event instead, they can no longer see your records for it, although platform administrators can until they are deleted. Either way, you will no longer be able to see them in the app yourself; email us if you want a copy. What happens to the information you gave for that event is described under “How long we keep it”.
To delete your account, open Profile › Settings › Delete account in the app. Your account is switched off immediately and deleted permanently seven days later; during those seven days you can sign in and cancel. You can also email privacy@sdgs-alliance.com from the address you signed up with instead — we may ask you to confirm your identity first, and will complete the deletion within 30 days. Either way, the programme record described above stays with your name attached unless you ask us to remove it too; grades and the organising team’s notes on your work stay with your name attached until five years after the event ends; comments you posted on assignments stay, shown as written by “Deleted account”, until five years after the event ends, unless you delete them first; and records we are legally required to keep, or that no longer identify you, may remain. A record of what your account consented to is kept for five years, as described under “How long we keep it”.

We answer requests to see or copy your data within 15 days, and requests to correct, stop or delete within 30 days, as Taiwan’s Personal Data Protection Act requires; either period may be extended once for complex requests. The first request is free; we may charge the necessary cost for repeated or excessive requests. If the GDPR applies to you, you also have the right to restrict or object to processing, to receive your data in a portable format, and to complain to your data protection authority.

Security

Traffic is encrypted with TLS, passwords are stored only as salted hashes, and access to records is controlled in the database rather than only in the app. Files you upload are served by web address, so anyone who has that address can open the file without signing in. No system can be made completely secure; if a breach occurs that is likely to affect you, we will notify you and the relevant authority as the law requires.

Changes

If we change this policy we will update the date at the top of this page, and tell you in the app or by email if the change materially affects you; for a significant change, the app will ask you to accept the updated terms before you continue.