Privacy
The public site collects only what the reader route needs.
Contact consent, routed submissions, and narrow analytics stay visible and limited.
Public site policy
Consent, contact, and measurement stay on narrow public routes.
The site currently centers on editorial reading, routed contact, and narrow measurement, not on deep personal profiling.
Current collection scope
The form should explain the collection.
The public implementation stays limited to contact routing and narrow analytics while update-list collection remains deferred.
The contact form is the active personal-data flow.
KbeautyHunter currently asks for personal information when a visitor or operator voluntarily submits the public contact form. The form stores the submitted name, email, message, route type, and any scope details needed to handle the request.
The site uses GTM and GA4 for public measurement.
Key public interactions such as selected hero clicks, article-next-read clicks, trust-route clicks, contact-form success, and trust-page views can be pushed to GTM and streamed into GA4. This layer is designed for product measurement, not hidden profile collection.
No hidden profile collection is being built in public.
The public experience is a Korean skincare launch agency plus signal library. Any future clinic, dermatology, plastic-surgery, medical referral, or partner-lead route needs separate disclosure, scope, and data handling before it appears.
How it is used
The current data model supports reading, routed contact, and narrow measurement.
Reader feedback
Reader submissions are used to review unclear pages, correction needs, and public wording issues.
Public contact routing
Contact submissions are used to route reader feedback, correction requests, or business inquiries into separate review lanes.
Operational source tagging
The `source` field helps distinguish whether an inquiry came from the homepage, Start Here, About, Contact, or another public entry point.
Event measurement
The public site pushes a narrow set of interaction events so the desk can measure whether entry routes, trust pages, and next-read paths are actually useful.
Business boundary
Business inquiries stay separate from reader feedback and correction requests so public editorial routes do not become a hidden sales funnel.
Operational boundaries
Reader privacy should not be diluted by unrelated commercial systems.
The current public site is intentionally separate from clinic-intake style collection, diagnostic questionnaires, and operator-side lead handling.
The live analytics layer is narrow: selected public interactions such as hero CTA clicks, article next-read clicks, trust-route clicks, contact-form success, and trust-page views can be routed through GTM into GA4.
Readers do not need a public account or list signup to continue reading the public archive through the stories page.
Retention and updates
The page should change when the implementation changes.
Email-update collection is deferred in the current public launch scope. If it becomes active later, this page should be updated before the signup surface is promoted.
Public contact submissions are retained for editorial review and routing so the desk can separate reader feedback, correction requests, and business scope instead of collapsing them into one generic inbox.
Analytics events are handled through the public measurement stack. This page describes the live public implementation as of this pass and should be revised whenever form fields, analytics behavior, advertising systems, or third-party data sharing change.
Privacy, corrections, and public contact requests can also be sent to info@kbeautyhunter.com.