Privacy Policy

1. Information we collect

The Service does not require registration for basic features such as viewing the map and checking nearby places. However, reviews, likes, nickname settings, and some reporting and verification features are available only after logging in.

The Service allows logged-in users to upload place photos. Uploaded photos may be retained, published, rejected, or deleted depending on their moderation status.

• Social login information: user identifiers provided by Google, Kakao, Apple, and Naver, login provider information, email address (if provided), and name, nickname, and profile information (if provided)
• Apps-in-Toss Toss login information: the minimum necessary userKey, connection status, and internal user UUID. The Toss authorization code and AccessToken/RefreshToken are processed only in memory during the login request and are not stored
• Account information: Supabase Auth user ID, session information, and user-set nickname (display_name)
• Apps-in-Toss session information: a bearer held in client memory and an HMAC hash on the server. Sessions expire absolutely 60 minutes after issue and are discarded immediately upon logout, disconnection, or account deletion
• User-submitted information: place reports, reports adding menu or other details, place photo files, reviews, likes, flags, alley notes, and inquiries
• Community operations information: version and time of UGC terms consent, author block relationships, contribution scores, and account deletion processing status
• Photo processing information: photo file name, MIME type, file size, image dimensions, uploading user ID, upload time, moderation status, and storage path
• Verification and operations information: confirmations of whether a place still exists, flag reasons, administrator moderation status, and processing records used to prevent abuse
• Location-related information: coordinates, addresses, and place information of locations a user selects on the map or reports, and, if the user has allowed the browser's current location permission, the current location coordinates needed to look up nearby places
• Technical information: IP address, browser and device information, access date and time, request path, error logs, and Service settings stored in cookies or local storage

2. Purposes of use

• Providing basic Service features such as the map, place details, and alley information
• Google, Kakao, Apple, and Naver social login, session maintenance, account identification, and nickname management
• Toss login, checking Apps-in-Toss connection status, session maintenance, account identification, and nickname management
• Providing community contribution features such as place reports, reviews, likes, flags, and confirmations
• Uploading, storing, and moderating place photos, publishing approved photos, and handling rejection and deletion
• Moderating, hiding, and deleting reports, flags, and reviews, and responding to abuse
• Providing location-based features such as nearby place lookup, moving the map center, and distance-based sorting
• Error analysis, security checks, Service quality improvement, and responding to customer inquiries
• Compliance with laws or platform policies, and responding to disputes

3. Location information

The Service may determine your current location through the browser or operating system location permission. The current location is used to look up nearby places and to move the map to the area around your current location.

• The current location permission is used only if the user has allowed it.
• Current location coordinates may be included in nearby place API requests.
• The Service does not combine current location coordinates with account identifiers to store them as a separate location history.
• However, technical logs such as IP address, request time, and request path may remain in the security logs of server and hosting providers.
• If a user selects a specific location while reporting a place or alley information, that location information may be stored and published as Service data.

4. Photos

Photos uploaded by users are stored in Supabase Storage, and approved photos may be published on place details. Photos not yet moderated and rejected photos are not exposed through public APIs.

Before publishing a photo, the Service may convert and compress it to the extent necessary to reduce exposure of personal information. However, photos may contain personal information such as faces, license plates, addresses, and contact details, so users must check for these themselves before uploading.

• Photo upload is available only to logged-in users.
• Photo files are processed for moderation, abuse prevention, responding to rights infringement, and Service quality improvement.
• Approved photos may be provided on the place details screen through access URLs valid for a limited time.
• The Service may process photos during conversion to reduce exposure of shooting metadata such as EXIF, but does not guarantee removal of all personal information.
• Users must not upload photos in which another person's face, license plate, address, contact details, or other personal information can be identified.

5. Provision to third parties and outsourcing

The Service uses external services such as Toss (Apps-in-Toss), Google, Kakao, Apple, Naver, Supabase, Vercel, and the iNavi Map Web SDK/API. Each service may process personal or technical information to the extent necessary to provide features such as authentication, sessions, data storage, hosting, and background map display. The Service does not sell users' personal information.

6. Overseas transfer of personal information

The Service may use domestic and overseas cloud and authentication infrastructure such as Supabase, Vercel, Google, Kakao, Apple, and Naver. Accordingly, personal information or technical logs may be stored and processed in the countries where each provider operates. If the operating region, destination country, recipient, or retention and use period is finalized or changed, we will update this Policy or give separate notice.

7. Cookies and local storage

The Service may use cookies or browser local storage to maintain login sessions, save user settings, maintain map and UI state, and for security and error analysis. Users can refuse cookies or delete stored cookies through browser settings, but some features may not work properly if cookies are restricted.

8. Retention and destruction

The Service destroys personal information without delay once the purpose of its collection and use has been achieved. Deletion request emails are retained for up to 30 days after the request is closed as completed, failed, withdrawn, or unanswered, solely for identity verification and correcting processing errors, and are then permanently deleted. If there is no reply within 30 days after an identity verification request, the request is closed as unanswered. After account deletion, the minimum records necessary for security and for responding to abuse and disputes are kept separately for up to 180 days, with their necessity reviewed every 30 days. If a law requires a longer period, they are retained until the end of that statutory period and then deleted.

9. Account deletion and disconnecting social login

Logged-in users can delete their account immediately on the Account and data deletion request page. If you cannot log in, you can make a request to golzers.admin@gmail.com by following the procedure on the same page.

After ownership is confirmed, we delete the authentication account, Service profile, sessions, social login connection identifiers, and personal information linked to the account.

Logout, Toss disconnection, and account deletion have different results. Logout ends only the current Apps-in-Toss session. Disconnection ends all Apps-in-Toss sessions and the Toss connection, but keeps the Golzers account and UGC. Account deletion within Apps-in-Toss ends sessions and the Toss connection, and deletes or de-identifies Golzers account data according to the criteria below.

• Photo files and photo moderation records are deleted together, including both Storage objects and database rows.
• Reviews, likes, and contribution score records are deleted with the account.
• Reports, confirmations, flags, and alley notes may be kept as de-identified contributions needed to operate the Service; if kept, account-linking information such as user ID is removed. If de-identification is not possible, they are deleted.
• De-identified contributions may be kept for as long as the Service operates. Minimum records for security, abuse, and dispute response are kept separately from account data for up to 180 days, and records required by law only until the end of the statutory period.
• Google, Kakao, Apple, and Naver accounts themselves are not subject to Golzers account deletion and are managed separately on each provider's account management screen.
• Web social login accounts and Apps-in-Toss Toss accounts are different login channels. They are not automatically combined as the same person and are managed separately in each channel.

10. User rights and how to exercise them

Users may request access to, correction of, deletion of, or suspension of processing of their personal information, and may withdraw consent. Requests can be submitted to golzers.admin@gmail.com, and the Service will handle them without delay within the scope of applicable laws.

11. Personal information protection officer

• Personal information protection officer: Golzers Service operator
• Contact: golzers.admin@gmail.com

12. Revision history

• v1.4 (2026-10-21): Added the immediate account deletion path for logged-in users
• v1.3 (2026-08-14): Added Apps-in-Toss Toss login, sessions, UGC, blocking, and account deletion processing
• v1.2 (2026-07-22): Added the account deletion request path and the scope of deletion and de-identification by data type
• v1.1 (2026-07-10): Added personal information processing for place photo uploads
• v1.0 (2026-07-06): Initial version