Privacy

The public site should collect as little reader data as it needs to run the newsletter cleanly.

KbeautyHunter is not trying to turn public reading into a hidden intake funnel. This page explains the current collection scope in plain language.

Newsletter fieldsEmail address, optional first name, selected interest, signup source, and marketing consent.

Contact fieldsName, email, message, route type, and any extra scope details submitted through the public contact page.

First-party analytics fieldsA session-scoped ID, current page path, target path, route source, and compact event metadata for key public interactions.

Why it is collectedTo deliver the weekly editorial email, maintain subscription preferences, and route public feedback, corrections, or business scope to the correct desk lane.

What is not offeredThere is no public member account, paid checkout, clinic funnel, or quiz-driven profile collection on the public site.

A restrained privacy-page still with one visible skincare object, soft daylight, and generous negative space for a calm public trust surface.

Public site policy

Newsletter consent is explicit, and the public front end stays intentionally narrow.

The site currently centers on editorial reading and newsletter subscription, not on deep personal profiling.

Current collection scope

What is collected should be obvious from the form itself.

The current public implementation keeps collection limited to newsletter data, contact routing, and a narrow first-party analytics layer for key public interactions.

Newsletter signup is the main intentional data collection flow.

KbeautyHunter currently asks for personal information when a reader voluntarily joins the weekly edit or submits the public contact form. The newsletter flow stores the submitted email, optional first name, selected interest, source tag, and consent flag.

The site now uses a small first-party analytics layer.

Key public interactions such as selected hero clicks, article-next-read clicks, trust-route clicks, newsletter subscription success, contact form success, and trust-page views are logged with a session-scoped ID, route labels, and same-origin paths. This layer is designed for product measurement, not ad profiling.

No hidden quiz profile is being built in public.

The public experience is reader-first editorial. It is intentionally not collecting a deeper skin profile, diagnosis-style intake, or treatment preference questionnaire.

How it is used

The current data model exists to support one relationship: reader to weekly edit.

Editorial email

Subscriber information is used to send the weekly edit and maintain an updated subscription record.

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 a signup or inquiry came from the homepage, Start Here, About, Contact, or another public entry point.

First-party event measurement

The public site also records a narrow set of same-origin interaction events so the desk can measure whether entry routes, trust pages, and next-read paths are actually useful.

Consent gate

Newsletter subscription requires an explicit consent checkbox before the request is accepted.

Operational boundaries

Reader privacy should not be diluted by unrelated commercial systems.

This public site is intentionally separate from clinic-intake style collection, diagnostic questionnaires, or operator-side lead handling.

The live analytics layer is first-party and narrow: session-scoped event logging for selected public interactions such as hero CTA clicks, article next-read clicks, trust-route clicks, newsletter success, contact-form success, and trust-page views.

Readers who prefer not to subscribe can continue reading the public archive through the stories page without joining the list.

Retention and updates

The page should change when the implementation changes.

Subscriber records are maintained for newsletter operations until a person unsubscribes or the workflow is changed. Current public copy assumes a human-reviewed editorial list rather than automated promotional blasts.

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 event records are retained as first-party operational measurement data. 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.