Skip to content
byeot
About byeot Privacy Terms Support
한국어

SERVICE INFORMATION

Privacy Policy

How we use personal data, retain it and respond to your rights.

Last updated: Nov 17, 2026

Contents

  1. Purposes and basic principles
  2. Account and saved shops
  3. Language preference and support
  4. Reviews are public
  5. Review reports and blocks
  6. Location and search
  7. External services and network requests
  8. Retention and account deletion
  9. Your rights and safeguards
  10. Usage analytics and processing abroad
  11. Policy changes

Operator and contact

Operator
볕 운영팀
Privacy officer
김유진
Email
byeot93@gmail.com

Purposes and basic principles

byeot processes personal data needed for shop discovery, account authentication, saved shops, public reviews and safe operation. The operator, privacy officer and contact address are listed above.

Account identification and authentication, and saving shops or publishing reviews at your request, are used to perform the service contract. Review reports and blocks support your requested features and moderation, not advertising or sale of personal data. Location features and support inquiries are optional. General browsing and public information are available without sign-in.

Signing in or reading this document is not blanket consent to all processing. Separate notice and consent procedures apply where legally required. We do not request additional data unrelated to the purpose of the feature.

Account and saved shops

If you choose Apple or Google sign-in, the authentication provider and Supabase connect your account. The app uses your Supabase user ID, email, and available display name and profile photo URL to maintain sign-in and show your profile. Native Apple sign-in requests only an email, not your real name, and supports Hide My Email. Available fields vary with account and authentication settings. The app does not ask you to enter your Apple or Google password.

Saving a shop records your user ID, shop ID, and save time in Supabase. Saved shop IDs are also stored on the device. On sign-in, the existing device list is merged with the account list. Saving a new shop requires sign-in.

The Supabase SDK stores session information on the device to maintain sign-in. Signing in is not treated as blanket consent to every use of personal data.

Language preference and support

Your chosen app language, Korean or English, is stored in SharedPreferences on the device and retained when you reopen the app. It is not linked to an account or synchronized to a server, and remains separate from sign-in and sign-out.

Contact us in Settings opens an external mail app with a draft addressed to byeot93@gmail.com, including the app version and a message prompt. You write the message and decide whether to send it. The app does not send the email itself or save the inquiry to a database.

The sender address, message and replies of an email you send are used to answer inquiries, investigate errors, correct shop information and handle privacy requests. The byeot operating team receives and replies through Gmail. Messages become due for deletion one year after the last message sent or received and are deleted in the next monthly cleanup, within one additional month. The receipt date applies if there is no reply. This is an operating retention rule, not a statutory minimum.

We aim to acknowledge inquiries within three business days and handle privacy requests within applicable legal deadlines. If additional checks are necessary, we explain the reason and progress. Do not send passwords, verification codes, resident registration numbers or unnecessary personal data.

Reviews are public

When you submit a review, the app stores the shop ID, user ID, author name, rating, review text, and creation and update times. Reviews for published shops can be read without signing in. The screen shows the author name, rating, text, and creation date.

Your author name may use the name provided by Google. A default name is used if no suitable name is available or the name resembles an email address, but reviews are not guaranteed to be anonymous. The current review query response also includes user IDs and review IDs.

Do not include phone numbers, addresses, sensitive information, or another person's personal data in your review. You can edit your review through the same shop's form or delete it from the review menu. Public reviews are retained until you delete them or your account. Report evidence may be retained separately for the periods below.

Review reports and blocks

Reporting a review stores your user ID, target review, shop and author IDs, public author name, a snapshot of the reported text, reason and submission time in Supabase. The operator manages review and resolution records. Reporter identity and internal moderation records are not exposed to other app users. Evidence captured when reporting may remain after the review is deleted.

Blocking an author stores your user ID, blocked author ID and public name, and block time. It affects review lists and rating summaries for your account only; it does not delete another account or change other users' screens. You can unblock authors in Settings.

The operator can apply content filters, hide violating reviews and restrict abusive accounts. The byeot operating team reviews reports and accepts questions and appeals through the contact email above. Urgent reports such as exposed personal data or threats receive priority. Restrictions are applied after checking the facts and only as needed. A low rating or critical opinion alone is not grounds for sanctions.

Report records become due for deletion at the earlier of 90 days after resolution or 180 days after submission. The 180-day rule also applies to pending reports. Finite sanction records become due 90 days after the sanction ends. Due records are deleted in the next daily cleanup. Indefinite sanctions remain until lifted or the account is deleted; blocks remain until unblocked or a related account is deleted. These are operating limits for safety and review of appeals.

Location and search

With location permission, the app obtains your current latitude and longitude to sort nearby neighborhoods, move the map camera, and show your current location. The current app code does not persist location history or send your current coordinates to Supabase. Search text and shop filters are also processed within the app.

App version 1.0.6 and later use the Kakao Maps SDK. Versions 1.0.5 and earlier use Google Maps and remain subject to that provider’s privacy disclosures. Kakao Maps is used for the map view and current-location display. Processing by the map SDK and device location services is separate from processing inside the app. Kakao Maps requests require network communication with Kakao servers. The app obtains the current location through device location services and displays it as a map marker. Detailed SDK processing categories and retention are checked separately against the provider’s disclosures. This does not mean the app stores location history in Supabase.

You can deny or revoke location permission in device settings. This limits current-location features, but general shop browsing and search remain available.

External services and network requests

The app currently uses Apple and Google sign-in, Kakao Maps (app 1.0.6 and later), Google Maps in earlier versions, and Supabase authentication, database, and image storage. Some profile and shop photos are loaded directly from external image URLs. Loading a photo makes a network request to that server and may disclose connection information such as your IP address.

Opening a shop website, social media page, or source link takes you to an external app or browser. That service's own privacy policy and terms apply there.

The app has no separate advertising SDK. Builds with usage analytics enabled use the PostHog SDK; the usage analytics section below describes the data and overseas processing. Map SDK usage and diagnostic information and provider logs may still be processed. The independent processing of Apple and Google authentication, Kakao Maps and Google Maps in earlier versions, Gmail and external image servers is also described in their own privacy notices.

Supabase Pte. Ltd. provides authentication, the database and server functions. Account identification and profile, saved shops, reviews, reports, blocks and sanctions are transmitted through HTTPS when you use these features. The verified primary database location is Tokyo, Japan. This does not mean that all authentication, functions, support, logs or backups are processed only in Japan. Supabase's privacy contact is privacy@supabase.com.

International processing and storage necessary for account features are limited to performing the service contract. Not using account features or deleting your account stops new transmissions for those features, while general browsing remains available. Supabase's contracting entity is in Singapore and the primary database is in Tokyo, Japan. Support, security operations and subprocessors may process data in other countries. A region setting does not restrict every processing operation to that country. The scope is described in Supabase's data processing addendum and subprocessor list.
https://supabase.com/legal/customer-resources/data-processing-addendum
https://supabase.com/legal/customer-resources/subprocessor-list

Google LLC (United States) handles map display and SDK operations in app version 1.0.5 and earlier, your chosen Google sign-in and Gmail support messages; Apple Inc. (United States) handles your chosen Apple sign-in. Necessary account or device and request information is sent over encrypted networks when you sign in, use maps or send a support message. These global services may process it in other countries. Their own processing, retention and rights procedures are described here:
https://policies.google.com/privacy
https://www.apple.com/legal/privacy/

The current Supabase project uses the Free plan, with project observability log retention set to one day. Operator-accessible automatic backup retention and restoration, and point-in-time recovery (PITR), are not supported. This does not mean the provider has no internal security records or protective copies, or deletes all such records within one day. Internal processing follows the provider's contract and privacy notices. If a backup is restored, previous deletion requests must be reapplied before service resumes.

App version 1.0.6 and later switch map display to the Kakao Maps SDK. Kakao’s privacy disclosures apply to the map SDK’s separate processing; detailed SDK processing categories and retention are checked separately.
https://www.kakao.com/policy/privacy

Retention and account deletion

Account identification and profiles are retained until account deletion; saved shops until unsaved or account deletion; and public reviews until review or account deletion. Device language settings remain until changed or app data is cleared. Local sessions and saved shops are cleared on sign-out or account deletion. Inquiry, report, sanction and block periods are described in their respective sections.

Choosing account deletion requests deletion of the authenticated user's Supabase account. Accounts linked to Sign in with Apple require Apple re-authentication to verify the linked account and revoke sign-in tokens before deletion. The account is not deleted if you cancel re-authentication or revocation does not complete. If server setup is incomplete or re-authentication is unavailable on your device, the app explains the issue rather than reporting successful deletion.

The one-time Apple authorization code and tokens are used only for the revocation request. Authorization codes and revocation tokens are not kept in a separate database or written to application logs. The Apple private signing key is not included in the app. This is separate from Supabase session storage used to maintain sign-in.

The deployed database has been checked for cascading deletion of linked saved shops, reviews, profiles, blocks and sanctions. Reports made by other users may retain evidence for the report retention period after the reported account is deleted.

Expired reports and finite sanctions are scheduled for daily server cleanup at 11:15 Korea Standard Time. The operating team reviews support mail monthly and permanently deletes expired messages. Any legally required preservation is separately identified by law, data category and period, with restricted access. Electronic records are deleted to prevent recovery; any paper records are shredded.

After successful account deletion, the app clears this device's saved shops and sign-in state. Signing out is not account deletion. Deleting a byeot account does not delete the Apple or Google account itself. We do not guarantee immediate erasure of all external-provider logs and backups.

Your rights and safeguards

Subject to applicable law, you may request access, correction or deletion, restriction of processing, and withdrawal of consent for your personal data. In the app, you can unsave shops, edit your review, and delete your account. Location permission is managed in device settings.

Send other requests through the contact email above or Contact us in Settings. The operating team and privacy officer verify your identity or authority using the minimum necessary information. Re-authentication or confirmation through your existing account email is preferred. Passwords, verification codes, resident registration numbers and ID copies are not required as standard evidence. Any proof of representation requested is limited to what is necessary. We explain the result and any applicable legal restriction.

Account authentication and database access controls protect saved shops and review creation or editing. Reports and sanctions are not public to ordinary users. The operating rules limit administrator access to necessary staff and prioritize personal-data exposure and security incidents. Confirmed incidents are investigated and notified or reported as required by law. We do not promise encrypted device session storage or complete security before verifying actual settings.

Where parental consent is legally required for personal data of a child under 14, separate consent and verification are necessary. This notice and an App Store age rating do not replace that process. Such requests can also be sent to the privacy contact.

In Korea, privacy complaints can be discussed with the Privacy Infringement Report Center at 118 or the Personal Information Dispute Mediation Committee at 1833-6972.

Usage analytics and processing abroad

In builds with PostHog analytics enabled, we record app launches and returns, area selections, submitted searches and result counts, shop detail views, successful saves/removals, and directions-button clicks to improve the service. Data may include a randomly generated per-installation identifier, event timestamps, shop IDs and trade areas, query length, direction provider, and SDK app, OS, device and session metadata. This identifier is not linked to a Supabase account or used to merge people across devices.

Analytics events exclude email, name, raw search queries, review text and current location coordinates. Session replay and automatic click/error capture are not used. IP-based geographic enrichment is disabled, but the provider may process network IP addresses during transmission.

The analytics processor is PostHog, Inc., reachable at privacy@posthog.com. The connected project uses US Cloud. In analytics-enabled builds, the actions described above are queued locally and transmitted over HTTPS to the US ingestion service to analyze usage paths, conversions and return visits. Account details and advertising identifiers are not provided for ad targeting. The provider's privacy notice is available at https://posthog.com/privacy.

The Free plan provides a one-year event query window. Expiry of that window does not guarantee immediate, complete deletion of all originals and backups. Actual deletion and retention exceptions are handled after checking the provider's deletion procedures and applicable contract. Changes to processing or retention, including a paid-plan change, are reflected in this policy.

Requests for access, deletion or restriction of analytics processing can be sent through Contact us in Settings or to byeot93@gmail.com. Because account IDs are not linked to analytics identifiers, deleting an account does not automatically delete that installation's analytics events. We verify only the minimum identifying information needed to handle a request. The app currently has no user setting to turn analytics collection on or off. PostHog is not initialized in builds without analytics configuration.

Policy changes

This document was last updated on October 14, 2026. This policy takes effect on October 7, 2026. Subsequent changes retain revision dates, effective dates and previous versions.

Material changes to purposes, data categories, disclosures, processors, retention or rights are announced in the app and on the public policy page before or immediately when changed. Separate consent is obtained when required. Reading the policy or signing in does not replace that consent.

볕 운영팀 · Small shops, thoughtful discoveries

© 2026 byeot. byeot93@gmail.com

About byeot Privacy Terms Support