Privacy Policy
MINGKYME, the operator of GUESS MBTI (the “Operator”), processes personal information only as needed for the service and explains that processing in this policy.
1. Controller and Contact
- Controller
- MINGKYME
- Questions and rights requests
- mingkyme@gmail.com
2. Information We Process
- Google and Kakao sign-in: the sign-in provider, provider identifier (the account ID stored in the service's internal token identifier field), and email address. Temporary authorization codes and access tokens are processed between the provider and the server during sign-in.
- Member profile: the user-entered username, profile MBTI, introduction, and referrer identifier where applicable.
- Friends' guesses: the nickname entered by a non-member visitor, MBTI guess result, optional guestbook message, and submission time.
- Cookies: an HttpOnly session cookie used to keep you signed in, OAuth state and provider-verification cookies, a referrer cookie where that feature is used, and a non-HttpOnly SameSite=Lax language preference cookie. The session cookie may contain a signed form of the provider identifier and email needed for authentication. The language preference cookie stores only ko or en and contains no personal data.
- Automatically generated information: where applicable, the service, hosting, and security infrastructure may generate IP addresses, access records, error and security logs, and browser or device information.
- Usage analytics: When GA4 measurement ID G-V0DT48R4N0 is enabled in production, the service sends sanitized page views and allowlisted interaction events: login started (provider only), profile registered or updated, quiz link copied, quiz started or completed (numeric internal target profile ID and whether a nonblank guestbook was submitted), guestbook submitted, result-history page viewed (page number), and language changed (ko or en). Initial page views may include strictly validated utm_source, utm_medium, and utm_campaign campaign labels. Page locations exclude every query string and fragment; OAuth, unknown, and private paths become safe generic paths. Google may also process access time and device, browser, and approximate-region information. Analytics never intentionally includes names, nicknames, email addresses, MBTI values, introductions, guestbook text, form answers, OAuth data, or arbitrary URL parameters.
- Operational notifications: If a Discord webhook is configured on the server, successful initial profile registration, profile updates, and guess submissions send notifications to the operator's Discord channel. Each notification includes the event type, a cryptographically random event ID, the UTC event time, and a numeric internal user ID; a guess submission also includes a numeric internal guess ID. Registration and update notifications include the owner's saved profile name, introduction, and actual MBTI. Guess notifications include the target profile owner's saved name, introduction, and actual MBTI, clearly separated from the guesser's saved nickname, guestbook message, and guessed MBTI derived from stored answers. Only guess notifications include these saved guess fields. Names, introductions, nicknames, and guestbook messages are escaped and may be truncated to fit Discord's message limit. If the profile lookup fails, the notification omits owner fields; if the guess lookup fails, it omits guess fields, retaining event metadata and any available owner profile. Lookup or delivery failure does not fail a successful submission. Provider credentials or tokens, account emails, and IP addresses are not included. Mentions are disabled. This does not add fields to public profile pages, API responses, browser configuration, or analytics.
3. Purposes of Processing
- Identity verification, sign-in, and session maintenance through Google or Kakao
- Providing profiles and shareable MBTI quizzes and displaying guess results and guestbook messages
- Processing referral relationships and responding to questions and deletion requests
- Diagnosing errors, maintaining security, preventing misuse, and operating the service
- Statistically understanding and improving service usage
4. Retention and Deletion
Information connected to accounts and profiles and submitted content is retained while the service is provided, and is deleted without undue delay when a user requests deletion or the operational purpose ends. Information that applicable law requires to be retained is separated, kept for the legally required period, and then deleted. The app currently has no in-app account deletion feature, so please request deletion by email below.
After reasonably verifying the requester, the Operator deletes the target account and related information from the active database. If backups exist, deleted information may remain only until the backup is safely rotated or destroyed and is not used for ordinary business other than recovery. The Operator does not promise fixed backup or log retention periods that are not implemented, and deletes electronic files so that recovery is difficult once the retention purpose ends.
The sign-in session cookie is used for up to 30 minutes and deleted on sign-out. OAuth state and provider cookies are used for up to 10 minutes to verify sign-in. The language preference cookie keeps the selection until the user changes it or removes it in the browser. Referrer cookies and access or security logs are processed for the period required by the feature and security needs and within the scope of browser, server, or applicable legal rules, and are deleted when no longer needed.
5. Third-Party Provision, Processing, and International Transfers
The Operator does not provide personal information to third parties except with the user's consent, to comply with law, or where strictly necessary to provide the service. During the Google or Kakao sign-in process selected by the user, authentication information is exchanged with that provider under its policies.
When GA4 is enabled, Google's Google Analytics processes the usage analytics described above. This may involve international processing, including transfer to and storage in Google's facilities outside your country, and Google's policies may govern the specific locations and periods. Browser settings or blocking tools may limit analytics requests, although behavior can vary by environment.
When operational notifications are enabled, Discord processes the event metadata and the profile name, introduction, and actual MBTI described above, plus the saved guesser's nickname, guestbook message, and guessed MBTI for guess notifications only, through a webhook to the operator's Discord channel, subject to Discord's policies and possible international infrastructure processing and storage. Notification delivery is separate from service storage and operates on a best-effort basis, so a notification may be omitted or duplicated by an uncertain retry and is not used as the source of truth for service records.
If external processors are used to operate service infrastructure such as servers or databases, the Operator manages processing so it occurs only as necessary and updates this policy as required by applicable law. Because the current service code does not establish a specific hosting company or fixed international-processing terms, this policy does not state an inaccurate provider name or retention period.
6. Your Rights and How to Exercise Them
You may request access to, correction or deletion of, restriction of processing of, or withdrawal of consent for your personal information. Send requests, including account or content deletion, to the email address below. The Operator will act after reasonably verifying your identity, such as through the account email; requests that infringe another person's privacy or rights may be limited. mingkyme@gmail.com
7. Security Measures
The service uses technical measures including HttpOnly and SameSite settings for authentication cookies, Secure settings in production, access-scope restrictions, input validation, same-origin checks for write requests, and exclusion of secrets from public responses. The language preference cookie is not HttpOnly so the client can switch languages, but it contains no personal data and is limited with SameSite=Lax. No transmission or storage method can guarantee complete security, and the Operator reviews measures according to the risks.
8. Children and Young People
Minors should decide carefully with a guardian what personal information to make public and should not enter unnecessary sensitive details such as an address, school, or contact information in a name, introduction, or guestbook message. A guardian may contact the Operator at the email above when needed.
9. Changes to This Policy
If processing practices or applicable law change, this page will be updated and the effective date shown. Material changes will be announced in a reasonably prominent way through the service.
Effective date: September 16, 2026