Privacy Policy
Effective date: July 6, 2026
LINKON Co., Ltd. (the 'Company') complies with the Personal Information Protection Act of Korea and other applicable laws in connection with LINKON pre-registration and consultation requests, and processes personal information as follows.
1. Information we collect and how
Collected via the pre-registration form: name, email, phone (optional), company/organization name (brand & hospital applications), primary social platform and channel URL (influencer applications), selected interests, marketing consent status, and time of consent Collected via the inquiry form: inquiry type, name, phone, email, company/organization name (optional), selected interests, estimated budget, and inquiry message Collection method: entered directly into the website pre-registration or inquiry form Collected automatically: your IP address is recorded in partially masked form for spam prevention.
2. How we use your information
· Confirming pre-registration and sending LINKON launch updates · Responding to marketing and Japan market entry consultation requests · (With optional consent) sending LINKON news and marketing communications
3. Retention period
We retain your information for 12 months from the date of collection, then delete it without delay. If you withdraw consent, it is deleted immediately.
4. Processing delegation and cross-border transfer
· Recipient: Google LLC (United States) · Items transferred: all items listed above · Purpose and method: storage and management of pre-registration and inquiry data (Google Sheets), transmitted over the network · Retention: same as '3. Retention period' above You may refuse consent to this cross-border transfer; in that case, pre-registration and inquiries may not be available.
5. Withdrawing consent and your rights
You may request access to, correction or deletion of, or suspension of processing of your personal information, or withdraw consent, at any time. Contact us below and we will act without delay.
6. Privacy officer and contact
Privacy officer: Byeongsu Kim Email: linkon@linkonkr.com
7. Optional Meta advertising measurement
Advertising measurement notice updated: 2026-10-19 Separately from storing inquiries in Google Sheets, we may use browser-based Meta Pixel and server-side inquiry-completion transmission (Conversions API) only when measurement is enabled and you give a separate choice to allow it. You can submit an inquiry without agreeing. To measure advertising effectiveness, visit and inquiry-completion information and a random receipt identifier may be sent to Meta together with page and referrer URLs, IP, browser and device information, and cookie identifiers. We do not add your inquiry message, name, phone number or email address to events, either directly or as hashes. Server transmissions use a random identifier linked to a successfully received inquiry, its receipt time, a public page URL, IP and browser information, and available Meta cookie identifiers. The browser and server use the same receipt identifier to reduce duplicate measurement. You can allow or withdraw measurement near the inquiry form or at the bottom of the website. Your choice, decision time and notice version are recorded in this tab’s session storage. After consent, we remember the advertising source, medium, campaign ID, ad set ID, ad ID, creative identifier and landing path in this tab. When you inquire, these are saved with the receipt identifier, consent time and capture time in the Google Sheets inquiry record and staff notification. Raw cookies and click identifiers are not stored in these inquiry attribution fields. The inquiry retention policy above applies. Visits without consent, after withdrawal or without identifiable source details are recorded without a known advertising creative. Withdrawal stops new measurement requests and attempts to cancel pending browser requests and remove related first-party cookies. A server transmission already started may still complete. It does not immediately delete information already received by Meta. The inquiry-information retention described above is separate from Meta’s handling of information it receives. Please also review Meta’s official privacy and cookie information below.