길잇 개인정보 처리방침

gilit Privacy Policy (English summary)

Effective December 9, 2026 (announced November 9, 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 versions (1.0.0 and 1.0.1) and server actually do, naming the version where the two behave differently; 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, mobile number and business card details (company, title, card email, card and profile photos); we no longer ask for gender in the profile. 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. Optional consents (chosen separately from the required ones, never pre-ticked): age group, gender and similar information for statistics, and advertising email consent records. If you choose mobile identity verification, which is optional: name, date of birth, mobile number and a duplicate-sign-up identifier (DI) (gender, domestic or foreign status and carrier are kept only while you consent to statistics use), received directly by our server from NICE Information Service Co., Ltd.; we do not receive the connecting information (CI) or your resident registration number.
• 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 (aggregated figures may be shared with event organizers, exhibitors and sponsors; externally shared tables hide cells under 10 people and round figures to multiples of 5) 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). From December 9, 2026 we may also produce statistics across several events (such as return rates) in the same aggregated way, and statistics split by age group or gender use only the values of users who agreed to statistics use; advertising emails go only to users who gave both advertising consents in Art. 9 (choosing content and recipients by the events you joined and interests you picked only with the separate tailored-advertising consent). Mobile identity verification, for those who choose it, is used to confirm your identity, confirm that you are 14 or older, prevent one person from creating several accounts, prevent fraud and handle disputes.
• 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 (consent type, document or text version, time of consent and withdrawal, the screen and method used, app version, OS and display language, and how and when we notified you of the result), 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 and mobile number (profile step after sign-up, can be skipped; the mobile number is shown on the card edit screen but cannot be edited there), business card details (card edit screen), your in-venue position and booth visits (only after you grant Bluetooth and location permission, Art. 10) and the old marketing opt-in status (kept only as consent history and never used for marketing, Art. 9). We no longer ask for gender in the profile: app 1.0.1 has no gender field there, gender collected by the app 1.0.0 profile step is not used for anything from November 16, 2026, is deleted when we update the server, and gender sent by app 1.0.0 is not stored after that; gender given with the statistics consent or received through identity verification is described below. 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 with your in-venue position at the start, the destination booth when navigating to a person and whether you arrived, map opens with your in-venue position and zone at that moment, and card exchanges with the counterpart's one-way identifier and the booth where the exchange happened; from app 1.0.1 also booth and place search terms and the booth picked from the results. Search terms are stored with phone-number-like and email-like text masked and the raw text is deleted after 90 days; the location data inside activity records is deleted 7 days after the event ends) 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. New optional items: (1) age group, gender and similar information for statistics, given under "[Optional] Consent to use age group, gender and similar information for statistics" at sign-up or under My > Settings > Optional consents (for verified users: birth year, used only to work out the 10-year age group, gender, domestic or foreign status and carrier type; otherwise the age group and gender you pick); (2) advertising email consent status with times, the consent text version, the screen and how we confirmed the result; (3) for tailored advertising emails, the events you joined and the interests you picked; and the mobile identity verification result described above, with gender, domestic or foreign status and carrier kept only while you consent to statistics use, collected on the basis of your request for verification and the consent shown when you start it.
• 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 3 years, but the location data inside them is deleted 7 days after the event ends and the raw search text after 90 days, and when you delete your account your identifier is replaced with a random value that differs per event and the location data, search terms and counterparts in them are removed; internal aggregate tables 3 years after the event; aggregate reports given to organizers, exhibitors and sponsors (cells under 10 hidden, rounded to multiples of 5) are not personal information and have no set limit; entry and exit records 90 days; usage events 90 days; user security audit records 1 year; operator console access, edit or delete and individual record view 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. Statistics information is kept until you withdraw consent or delete your account and is deleted right away when you withdraw; identity verification results are kept until you delete your account (gender, domestic or foreign status and carrier only until you withdraw the statistics consent; nothing is stored if you are under 14, an automatic decision from your date of birth that you can ask us to explain or review at achang@maimhaim.co.kr), and in-progress verification requests stay in server memory for at most 10 minutes; advertising email sending records are kept 1 year from sending, and records of consent result notices and two-yearly reminders 3 years.
• 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, exhibitors and sponsors never receive individual-level data (name, contact details, location, trail or search terms), and the console has no export to organizers. Event statistics are given only as one finalized aggregate report per event, the same version for every recipient, with cells under 10 people hidden and figures rounded to multiples of 5. 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. Aggregated statistics split by age group or gender use only the values of users who agreed to statistics use, and no location-based statistics are provided. Operator edits and deletions made in an operator session (console or admin API) are audit-logged.
• 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). From December 9, 2026 Amazon Web Services also sends advertising emails and consent result and reminder emails. NICE Information Service Co., Ltd. (Republic of Korea), a designated identity verification agency, performs mobile identity verification; the terms shown inside its screen are collected by NICE and your carrier, and we pass it no other personal information.
• 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, in-venue position records, 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 with a per-event random identifier and remove the location data, search terms and counterparts in them, 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), 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. Statistics information and identity verification results (including the DI) are deleted when you delete your account, and advertising consent stops having effect; advertising sending records (1 year) and notice records (3 years) remain with a member identifier but without the email address.
• Your rights (Art. 8): access, correct, delete, suspend processing or withdraw consent at any time, in the app (My tab for your profile; the "discoverable" switch below the privacy policy under My > Settings > Terms and policies; Settings for account deletion) or by email from your sign-up address to achang@maimhaim.co.kr. To stop in-venue location collection, use the method in Art. 10. From app 1.0.1 the sign-up screen no longer asks for marketing consent, and earlier marketing opt-ins are never used for marketing (Art. 9). 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; your name cannot be cleared in the app and the mobile number cannot be edited on the card edit screen, so both are removed on request by email or by deleting the account. Gender is no longer collected in the profile, and values already collected there are deleted as described in Art. 2. 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. Optional consents are turned on and off, and their history viewed, under My > Settings > Optional consents; turning them off is never harder than turning them on, and advertising emails can also be stopped with [Unsubscribe] without signing in. You can see whether and when you verified your identity under My > Settings > Identity verification, delete the record and withdraw the consent there, and ask us by email to access the result; we do not edit verified values, but you can delete the record and verify again.
• Marketing messages (Art. 9): we send advertising emails only to users who gave both "[Optional] Consent to receive advertising information (email)" and "[Optional] Consent to the use of personal information for sending advertising", chosen separately at sign-up or under My > Settings > Optional consents; the consent texts are published by version at maimhaim.co.kr/gilit/consents. Sender: gilit · Maim Haim Co., Ltd. Content: news about gilit and the exhibitions and events it supports (including news from organizers and exhibitors, sent by us without giving your address to anyone), new features, events and offers, and survey or interview requests; never job postings. Email only, to your stored sign-in address (accounts with no stored address, i.e. created before November 5, 2026 and not signed in since, receive none); no text messages or app notifications, and nothing between 9 p.m. and 8 a.m. With the separate "[Optional] Consent to the use of personal information for tailored advertising emails" we choose content and recipients by the events you joined and the interests you picked, never by age, gender, location, card details or identity verification data; without it you receive only the emails sent to everyone. Subjects start with the Korean advertisement label, and the body shows the sender name, email, phone, address and how to unsubscribe in Korean and English; we do not track opens or clicks. [Unsubscribe] works without signing in (maimhaim.co.kr/gilit/unsubscribe), and you can also turn it off in the app or ask by email; it takes effect immediately. We show the result of every agreement, refusal or withdrawal right away and email it within 14 days if the app could not confirm it, and remind you of your consent every two years. Consents given through the old "[Optional] Marketing messages" row or switch in app 1.0.0 are never used for advertising, whenever they were given. Consent records are kept 3 years after account deletion, sending records 1 year and notice records 3 years. Essential notices (sign-in codes, policy changes, security, consent result and reminder notices) are not advertising.
• 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 in app 1.0.0 has no effect (turning it off does not stop collection) and was removed in app 1.0.1, 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, inside activity records, the coordinates and zone at navigation start and map open, whether you arrived, the booth where a card exchange happened and the destination booth when navigating to a person. Purposes: indoor navigation, visit records, navigation quality checks and service improvement; position records and the location data inside activity records are deleted 7 days after the event ends, and the last known booth is cleared 7 days after reports stop. We do not produce statistics counted from location data (visitor counts, dwell time) until location-based service terms and consent are in place. 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, and whenever an operator views an individual's trail or activity records, who viewed whose records and when is 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. Deleting your account deletes your position records immediately.
• 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. Mobile identity verification opens NICE's screen in an in-app browser (Safari view on iOS, Custom Tabs on Android) and needs no new permission.
• 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, including card and photo copies and card changes not yet sent to the server, 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). If you verify your identity, we use the date of birth in the result to confirm that you are 14 or older; if you are not, we do not store the result and delete the account and data without delay. We do not receive the date of birth of users who do not verify.
• 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 console logins, edits and deletions audit-logged with operator identifier and IP for 1 year; currently every operator who signs in with an approved email has supervisor rights, so approved emails are limited to staff who need them, and role separation is in preparation; 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. All traffic uses TLS 1.2 or later. Identity verification results are handled only on the server and encrypted with a per-member key (AES-256-GCM); the DI is used for duplicate checks only as an irreversible HMAC value, the original stays inside the encrypted result, the raw encrypted result from NICE is not kept, and CI and resident registration numbers are never received; results such as the DI and date of birth never appear in app screens, responses or logs, and only your name is sent to the app once, right after verification, to ask whether to change the name on your card; request numbers and results are single-use and expire; the service credentials are kept in the server's secret store, separately for testing and production, and never in the app or source code. Unsubscribe links carry a tamper-evident encrypted value that does not reveal the member identifier, and the unsubscribe page uses no cookies. Operator viewing of individual trails and activity, statistics views and advertising sends are audit-logged for 1 year.
• 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: internal statistics screens hide cells under 5 people, externally shared figures hide cells under 10 and are rounded to multiples of 5, and no statistics are counted from location data. We do not collect other companies' app or web usage and show no ads in the app; with the tailored-advertising consent only, we choose advertising emails by the events you joined and interests you picked inside gilit. Event statistics are only aggregated figures (we still do not process pseudonymized information under Art. 28-2): the internal statistics screen hides cells under 5 people and logs each view, reports for organizers, exhibitors and sponsors hide cells under 10 and round to multiples of 5, splits by age group (counted by calendar-year age), gender, domestic or foreign status and carrier type use only users who agreed to statistics use, and these values are never used to pick individuals for advertising or job offers or combined with location statistics.
• 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 at least 30 days ahead with a side-by-side comparison (maimhaim.co.kr/gilit/privacy/changes) when they materially affect your rights. This version, effective December 9, 2026 and announced 30 days ahead, adds the optional statistics consent, the advertising email consents with a rewritten Art. 9 and optional mobile identity verification through NICE Information Service Co., Ltd.. The server does not accept the new consents or verification before the effective date, and starts accepting them only once we are ready; until then the app shows only a preview. If an app version with a new feature ships before the effective date, the server does not collect data for that feature before then. Previous versions: November 16, 2026 (to December 8, 2026), November 5, 2026 (to November 15, 2026) and October 28, 2026 (to November 4, 2026); versions from November 5, 2026 are viewable on our website and all are available on request at achang@maimhaim.co.kr.