Privacy Notice · 개인정보처리방침

Who operates this service

MyGSB (schedule.mygsb.net) is an internal scheduling and events tool of SKK Graduate School of Business, Sungkyunkwan University. This privacy notice is effective as of 2026-08-14.

The operator of MyGSB is Frank Huettner (SKK GSB). For every privacy matter concerning this service, including questions, access, correction, and deletion, please contact the operator at huettner@skku.edu. Privacy matters that concern the whole university, rather than this service specifically, are governed by Sungkyunkwan University's own privacy policy and privacy office.

Our principles

MyGSB follows a small set of data-protection principles, and the rest of this notice explains how each principle is put into practice.

• Data minimization: We collect only the information the service actually needs to do its job.
• Purpose limitation: We use the information we hold only to run course scheduling and events, and for nothing else.
• Encryption: All information is encrypted, both while it is stored and while it travels over the network. The most sensitive fields (your Google Calendar authorization tokens, your personal contact address, and your dietary preference) carry a second layer of encryption on top.
• Data residency: The database and the uploaded files that hold this service's information are stored in South Korea.
• Proactive deletion: When a person leaves SKK GSB, we delete that person's data ourselves, without waiting for a request.
• No sensitive data and no behavioural tracking: We do not collect sensitive personal information such as health or religion, and we do not track your browsing or use advertising cookies. The one place we record an IP address is an internal access log of administrative access to other people's data, kept as a legal security measure (see Security).
• Transparency: We publish this notice and keep it current.

What we process, and why

• Faculty and staff (signed-in users): For each signed-in user, we hold the display name and the @g.skku.edu login email that come from that user's Google account. In addition, we hold optional profile fields that the user enters personally: a preferred (display) name, a single contact email address (a notification address used for all mail the service sends the user, including event invitations), the user's scheduling preferences, and a coarse dietary preference (none, vegetarian, or vegan, with no free text) that is shared only with the event managers of events the user attends. We also hold records that the school maintains about the user: the user's roles and teaching assignments, the user's start date, and the user's event invitations and RSVP status. This contact email address may be a private address, is never shown to other users (rosters and event managers see the institutional address), is used only for notifications and event invitations, and carries a second layer of encryption, as does the dietary preference (see Security).
• Calendar connection (optional): If a user connects Google Calendar, MyGSB stores that user's Google authorization so it can keep the user's class schedule and the events the user is attending in sync. This authorization is deliberately narrow: MyGSB can only create and update a calendar that MyGSB itself makes for the user, and it cannot read or change any of the user's other Google calendars or events. Because this authorization acts as a login credential, it carries a second layer of encryption (see Security). Disconnecting Google Calendar, or deleting the account, removes the stored authorization.
• External instructors: For an external instructor, we hold only the instructor's name and a non-functional placeholder identifier, kept so that the schedule can attribute sessions to that instructor. External instructors are not users of this service: they cannot sign in, they are never contacted, and we neither collect nor use their real contact addresses.
• Students: For a student who is enrolled and signed in, we hold the display name and the @g.skku.edu login email from the student's Google account, the student's cohort membership, and, for events the student is invited to, the RSVP status. As with staff, a student may optionally enter a preferred name, a single contact email address (which may be private, is never shown to other users, and is used only for notifications and invitations), and a coarse dietary preference (none, vegetarian, or vegan, with no free text) for event catering, shared only with those events' event managers and stored with a second layer of encryption. We hold no grades, transcripts, or other academic records: MyGSB is a scheduling and events tool, not a student records system. Before a student's first sign-in, when they have only been added to a cohort's roster, we hold no name for them and no readable email address. Instead we store a one-way cryptographic hash of their university email together with the cohort assignment, used only to recognise them as allow-listed when they sign in. A student's profile is created only when they first sign in with their @g.skku.edu account and grant the required consent.
• Technical data: We use only functional cookies and local storage, namely a signed session cookie that keeps a user logged in, a small user-interface cookie that remembers the sidebar state, and local storage that remembers display preferences such as light or dark mode and whether you have dismissed an in-app notice. We use no tracking or advertising cookies. A user can block or clear these in the browser, but without the session cookie that user cannot sign in. We do not store profile photos or browser user-agent strings, and ordinary browsing is not logged with an IP address. Server logs and error reports have secrets and credentials removed, and email addresses are automatically detected and removed even where they appear incidentally; other than an internal identifier, we do not add personal data such as names or IP addresses to them. Separately, an internal administrative access log records the IP address of a manager's or superuser's access to other people's personal data, as a legal security measure (see Security).

We process this information to operate the school's course-scheduling and events service, and we ask for your explicit consent to it when you first sign in. That consent screen covers the required items the service runs on (your name and @g.skku.edu email from your Google sign-in, your roles and cohort or teaching assignments, the resulting schedule, your event RSVP status, and sign-in and access records). It is never pre-ticked, it shows what is collected, what it is used for, and how long it is kept, and it states the consequence of refusing: these items are required to run the service, so without this consent MyGSB cannot be used, and there is no other disadvantage. You can withdraw this consent at any time on your Settings page; MyGSB is then blocked until you consent again, while downloading your data and requesting account deletion remain available from the consent screen without re-consenting. Independent of this consent, the underlying relationships remain documented supporting bases: for faculty and staff the employment relationship (PIPA Article 15(1)(4), the performance of a contract with the data subject) supported by the school's statutory duties as an educational institution (Article 15(1)(3)), and for students the school's statutory education duty (Article 15(1)(3)) supported by the enrollment relationship (Article 15(1)(4)). Where a field is optional, providing it is voluntary. For your personal contact email address and your dietary preference we ask for a further, separate consent where you enter them: a checkbox per purpose on your Settings page, never pre-ticked and never bundled with the required consent, showing the same disclosure items and that refusing these has no disadvantage at all. You can withdraw such a consent at any time by unticking the box and saving, which immediately deletes the stored value. We keep a record of all these consents (the fact, the text version you saw, and the timestamps, never the value itself) so we can demonstrate them. A preferred name and scheduling preferences remain simple voluntary entries, used only for the purpose shown where you enter them. Connecting Google Calendar is likewise based on your consent, which you can withdraw at any time by disconnecting. We do not ask for a Korean resident registration number (주민등록번호) or any other national identification number (we do not collect student or staff numbers either), and we collect no sensitive-category information.

Retention and deletion

We keep a person's data for as long as that person is affiliated with SKK GSB and the service still needs the data. When a person leaves SKK GSB, the operator deletes that person's personal data promptly and without waiting for a request; records that are under a legal hold or a statutory retention duty (for example the access log) are kept for their required period. Deletion happens in two steps: the person is first marked as departed, and the person's data is then deleted permanently, including the profile, the login, any stored calendar tokens, the roles, the memberships, and the RSVP records. Content that the departed person created remains in the service, but without that person's name attached. A person may also request deletion at any time. Beyond deletion tied to a person, we also apply fixed time limits: an event's RSVP records (the invitation and reply rows linking invitees to that event) are deleted 24 months after the event has ended or been cancelled, and a student's cohort-membership record is kept with its final status (graduated or withdrawn) for historical attribution and then deleted 24 months after that. RSVP records are also removed together with the person or the event whenever that happens sooner.

Where your data is processed (PIPA Articles 26 and 28-8)

MyGSB's database and the files uploaded for event pages are stored in South Korea, on AWS (Amazon Web Services Korea LLC, Seoul region). Some of the providers that run the rest of the service are located outside South Korea, so operating MyGSB also involves cross-border processing of personal data. The table below lists, for each overseas recipient, the items transferred, the country, when and how the transfer happens, and the purpose and retention period.

Each recipient publishes its own privacy contact in the privacy policy at the linked domain. A user may refuse this overseas processing by choosing not to use the service and by asking the operator to delete that user's data; because MyGSB runs on this infrastructure, the service cannot be provided without these providers. Under PIPA Article 26, AWS (Amazon Web Services Korea LLC) and Cloudflare act as our processors under data-processing agreements, entrusted with processing personal data on our behalf and bound to process it only on our instructions: AWS keeps the database and the uploaded files in South Korea, and Cloudflare runs the application layer described above. Google is different: it is engaged through the university's own Google Workspace agreement, not a separate MyGSB entrustment. Outbound email (notifications and event invitations or reminders) is sent through the university's own email service, the mygsb@skku.edu mailbox on NAVER Works, which necessarily receives the recipient's email address and the message content (such as event details) in order to deliver the message. Like the Google Workspace above, this is the university's own email infrastructure, a domestic Korean service, not a separate MyGSB entrustment; MyGSB configures only the sending account.

Your rights

On your Settings page you can view and edit your own profile fields, withdraw the optional consents described above by unticking them (withdrawing the required-items consent is a separate button there, and blocks MyGSB until you consent again), download a copy of all the data MyGSB holds about you, and request permanent deletion of your account and its data. You may also email the operator to exercise your right of access, correction, deletion, or suspension of processing, and the operator will handle such requests promptly. Beyond contacting the operator, a data subject may also contact the Personal Information Infringement Report Center (privacy.kisa.or.kr / 118) or apply for dispute mediation to the Personal Information Dispute Mediation Committee (kopico.go.kr / 1833-6972). If a data breach affects you, the operator will notify you without undue delay, and in any case within 72 hours.

Security

All information is encrypted while it travels over the network and while it is stored. The most sensitive fields, namely your Google Calendar authorization tokens, your personal contact email address, and your dietary preference, carry a second layer of encryption on top, so that access to the stored data alone is not enough to read them. Names and schedules must stay readable for the service to do its job, so those are protected instead by access controls, by keeping credentials in a managed secret store, and by removing personal data from logs and error reports. Consistent with our principles, we deliberately collect as little as possible: no photos, no health or religious information, and no tracking of your everyday use of the service.

Administrative access to other people's personal data is recorded in an internal access log. For each such access we record the staff account, the time, the source IP address, the action taken, and which data was involved. This log exists to meet a legal safety-measure duty (keeping a record of who accessed whose personal data); it can be read only by a designated auditor and by system administrators, and it is retained for at least 12 months. Within this log, access-authority records (role grants and revocations, per-event access grants, and the employee-account lifecycle) are retained for at least 3 years, as the access-control safeguard requires. Your own access to your own profile is not recorded, and ordinary members (instructors and students) generate no such records as long as they cannot reach other people's data; where an event's manager grants a staff member access to that event's participant list, that person's access is recorded the same way. The consent choices you make for optional profile fields are not part of this log either; they live in the separate consent record described under “What we process, and why” (facts, text version, and timestamps only, never the stored values).

Changes

When we make a material change to this notice, we announce the change inside the app, and the change takes effect with a new effective date shown on this page. This notice is effective as of 2026-08-14.