English — Privacy Policy

This blog values the privacy of its users and strives to process personal information securely in accordance with applicable laws.

This blog does not offer membership registration or a separate contact form, and does not require a name, email address, or phone number to post a comment. However, information such as comment content, visit and usage records, online identifiers, and technical information related to site security may be automatically generated or processed while you use the blog.

This blog provides content to users both in Korea and abroad. In the course of using global services such as Google, Microsoft, Cloudflare, Optimole, Google Drive, Google Cloud (BigQuery), and affiliate marketing service providers, some information may be processed outside the Republic of Korea or outside the user’s country of residence.

1. Information Processed and Purposes of Use

The following information may be automatically generated or processed while you use the blog.

  • Pages visited and content usage records
  • Date and time of access and duration of use
  • Cookies and other online identifiers
  • Browser, operating system, screen size, and device information
  • Approximate location of access
  • IP address or network information derived from it
  • Requested URL, referrer, and network request information
  • Site usage behavior such as clicks and scrolling
  • Comment content and technical information generated when posting comments
  • Identifiers used to measure affiliate link clicks and conversions

This information may be used for the following purposes.

  • Analyzing blog visits and content usage
  • Improving content quality and user experience
  • Managing site performance and stability
  • Compiling statistics on popular content and post views
  • Detecting and blocking abnormal access, spam, and security threats
  • Publishing and managing comments
  • Measuring affiliate link clicks and conversions
  • Settling affiliate commissions
  • Backing up the site and restoring it in the event of failure
  • Complying with applicable laws and protecting users’ rights

2. Use of Google Analytics

This blog uses Google Analytics 4 (GA4), provided by Google, to analyze how visitors use the site and to improve content and user experience.

Google Analytics may use technologies such as cookies to process information including pages visited, time spent, traffic sources, browser and device information, approximate location, events, and site usage behavior.

This blog uses Google Analytics for visit statistics and content analysis, and does not intentionally send information that directly identifies users, such as names, email addresses, or phone numbers, to Google Analytics.

Google Analytics 4 does not log or store IP addresses, although IP addresses may be processed in the course of providing the service, for example to derive approximate location.

The retention period for user-level and event-level data in this blog’s Google Analytics is set to 14 months. Information processed through Google Analytics may be processed outside the Republic of Korea or outside the user’s country of residence as part of Google’s global service delivery.

For more detailed visit analysis, this blog exports and stores Google Analytics data in BigQuery on Google Cloud, managed by the blog operator. BigQuery data is stored in the Seoul region (asia-northeast3).

Data exported to BigQuery may include event and page usage records, pseudonymous identifiers (cookie-based identifiers), browser and device information, approximate location, and traffic sources. It does not include information that directly identifies users, such as names or email addresses, or IP addresses.

Data stored in BigQuery is managed separately from the Google Analytics retention setting and is retained for up to 25 months and then automatically deleted. However, statistical data that has been aggregated, with identifiers and personal information removed so that individuals cannot be identified, may be retained separately for as long as needed for analysis. This data is accessible only to the blog operator, is used solely for statistical analysis, and is not provided to third parties.

3. Use of Microsoft Clarity

This blog uses Microsoft Clarity, provided by Microsoft, to analyze how users interact with the site and to improve content structure and user experience.

Microsoft Clarity may process the following information.

  • Page visits and usage records
  • Click and scroll information
  • Mouse or pointer movements
  • Screen and browser size information
  • Page rendering and DOM-related information
  • Browser and device information
  • Pseudonymous identifiers related to sessions and page use
  • Other technical information related to site usage behavior

This information may be used for heatmaps, session replays, behavior analysis, and improving site usability.

Microsoft Clarity may use cookies such as _clck and _clsk or similar identification technologies.

Under Microsoft’s policies, session replay data is generally retained for 30 days, and click data, heatmaps, and some aggregated data may be retained for up to 9 months.

In regions where prior consent is required by law, Clarity’s cookies and analytics features may be limited depending on the user’s consent status.

4. Use of Cloudflare and Site Security Services

This blog uses Cloudflare’s CDN and WAF (Web Application Firewall) to improve content delivery speed, provide stable service, and prevent security threats.

In addition, separate firewall and access protection features are used to strengthen security at the WordPress server level.

The following information may be processed when you access the site.

  • IP address and network information
  • Date and time of access
  • Requested URL
  • Browser and device information
  • HTTP request and response information
  • Abnormal access or request patterns
  • Technical information related to security threat detection

This information may be processed to deliver content, improve site performance, ensure service stability, and detect and block malicious requests, automated access, spam, and security attacks.

5. Use of Image Optimization Services

This blog uses Optimole to improve image delivery speed and site performance.

The following information may be processed in the course of providing the service.

  • IP address
  • Browser and device information
  • Time of access and request
  • Requested image or page information
  • Network request information

This information may be used for image optimization, content delivery, caching, and improving site performance.

6. Comments and Spam Prevention

This blog may operate the WordPress comment feature so that users can leave their opinions.

A name and email address are not required to post a comment, and commenter avatars or the Gravatar feature are not used.

The following information may be processed when posting a comment.

  • Comment content entered by the user
  • IP address
  • Browser and User-Agent information
  • Date and time the comment was posted
  • The post on which the comment was made and related request information

If a user voluntarily enters information in optional fields, that information may also be processed together with the comment.

This blog uses Antispam Bee to detect and block spam comments.

Comments classified as spam may be retained for up to 30 days for management and security purposes and then automatically deleted.

Published comments may be retained for as long as necessary to operate and manage comments, and may be deleted upon the user’s request or when there is no longer an operational need to retain them.

7. Cookies and Similar Technologies

This blog and the external services it uses may use cookies or similar technologies for the following purposes.

  • Visit statistics analysis
  • Usage behavior analysis
  • Improving user experience
  • Ensuring site security and stability
  • Providing services and maintaining functionality
  • Measuring affiliate link clicks and conversions

The main services that may currently use cookies or similar identification technologies include the following.

  • Google Analytics
  • Microsoft Clarity
  • Certain WordPress features
  • Site security and operational features
  • Affiliate marketing service providers

Users can allow or block cookies through their web browser settings and can also delete cookies that have already been stored.

If cookie use is restricted, visit statistics analysis, usage behavior analysis, affiliate tracking, or some site features may not work properly.

In regions where prior consent is required by law, users may be given choices regarding cookies and the processing of analytics information, and where a consent management feature is in place, users can change their choices or withdraw their consent.

8. Possible Future Use of Google AdSense

This blog does not currently use Google AdSense.

If Google AdSense is introduced in the future, Google and ad technology providers may process cookies, local storage, online identifiers, device information, and site usage information to serve ads, manage ad frequency, measure ad performance, prevent invalid traffic, and personalize ads.

Where personalized ads are served, information for ad personalization may be processed in accordance with the user’s consent status and applicable laws.

When AdSense is actually introduced, this blog intends to update this Privacy Policy, cookie settings, and any necessary consent procedures to reflect actual operations.

9. Affiliate Marketing

This blog participates in affiliate marketing programs when introducing products, accommodations, transportation, travel services, and other related products and services.

Some posts or pages may contain affiliate links, and these links may include identifiers or tracking parameters used to verify the affiliate relationship.

When a user clicks an affiliate link, the external service provider may process the following information.

  • IP address and network information
  • Browser and device information
  • Referrer information
  • Date and time of the click
  • Affiliate identifier
  • Whether a purchase, booking, or conversion occurred
  • Cookies and other online identifiers

The specific processing methods, retention periods, and use of cookies are governed by each affiliate service provider’s privacy policy and service settings.

When a user purchases a product or books accommodation, transportation, or other services through an affiliate link, this blog may receive a commission or other compensation.

Where an affiliate relationship exists, this is clearly disclosed on the relevant post or page.

The existence of an affiliate relationship does not guarantee the quality, price, availability, or suitability of the product or service.

10. Backup and Recovery

This blog periodically backs up site data to store it securely and restore it in the event of failure. The data may be stored on Google Drive.

Backups may include the following information.

  • Posts and pages
  • Comments and comment-related data
  • Site settings
  • Database
  • Plugin and theme data
  • Uploaded images and files

Comment content, IP addresses, and other technical information processed through comments may also be included in database backups.

Backup files may be retained on a rotating basis according to the configured retention policy.

11. Other Site Operation Plugins

This blog may use WordPress plugins for site operation, including multilingual support, search engine optimization, design, caching, post view counting and popular content display, and administrator account protection.

These features are mainly used for the following purposes.

  • Providing multilingual content
  • Search engine optimization
  • Site design
  • Counting post views and displaying popular content
  • Caching and performance improvement
  • Administrator account and site security

This blog does not use these features for personalized advertising or individual profiling of users.

12. External Services and Processing Outside Korea

This blog uses the following external services.

  • Google: Google Analytics, Google Drive, Google Cloud (BigQuery)
  • Microsoft: Microsoft Clarity
  • Cloudflare: CDN and security services
  • Optimole: image optimization and delivery
  • Affiliate marketing programs and affiliate service providers

Additional advertising services, such as Google AdSense, may be introduced in the future.

In this process, some information may be stored or processed on servers located outside the Republic of Korea or outside the user’s country of residence.

The specific storage locations, processing methods, retention periods, and safeguards of each service may vary according to each service provider’s privacy policy, contracts, and service settings.

13. Advertising, Affiliates, and Use of Personal Information

The operator of this blog does not sell users’ personal information.

This blog participates in affiliate marketing programs and may receive a commission when users purchase products or book services through certain affiliate links.

Affiliate service providers may process cookies, online identifiers, device information, click information, or purchase and booking information to verify affiliate relationships, measure clicks and conversions, and settle commissions.

The following services are not currently used.

  • Google AdSense
  • Google Ads conversion or remarketing tracking
  • Meta Pixel

If advertising services are introduced in the future, this Privacy Policy and any necessary consent procedures will be updated to reflect the actual processing of information.

14. Retention and Use Period of Personal Information

Information processed by this blog may be retained for as long as necessary for each purpose of use.

  • Google Analytics user-level and event-level data: 14 months
  • BigQuery copy of Google Analytics data: up to 25 months
  • Aggregated statistical data that cannot identify individuals: for as long as needed for analysis
  • Microsoft Clarity session replay data: 30 days
  • Microsoft Clarity click, heatmap, and some aggregated data: up to 9 months
  • Comments classified as spam: up to 30 days
  • Published comments: for as long as necessary to operate and manage comments
  • Security-related information: for as long as necessary for site security and operation
  • Post view statistics: for as long as necessary to compile and operate popular content
  • Affiliate click and conversion data: for as long as required by each affiliate service’s policies and for settlement
  • Backup data: according to the configured backup retention policy

When the purpose of processing has been achieved or the information no longer needs to be retained, it is deleted or destroyed in accordance with applicable laws and operational policies.

15. Users’ Rights and Choices

To the extent provided by applicable laws, users may request access to, correction, deletion, or restriction of processing of personal information relating to them.

Users can restrict or delete cookies through their browser settings.

Users who do not want their data collected by Google Analytics can use tools such as the Google Analytics Opt-out Browser Add-on provided by Google.

In regions where a consent management feature for cookies and analytics processing is provided, users can change their choices or withdraw their consent through the relevant settings.

Commenters may request the deletion of their comments and of information processed in connection with those comments.

Users outside Korea may have additional rights under the privacy laws applicable in their region.

16. Privacy Inquiries

Inquiries about the processing of personal information on this blog, or requests to exercise privacy rights, can be made through the contact below.

Privacy Officer: Blog operator
Email: [email protected]

Where necessary, reasonable steps may be taken to verify that the requester is the subject of the relevant information.

17. Changes to This Privacy Policy

This Privacy Policy may be revised when applicable laws, the services or plugins in use, advertising and affiliate services, methods of processing personal information, or the way the blog is operated change.

Any changes will be published on this page.

Effective date: October 16, 2026