PRIVACY & DATA

Kakao login ended on October 12, 2026. The content below is a historical record of the policy when it was in effect, not a description of current functions.

This is an archived version. Follow the link below for the current policy.

View current privacy policy

Privacy policy

How Entity Flow processes data for Entity Clinic Kakao login, self-checks and enquiries.

Published and effective: 2026.09.28

Scope and operator

The operator is Entity Flow, represented by Siheon Kim. This policy covers the public entityclinic.com website and Kakao login. The private content workspace at studio.entityclinic.com uses separate sign-in and privacy notices. Kakao login alone does not grant workspace access or start a paid subscription.

Kakao login: data, purpose and retention

We use the app-specific user ID issued by Kakao, authentication tokens, session issue and expiry times, and authentication request verification values to verify and maintain login. The user ID is an app identifier, not a resident registration number. These items are necessary for login. The current implementation does not retrieve names, nicknames, profile pictures, email addresses, phone numbers, dates of birth or friend lists. This website never receives your Kakao password.

Login storage and expiry

We do not create a separate member database. The login user ID and access token are kept in an encrypted secure cookie for up to one hour, or less if the token expires sooner. The authentication request cookie lasts up to ten minutes. The server temporarily processes this information during authentication. These periods concern login cookies and do not describe infrastructure access-log retention.

Access approval information

Only operator-approved accounts may access My Services after Kakao authentication. An approval request code is derived from the verified user ID; approved codes are kept in server-side access settings to check permissions and prevent unauthorized access. They are retained while access is authorized and removed when the operator revokes permission or fulfills a deletion request, independently of the one-hour login cookie. The code alone cannot log you in or grant access.

Basis for processing and your choice

The minimum information necessary to authenticate is processed to provide the login service you request, under Article 15(1)(4) of the Korean Personal Information Protection Act. You can review disclosure items on Kakao’s consent screen or cancel login. Public pages and self-checks remain available without login; the My Services page does not. Reading this policy does not constitute consent to advertising messages or additional data collection.

Logout, unlinking and deletion

Logout removes the login cookie and requests token logout from Kakao. Unlinking disconnects this service from your Kakao account and removes the login cookie after success. Expired sessions cannot be reused. You can also delete site data through your browser settings. Deleting browser cookies alone does not disconnect Kakao or delete enquiry records separately submitted.

Self-checks and storage on your device

Clinic names, website addresses, answers and notes entered in the self-check are processed only in browser memory, not sent to our server or an external AI service. Copy uses your device clipboard; download saves a file to your device. Refreshing or closing the page resets the site’s input state, while browser restoration, downloaded files and the clipboard remain under your control. Do not enter patient identifiers, medical records or health information.

Cookies and safeguards

Login cookies are encrypted and use Secure, HttpOnly and SameSite=Lax attributes. Authentication pages are configured not to cache. We check the origin of actions such as unlinking and validate Kakao tokens when checking login status. Cookies can be blocked or deleted in your browser’s privacy or site settings, which may prevent Kakao login from working. Our application code has no advertising trackers or behavioral analytics; we do not sell personal data or use login information to send advertising.

External services and hosting

Kakao handles authentication, token validation, logout and unlinking. The website runs on OpenAI Sites and Cloudflare infrastructure. IP addresses, request URLs, access times, browser information and authentication requests may be processed for delivery, execution and security. Processing on overseas infrastructure is possible. Providers’ general policies alone do not establish every processing country or access-log retention period applicable to this site. You may ask our privacy contact for clarification.

OpenAI Privacy Policy · Cloudflare privacy policy · Kakao Privacy Policy

Service and privacy enquiries

The Kakao chat link opens Kakao. Login information and self-check notes are not automatically sent as chat messages. If you send a message, the operator can see your displayed profile and message content. Chat records are processed separately from login cookies; the one-hour cookie lifetime does not apply to chat records. You may request access to or deletion of chat records through the contact below. Do not send passwords, verification codes or patient information.

Your rights and how to exercise them

You or an authorized representative may request access, correction, deletion, restriction of processing or withdrawal of consent. Use logout or unlinking in My Services, or contact us below. We verify identity or authority to the extent necessary and explain the result in accordance with applicable law. If a legal restriction prevents fulfillment, we explain the reason. Kakao account information itself can also be managed through Kakao.

Privacy officer and contact

Privacy officer: Siheon Kim, Representative of Entity Flow. Submit privacy questions, complaints or rights requests through the Entity Clinic KakaoTalk contact link below. Start your message with “Privacy request” and describe your request.

Contact us about privacy

Privacy infringement reports: 118 · Privacy dispute mediation: 1833-6972

Revision history

2026.09.28: Clarified login data, processing basis, cookies, rights procedures and the privacy officer, and distinguished the public website from the content workspace. We update this policy if data collection or purposes change and obtain separate consent where required.

Previous policy (2026.09.11)

What are you looking for?