Service information

Privacy Policy

Effective date: 3 October 2026

This policy covers Kangnam Myeonok's review management service for authorized restaurant managers. Contact: mienlanhkangnam@gmail.com.

Data we access and why

After a manager grants Google Business Profile management permission, the app reads account and business profile information to identify configured restaurants. It reads review ratings, text, creation and update times, reviewer display names and existing owner replies to find new unanswered reviews, choose a reply language and apply the manager's posting rules. The API may also return reviewer photo references; the app does not use those photos.

Reviewer names provide only a language clue, not confirmed nationality. The app publishes owner replies to eligible reviews through Google. We use this information solely to provide the authorized review management functions.

Processing and service providers

For eligible text reviews, the app sends review text, rating and selected reply language to the OpenAI API to identify complaints and draft replies. Reviewer names, photo references, review identifiers and Google credentials are not included in these AI requests. Review text itself may contain personal information voluntarily written by a reviewer.

OpenAI requests use store: false. OpenAI states that API data is not used to train its models unless the customer opts in; this app does not opt in. OpenAI may retain abuse monitoring data for up to 30 days by default, or longer when required by law or necessary to prevent harm. We do not claim zero retention. See OpenAI's data controls.

Google receives published replies and retains reviews and replies under its own policies. The manager receives operational notifications through the Codex service, normally limited to branch, rating, issue category and time. A manager may request a private review translation or reply recommendation through that service. These services may process data outside Vietnam.

Storage and security

The review worker runs on an operator-controlled computer. Raw reviews, reviewer names and review identifiers are handled in memory and are not written to the worker's logs or checkpoint files. Local files contain processing checkpoints and aggregate AI usage counters. Google refresh tokens and the OpenAI API key are stored in Windows Credential Manager; the Google OAuth client configuration is kept separately on the operator's computer. Credentials are not published on this website or committed to the app's source repository. API connections use HTTPS.

Netlify hosts these public information pages; it does not run the review worker or receive its Google credentials or review API responses. The hosting provider may process routine website request data, such as IP address and browser information, to deliver and secure these pages.

Retention, deletion and your choices

Local checkpoints and usage counters are retained while the automation operates. Managers can ask the operator to remove local app metadata and stored credentials. To stop Google access, revoke the app in Google account connections. Revoking access stops further API processing, but does not delete reviews or replies already published on Google; those must be managed through Google Business Profile. Provider retention is governed by the respective provider's policies.

For access, deletion or privacy questions, contact mienlanhkangnam@gmail.com. We may ask for enough information to confirm your authority over the relevant profile. Do not email passwords, API keys or tokens.

Limited use and policy changes

Kangnam Myeonok's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, or use it to train generalized AI models. Human access is limited to authorized managers and support needed to operate the app, with consent or where required for security or law.

We update this page when the app's data practices change and identify the effective date above.