Privacy and visitor statistics
This site records page views using a random browser identifier saved in local storage. The identifier is used to estimate unique browsers, not to establish a person’s identity. Clearing browser storage or using another device can count as another visitor.
Stored visit records contain the page, time, referring website hostname, approximate country/region/city supplied by the hosting platform, and mobile/desktop category. We do not store raw IP addresses in these analytics records. Administrator visits and recognised bots are excluded where detected.
Statistics are stored in the site’s Cloudflare R2 storage and viewed through a restricted administrator account. Historical records remain until deleted by the operator; there is currently no automatic deletion schedule. Email inquiries remain in the operator’s mailbox until removed.
Saved favourites remain in your browser. Optional ChatGPT sign-in is used for administrator access. When you request a transit route, selected start and destination coordinates are sent to ODsay. Route results are displayed and briefly retained in the page’s memory, not stored as booking records.
Map tiles are provided by OpenStreetMap infrastructure; map resources and external booking or map links are handled by their providers. They receive network requests when used and apply their own privacy policies. Hotel payment and reservation details are not collected on this site.
To remove local identifiers and favourites, clear this site’s browser storage. For privacy questions or deletion requests, contact the operator.
Trip planner and optional location
Your day-by-day itinerary, saved place snapshots and pending itinerary selection are stored in this browser. Guest trip data stays on this device. If you explicitly choose “Save my trip”, a copy is stored in your member account as described below. Itinerary backups are files you download or import yourself.
Location access is requested only when you choose “Use my location”. Coordinates are used in page memory for approximate straight-line distances and to centre the map. The trip planner does not save them or send them to our tourism API; that API receives your selected region. Map providers receive requests for map tiles around the displayed area, which may reveal the approximate area being viewed.
If you choose offline preparation, a service worker caches only the public trip page and its required local scripts and styles. It does not cache administrator pages, sign-in responses or tourism/transit API responses. Clear this site’s storage in your browser settings to remove cached pages, favourites and itinerary records.
Optional site membership
Email membership uses Supabase Auth to handle password authentication and session refresh. The simplified registration flow does not require email ownership confirmation and does not provide email-based password recovery. Users should enter their own email address accurately and keep their password safe. Passwords are handled by the authentication provider and are not stored in this site’s travel-profile records. Existing ChatGPT sign-in remains available for administrator access and legacy member profiles. We receive a provider-specific identifier and the email supplied for account access. Simplified email registration does not verify ownership of that email address. A display name and the privacy-consent version are saved when you create your member profile.
When you explicitly save to your account, your itinerary dates and stops, saved place identifiers and descriptions, and accommodation notes are stored under your authenticated site identifier in Cloudflare R2. These records are accessible through authenticated, user-specific endpoints. Loading and saving are manual; account data is not included in the offline page cache.
Member data remains until you delete it using “Delete my member profile” on My page or request deletion through our contact page. Deleting the site travel profile does not delete your authentication-provider account or local browser data. Contact the operator for full authentication-account deletion. Signing out also leaves local device data in place; clear site storage before handing a shared device to another person.
Updated 19 October 2026
Google Analytics 4 and your choice
With analytics enabled, Google Analytics 4 (measurement ID G-P6XH4C2EW1) receives page-view and interaction information, browser/device information and referrer information, and can use cookies or similar identifiers. Google processes network information when receiving requests. Google’s processing and retention are governed by the property settings and Google’s privacy policy. We do not send your account email or itinerary to GA4 intentionally.
You can disable future GA4 and site visit events on this browser. This does not delete records already collected. Clear browser storage to remove local identifiers and cookies, and contact the operator about stored data.
Full account deletion
View deletion options and submit a request. Immediate travel-profile deletion does not remove the email authentication account. Full login-account deletion is handled by the operator after verification.
Current-location directions
When you choose a map or directions link, the browser asks for your current location. Your position is used in page memory to prepare a route. Opening the Google Maps route shares the origin and destination with Google; opening a Naver destination link shares the destination with Naver. We do not store your route origin in your account or visitor statistics. You can refuse location access and enter a starting address instead. Map providers apply their own privacy policies.
Optional arrival checks and visit journal
Start trip enables location checks only while the trip page is visible. Hiding the page stops the checks; restarting requires your action. Phone coordinates and movement paths stay in temporary memory and are not stored or sent to our server. Only visits you confirm are saved locally, with a place, Korean date, confirmation time and manual/arrival-suggested label. Save my trip explicitly copies these visit records to your private member profile. Load saved trip merges records across devices. This is not continuous background tracking or proof of physical entry. Clear browser storage to remove local records; member profile deletion removes the account copy.