길잇 개인정보 처리방침

gilit Privacy Policy (English summary)

Effective November 5, 2026 (announced November 5, 2026). The Korean version prevails.

Maim Haim Co., Ltd. operates the gilit app and processes personal information under the Korean Personal Information Protection Act and the Network Act. This summary follows the structure of the Korean policy; where they differ, the Korean text applies. It describes what the current app version (1.0.0) and server actually do; features not yet opened are marked "in preparation".

• At a glance: required for the service: your email address (stored encrypted; accounts are keyed by a one-way identifier derived from it), an app-generated device identifier, OS type and app version, security audit records, consent history, pseudonymous usage events and activity records. Optional: name, gender, mobile number and business card details (company, title, card email, card and profile photos). If you grant Bluetooth and location permission: your position inside the venue and booth visit records. While your card screen is open, nearby users with the card screen open can see your name, company and title; the participant you choose to exchange cards with receives your card details and the booth you were at. Hosting is outsourced to Amazon Web Services (Seoul region); AI booth recommendations and participant classification are generated by OpenAI, L.L.C. (USA). Contact: Taesoo Chang (CEO), achang@maimhaim.co.kr.
• Purposes (Art. 1): sign-up and sign-in, indoor navigation, booth recommendations, business card exchange, syncing your interests and saved booths across devices, service improvement statistics and participant classification for event operations, security and dispute handling, customer inquiries, and marketing messages only to users who opt in (sending is in preparation).
• Data we process (Art. 2): required for the service, agreed to on the sign-up screen under "[Required] Collection and use of personal info": your email address (from November 5, 2026 it is stored encrypted when you log in and used for sign-in codes, account identification, essential service notices such as policy changes and security or breach notices, and identity checks when you contact us; accounts are keyed by a one-way identifier derived from it, and accounts created earlier that have not logged in since hold only that identifier; the operator console shows the address only in masked form; it is passed to the mail processor to send sign-in codes), the app-generated device identifier, OS type and app version, security audit records (sign-in code issue and failure, device registration and revocation, consent changes and account deletion events; the IP address is recorded for code, device registration and deletion events), consent history, usage events (screen and button names, tap position on the screen, OS type, app version, a per-launch session identifier, truncated IP, and an 8-character identifier derived from your name and phone or account identifier, never the raw values; collected before login as well) and inquiry emails. Optional: name, gender and mobile number (profile step after sign-up, can be skipped), business card details (card edit screen), your in-venue position and booth visits (only after you grant Bluetooth and location permission, Art. 10) and marketing opt-in status (Art. 9). Generated while you use the app after logging in: interests, saved booths and sessions, display language, notes on received cards (visible only to you), card exchange records (including the event and booth where you met), classification tags and categories that we derive from the company and title on your card, activity records (booth views, saved booths, navigation start and end and map opens with your in-venue position at that moment, and card exchanges with the counterpart's one-way identifier; booth and place search terms are in preparation and will be added from app version 1.0.1, which ships after this policy takes effect) and event entry and exit records (event, time, direction, decision, gate identifier, device identifier and report sequence, app version and the beacon signal strength at the time, if any; created when you enter or leave an event from the list and when the app leaves automatically after the event ends). Operators may view individual activity records for troubleshooting; statistics shared externally are aggregated. We do not collect GPS coordinates, advertising identifiers, your contact list, date of birth, passwords, payment data or biometric data; profile photos are stored as uploaded and no facial features are extracted.
• Retention (Art. 3): profile and card data until you delete your account; the member row (one-way identifier, sign-up and deletion dates, sign-up channel) 3 years after deletion, deleted together with the consent history; device sign-in tokens expire after 180 days, and expired registration rows are purged daily 180 days after expiry; sign-in codes 3 minutes; in-venue position records 7 days after the event ends (the last known booth is cleared 7 days after reports stop); activity records (including the coordinates recorded at navigation start and map open) 3 years, with your identifier replaced by a random value when you delete your account; entry and exit records 90 days; usage events 90 days; user security audit records 1 year; operator console access and edit or delete audit records 1 year; consent history 3 years after account deletion; inquiry emails 3 years after handling; AI recommendation requests cached in server memory for 10 minutes; database and disk backups 7 days, server file backups 30 days, and earlier versions of deleted photos expire after 1 day.
• Third parties (Art. 4): while your card screen is open, other users at the same venue who open their card screen see your name, company and title (no contact details or booth); this stops within 15 minutes of closing the screen, and nothing is shown for users who do not open the card screen. When you send a card request, the recipient receives your name, company, title, the classification tags we derived and the booth you were at; after acceptance both sides also receive mobile number, card email and photos (through 10-minute signed URLs), and the accepting user's booth at the time of acceptance is shared with the requester. Sending or accepting a card is your consent to that disclosure; nothing is shared if you do not send or you decline. The "discoverable" switch below the in-app privacy policy stores a "can be found" flag on the server (server default: on). The current app has no screen that lists participants, so inside the app this flag does not show your name, company or booth to other users as a list; however, the server still has a lookup function that returns the name, current booth and last report time of discoverable users to other logged-in users, so turn the switch off if you do not want this. We intend to close that lookup function until a participant lookup screen opens. The switch does not affect the nearby display while your card screen is open. A participant lookup screen is in preparation and will be announced in this policy with separate consent before it opens. Event organizers never receive individual-level data, the console has no export to organizers, and there are no exhibitor (booth staff) accounts or screens. Operator console accounts are issued only to our employees. We disclose data to authorities only when the law requires it.
• Processors (Art. 5): Amazon Web Services, Inc. (Seoul region) for server hosting, database and photo storage, sign-in code email and backups; OpenAI, L.L.C. (USA, cross-border processing, see Art. 6).
• Cross-border transfer (Art. 6): to OpenAI, L.L.C. (USA, privacy@openai.com) over TLS from our server: (1) when you ask for AI recommendations, your chosen interests and the event's booth list; (2) when an operator runs participant classification for an event, the company and title on your card. Your name, contact details, one-way identifier and location are never sent. Retention follows OpenAI's API data policy (by default, kept up to 30 days for abuse monitoring and not used for training); we have not set separate retention terms. You can avoid (1) by not choosing interests and (2) by leaving company and title blank; deletion of existing tags or transferred content can be requested as described in Art. 8. Every other feature still works. Requests from users who are not logged in contain only interests and booth lists with no identifier and cannot be linked to a specific person.
• Deletion (Arts. 7 and 14): usage events and activity records are purged daily; position records (7 days after the event), entry and exit records (90 days) and audit records (1 year) are also purged daily, as are expired device registrations and, 3 years after deletion, the consent history and member row. When you delete your account we revoke all tokens, delete your photos, card exchanges, current booth, interests, saved booths and classification tags, replace your name with the server's "withdrawn member" value, clear company, title, gender, phone, login email, card email and photo fields, set "discoverable" to off, anonymize your activity records and delete the app's account data stored on your phone (the device identifier and unsent usage events remain). Consent history and the member row (one-way identifier, sign-up and deletion dates, sign-up channel) for 3 years, anonymized activity records (3 years), position records (7 days after the event, with the one-way identifier), entry and exit records (90 days, with device and one-way identifiers), user audit records (1 year, with IP for code, device registration and deletion events) and usage events (90 days) remain until their periods end, as do backups for up to 30 days and earlier versions of deleted photos for 1 day. Signing up again with the same email creates a new account that is not linked to the old records; because the one-way identifier can be recomputed from the address, the remaining records are still protected as personal information.
• Your rights (Art. 8): access, correct, delete, suspend processing or withdraw consent at any time, in the app (My tab for your profile; the switches below the privacy policy under My > Settings > Terms and policies for marketing and "discoverable"; Settings for account deletion) or by email from your sign-up address to achang@maimhaim.co.kr. The "location records" switch next to those switches has no effect in the current version (turning it off does not stop collection); to stop in-venue location collection, use the method in Art. 10. Account deletion requests are handled within 7 days and other requests answered within 10 days. Legal representatives may act with the power of attorney form prescribed by the enforcement rules. Required items can be stopped by a suspension request or account deletion. Company, title, card email and photos are withdrawn by clearing them on the card edit screen; name, mobile number and gender cannot be cleared in the current app and are removed on request by email or by deleting the account. The policy is available without logging in from the "view" link on the sign-in screen and at maimhaim.co.kr/gilit/privacy. We are not subject to the data portability obligation under the Enforcement Decree.
• Marketing messages (Art. 9): we currently send none and store only your opt-in status and timestamps, set on the sign-up screen ("[Optional] Marketing messages") or the "marketing messages" switch below the in-app privacy policy. Once sending starts, marketing emails go to your stored login email address; before that we will announce here and in the app what we send and by which channel; consents collected so far will be re-confirmed before use. When we start sending: email only (app push and SMS are not available and would need separate consent, including for 9 p.m. to 8 a.m. delivery), subjects marked with the Korean-language advertisement label required by law, sender name, email, phone and address shown, no sending between 9 p.m. and 8 a.m., an unsubscribe link that works without logging in, consent re-confirmed every 2 years and opt-outs processed within 14 days. You can opt out now with the switch or by email. Declining never limits the service.
• In-venue location (Art. 10): your position is computed on your phone from venue beacon signal strength and motion sensors, never GPS; the phone sends the coordinates and the three strongest beacon signals to our server every 5 seconds, and the server determines which booth you are at. The report also carries calculation aids such as step count and heading, which the server discards. Collection happens only while you are logged in, have granted Bluetooth and location permission, are inside an event, the app is in the foreground and venue beacons are in range, on any tab. There is no background collection and no separate location consent screen beyond the permission prompts; the "location records" switch below the in-app privacy policy has no effect in the current version (turning it off does not stop collection) and will be fixed or removed in the next app version, so use the permission settings described below to stop collection. Items: floor-plan coordinates with estimated error, zone and booth code, the three nearest beacons and their signal strength, timestamps, the booth the server determined and the previous booth, and the coordinates at navigation start and map open. Purposes: indoor navigation, visit records, navigation quality checks and aggregated event statistics; position records are deleted 7 days after the event ends, and the last known booth is cleared 7 days after reports stop (any statistics are aggregated before then and no individual records are kept), while the coordinates inside activity records are kept with those records for 3 years and anonymized when you delete your account. The only third-party disclosure is the booth you were at when you send or accept a card request (for the "discoverable" flag and the remaining server lookup function, see Art. 4). Our operators may view individual trails and venue heatmaps for quality checks and incident handling; trail deletions are audit-logged for 1 year. You can pause at any time by turning off Bluetooth or location permission in your phone settings, ask us to delete your trail earlier than the 7-day purge, and request access or correction; we answer within 10 days.
• App permissions (Art. 11): no permission is mandatory. Bluetooth scan and connect and location (fine and coarse on Android; "while using" on iOS) are requested when you first open the map tab to read beacon signals; Bluetooth advertising when you first open the card screen to broadcast a short identifier; camera for QR codes and card or profile photos; photo library for choosing photos; motion sensors need no separate permission on Android, and on iOS a motion permission prompt may appear when the step sensor is first used. The current version does not request notifications, microphone, "always" location or contacts; iOS nearby interaction (UWB) is only checked for device support without opening a session, so it is designed not to show a permission prompt, and the Bluetooth background mode is for state restoration only. Permissions can be changed in system settings.
• On-device only (Art. 12): the current version has no interest note input and no recording feature (both in preparation); if a version offers them, notes stay on your phone and are sent only in AI recommendation requests, and recordings, transcripts and summaries are stored only on your phone and never sent to our server. Booths saved before logging in stay on the phone until you log in. Logging out deletes the account data on your phone except the device identifier and unsent usage events.
• Children (Art. 13): gilit does not accept members under 14 and does not collect children's data. You must confirm on the sign-up screen that you are 14 or older; until that box is checked, sign-up does not proceed and no sign-up data is sent to the server (pre-login app-usage events described in Article 2 are still collected without name or contact details).
• Security (Art. 15): TLS for all traffic; login email stored encrypted and shown to operators only in masked form, with accounts keyed by a one-way identifier; AES-256-GCM encryption of mobile numbers and card emails (last 4 digits of the phone kept separately); photos in a private bucket served only through 10-minute signed URLs, with storage and database encrypted at rest; sign-in codes valid for 3 minutes with rate limits; operator console access controlled by operator accounts with passcodes or approved operator email codes, locked for 5 minutes after 10 failures, with role-based permissions and console logins, edits and deletions audit-logged with operator identifier and IP for 1 year; database on an internal network without public access; secrets kept out of source code; privacy officer appointed; servers in AWS Seoul data centers, none in our office.
• Automatic collection and SDKs (Arts. 16 to 18): no cookies, no advertising identifiers, no tracking, no third-party analytics, crash or push SDKs. On Android, Google ML Kit reads QR codes on the device and may send device, app and performance diagnostics to Google LLC (USA) under Google's disclosure; an ML Kit on-device summarization library and ARCore are bundled but inactive in the current version; for ARCore the app only asks Google Play services whether the device supports it and does not use the camera. On iOS the QR library processes images on the device. We do not use behavioral information for targeted advertising. AI booth recommendations are reference material you choose to use and are not automated decisions under Art. 37-2. We do not process pseudonymized information under Art. 28-2; usage events carry only an 8-character identifier and are deleted after 90 days, and event statistics are aggregated so no one can be identified.
• Contact and remedies (Arts. 19 to 21): Privacy officer Taesoo Chang (CEO), achang@maimhaim.co.kr, 8F #860, 815 Daewangpangyo-ro, Sujeong-gu, Seongnam, Gyeonggi-do, Republic of Korea. You may also contact the Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr), the Privacy Infringement Report Center (118, privacy.kisa.or.kr) or the Korean National Police Agency (182, ecrm.police.go.kr). In case of a data breach we notify within 72 hours by email to your stored login address and by a website notice for at least 30 days (for accounts without a stored address, that is accounts created before November 5, 2026 that have not logged in since; users who entered a card email are also notified there), including the items affected, when and how it happened, what you can do, our response, the contact point and your legal remedies, and we report to the Personal Information Protection Commission or KISA where the law requires.
• Changes (Arts. 22 and 23): we announce changes at maimhaim.co.kr/gilit/privacy at least 7 days before they take effect and reflect them in the app's policy screen from the next app version; changes that materially affect your rights are announced at least 30 days ahead with a side-by-side comparison. This version adds no new data items: it describes current processing in more detail, corrects earlier descriptions, and changes the login email address we already collect to be stored encrypted from the effective date. Because the service had not yet been publicly released and no outside users had signed up when it was revised, this version alone takes effect on November 5, 2026, the day of notice; email storage applies to logins on or after the effective date. The previous version (effective October 28, 2026, with differences between the app copy and the website copy) is available on request at achang@maimhaim.co.kr.