Breeze in Busan / Policies & Standards
Site & Legal
Cookie Policy
A technical record of the cookies, browser storage, analytics and embedded services currently used by Breeze in Busan.
Technical scope
What this policy covers
This policy covers cookies and comparable browser technologies used on breezeinflow.com. It distinguishes first-party identifiers, browser storage, analytics and third-party embeds rather than calling every technology a cookie.
Current inventory
Technologies currently used
| Name / technology | Provider | Purpose | Storage / duration | Category |
|---|---|---|---|---|
| jwtToken | Breeze in Busan | Authenticated member and administrator session | HTTP-only first-party cookie; up to 7 days | Essential |
| anonymousUserId | Breeze in Busan | One response per article or poll; anonymous view and reader-history state | First-party cookie; up to 1 year | Functional / participation |
| theme | Breeze in Busan / next-themes | Remember light, dark or system appearance | Browser local storage; until cleared | Preference |
| subscribed | Breeze in Busan | Remember that the subscription interface completed locally | Browser local storage; until cleared | Preference |
| user | Breeze in Busan | Display selected signed-in account details in the site header | Browser local storage; removed at sign-out or when the session is no longer valid | Functional |
| _ga and GA4 property identifiers | Google Analytics 4 | Page, interaction and performance measurement | Provider-set browser identifiers; duration depends on the GA4 property and browser controls | Analytics |
| Cloudflare request analytics | Cloudflare | Delivery, security and aggregate request/path measurement | Infrastructure-level request data; not a Breeze advertising cookie | Essential / analytics |
| YouTube embed | Google / YouTube | Display video embedded in an article | Third-party requests and storage may occur when an embedded player loads | Embedded third party |
First party
Essential and functional technologies
The authentication cookie is needed to maintain a signed-in session. The anonymous identifier supports per-reader features such as one Reader Signal response per article, poll participation and reading history without using an email address as the identifier.
Theme, signed-in header and subscription-state entries are local browser preferences. Clearing them does not remove server-side account, newsletter or participation records.
Measurement
Google Analytics and Cloudflare
Google Analytics 4 measures public-page use through page location, path, title, referrer and hostname, along with selected article, section, newsletter and Web Vitals events. Search queries and newsletter names, email addresses, email domains and name lengths are not included in Breeze's custom analytics events.
Cloudflare supplies delivery, security and aggregate traffic information. A server-side newsroom process can import request, page-view, visitor and path totals for operational analysis.
The site does not currently provide an in-page analytics preference control. Readers can use browser and Google Analytics controls described below.
External media
Embedded and linked services
Articles can contain YouTube players. Breeze rewrites supported article embeds to YouTube's privacy-enhanced domain. The player can still make third-party requests when it renders, and further YouTube storage or processing may occur when a reader plays or interacts with it.
Ordinary links to external websites do not make those sites part of Breeze. Their privacy and storage practices apply when a reader visits them.
Reader control
Managing cookies and browser storage
Browser controls can block or clear cookies and site data. Blocking jwtToken prevents a persistent signed-in session. Clearing anonymousUserId may create a new anonymous identifier and can affect duplicate-response and history features. Clearing local storage resets theme, signed-in header and subscription-interface preferences.
Google also provides controls for Analytics and advertising settings. Breeze does not present advertising cookies as part of its current inventory.
Maintenance
Changes and contact
Adding an analytics provider, advertising technology, consent manager, member service or new embedded platform requires a review of this inventory and the Privacy Policy.
Questions about this inventory may be sent to [email protected].