Privacy Policy

Effective date: November 14, 2026

Search places

When you use the region or place search, the search term you enter and the search language you select are sent to the Google Places API through the Book & Place server. Google requests use the operating server’s IP address. Please don’t enter personal information such as your name, email address, or book contents in your search term.

Google Google Privacy PolicyWe process the information provided according to. For location searches, Google Maps/Google Earth Additional Terms of Servicealso applies.

When displaying place photos, the place identifier and photo size are sent to Google, and photo and attribution information are retrieved through the service's server. Photos are loaded starting with the cards visible on screen, and image and attribution information are processed only temporarily to display the current screen.

Search terms entered and submitted are kept in separate operational records along with the search time and whether an API call was made, regardless of whether Google was called. Operational records are not linked to member names or cookie identifiers. API request type, response status, time, count, image size, and Place ID are stored separately from search records. Search terms and operational history are kept in a private server directory until separately deleted. The original place names, addresses, and photo files in Google responses are not saved as reusable cache.

Areas Visited Photo Page

Only locations from explicitly run searches that return results and successfully retrieve actual photos are included in the public list. Search terms that were only entered, or searches where results or photo retrieval failed, aren’t included in the public list. The public list uses location names and Place IDs, and photos are fetched again from Google when viewed.

Display anonymous visitors

Containing random visitor IDs to reduce duplicate visitor counts reading_visitor Cookies are used. Cookies are valid for one day and can be deleted in the browser. A random identifier used to distinguish tabs is kept in memory while the page is running. The public screen displays only aggregated numbers and default anonymous icons, not member names or identifiers.

The server uses visitor and tab identifiers and your current space to count people online in real time. If an active connection stops refreshing, it remains valid for about 65 seconds. Even if you close your browser or lose your connection, you'll be excluded from the active user count once that time has passed.

Request a place creation

When you request a place to be created from a photo, we store the Place ID, the search term you entered, any optional location or seat notes, the submission time and processing status, and a signature used to distinguish visitors on the server. To reduce duplicate requests from the same browser and show your request history, an HttpOnly reading_requester Cookies are used. Cookie identifiers are not exposed in the original request list. Operators can update request statuses in the authenticated admin screen and save a manually entered place name, location verification note, and verification time, independently of the specific landmark ID for a creation candidate. Readers can view their location notes in their own requests in that browser and in the authenticated admin screen. They are not sent to Google automatically. Request records are kept private until they are deleted separately.

When an administrator views the details or photos of a place, or searches for a specific attraction, the place ID or the attraction search term entered is sent to the Google Places API. Google’s place names, addresses, categories, coordinates, and photo credits are used only on the current review screen and are not stored long-term in operational data. We can’t guarantee that the photos currently displayed are the same as those available at the time of a previous request.

Likes and Footprints

We store the like status for places and Footprints nicknames, post text, posting times, and signatures used to distinguish browsers on our server. We use HttpOnly cookies with a validity period of 365 days to reduce duplicate likes and allow you to delete your own posts.

reading_community

Footprints nicknames and post text are visible to other readers and are not automatically translated. Please don’t include contact information or sensitive information. Cookie identifiers and signatures used to distinguish authors are not made public. Posts and counts are shared across the two service domains, but browser identification cookies are independent for each domain.

Canceling a like removes that like. When you delete your own post, it is removed from the public list, and the stored nickname and post text are also cleared. Post identifiers, signatures used to distinguish browsers, and posting and deletion times are kept private to handle retries and limit excessive posting. After signing in, operators can hide posts. If you delete your cookies, we may be unable to verify whether an existing post is yours.

Request limits and external connections

To limit excessive requests, we use the access IP and request count in server memory to calculate per-minute request limits. The Google API key is managed only on the server and is never sent to the browser. If you select a link to an external site, that site’s privacy policy applies.

This notice is based on the current place search and visitor count features. Any changes to how data is handled will be reflected on this page.

Visitor statistics and ads

The homepage and spaces provided at bnp.vibeaz.co.kr collect page views and visit statistics using Google Analytics 4. Search terms and scene options are removed from page URLs, and identifiers used to count visitors are not sent to Analytics. Enhanced measurement, Google Signals, and ad personalization signals are not used. Google may process analytics cookies and information related to your device and browser.

We record scene loading time, location selection, sitting, opening the share menu, attempting to share, and successful sharing or copying as usage statistics. Share messages and activity trail content are not sent to Analytics.

Google AdSense ads may appear on the homepage, and Google and its advertising partners may use cookies or device-related information to serve and measure ads. Google Partner Site Data Usage Informationand Ad settingsYou can check it. You can restrict cookies in your browser settings.