Cookie Policy.
This Cookie Policy explains, in specific and practical terms, the small data files that Bralkon Journal stores in a reader's browser when they visit this website, why each one is used, how long it remains stored, and what choices a reader has over them. It should be read together with the Privacy Policy, which describes in broader terms how information connected with this website is handled. Where a technical term is used, such as "session cookie" or "first-party", it is explained in the surrounding text so that the policy can be understood without prior technical knowledge. A reader who wants to change a cookie choice at any point can do so through the Cookie Settings link available in the footer of every page.
1. What a cookie is
A cookie is a small text file that a website asks a browser to store, and that the browser then sends back to the same website on a later visit. Cookies are commonly used to remember a choice a reader has made, to keep a reader logged into a session-based feature, or to help a website understand, in aggregate, how its pages are used. A cookie set by Bralkon Journal directly is described as a first-party cookie, while a cookie set by an embedded third-party feature, such as an interactive map, is described as a third-party cookie. Cookies described in this policy do not, on their own, identify a reader by name, and none of them are used to compile an individual profile for resale or for advertising on other websites.
2. Categories of cookies used on this website
We group the cookies used on this website into three categories: strictly necessary cookies that support basic navigation and cannot be switched off without affecting core functionality, preference cookies that remember a choice such as the cookie consent selection itself, and analytics cookies that help us understand broad, aggregated readership patterns. We do not currently use cookies for personalised advertising, and no cookie on this website is shared with an advertising network for the purpose of following a reader across unrelated websites. The table below and the sections that follow list the specific cookies that may be set, their purpose, and their approximate lifespan, so that a reader can make an informed choice through the consent banner.
3. Strictly necessary and session cookies
A session-related cookie, commonly issued under a name such as PHPSESSID by the underlying web server technology, may be set to support basic page functionality such as the mobile navigation menu and the operation of the contact form. This cookie does not persist after the browser is closed, and it does not carry an advertising identifier of any kind. Because this category of cookie is necessary for the website to function correctly, it is not covered by the optional consent choices described in section 6, in line with common practice for strictly necessary cookies under applicable regulation. If a reader's browser is configured to block all cookies without exception, some interactive elements of the site, such as the mobile menu toggle, may not behave as expected, although the underlying editorial content will remain readable.
4. Preference cookies
A first-party preference cookie named ej_cookie_consent is set once a reader makes a choice in the cookie banner, and it records whether the reader selected "Accept All", "Accept Selected", or "Functional Only". This cookie is stored for up to one hundred and eighty days from the date it is set, after which the consent banner will appear again on the next visit so the choice can be renewed. The purpose of this cookie is solely to avoid repeatedly asking a returning reader for the same choice within a reasonable period, and its content is limited to the stored preference value with no additional personal detail attached. A reader can clear this cookie at any time through their browser settings, which will cause the consent banner to be shown again on the next page load.
5. Analytics cookies
Where analytics functionality is enabled on the website, a cookie following the common _ga naming convention, together with a related cookie such as _ga_ followed by a site-specific identifier, may be stored for up to thirteen months to help distinguish separate visits and to support aggregate reporting on page views, approximate visit duration, and broad device or browser categories. These cookies are configured, where technically available, to work with IP address truncation or similar aggregation techniques so that reporting reflects overall trends rather than the behaviour of a single identifiable reader. Analytics reporting is reviewed periodically by the editorial team to understand which topics are of interest to readers and to identify pages that may need technical attention, and it is not used to build an individual profile for any other purpose. A reader who selects "Functional Only" in the consent banner will not have analytics cookies set on their browser for that visit.
6. How consent is collected and recorded
On a reader's first visit, or after a stored consent cookie has expired, a cookie banner is displayed offering the choice to accept all cookies, accept a selected subset, or accept functional cookies only. The choice made is recorded locally through the ej_cookie_consent cookie described in section 4, and no separate server-side record of an individual reader's cookie choice is kept beyond what is needed to apply that choice on the current device and browser. If a reader uses a different device or browser, or clears their cookies, the choice will need to be made again, since the preference is stored locally rather than tied to a reader account. The consent mechanism does not distinguish between readers by name or email address, since cookie consent operates independently of any contact form submission described in the Privacy Policy.
7. Third-party cookies from embedded features
The interactive location map on the Contact page is loaded from the Google Maps Platform, operated by Google LLC, and loading that embedded map may cause Google to set its own cookies in the reader's browser under Google's own published cookie and privacy practices, which are separate from and not controlled by Bralkon Journal. Web fonts used across the site are served by Google LLC through the Google Fonts service; depending on how a browser handles font requests, this may involve a request to Google's servers without necessarily setting a cookie, and Google's own documentation describes the current handling of that request in more detail. We review the embedded features used on this website periodically to confirm that they remain limited to the purposes described here, and we would update this section if a new embedded feature that sets its own cookies were introduced.
8. Retention and expiry summary
To summarise the lifespans described above in one place: the session cookie described in section 3 expires when the browser is closed; the preference cookie described in section 4 is stored for up to one hundred and eighty days; the analytics cookies described in section 5, where enabled, are stored for up to thirteen months; and any third-party cookie described in section 7 is governed by the retention period set by the relevant third-party provider rather than by Bralkon Journal. Cookies that reach the end of their stated lifespan are automatically discarded by the browser without any action needed from the reader, and a reader can also remove any cookie manually at an earlier point through their browser's settings menu. We do not use any cookie on this website with a stated lifespan beyond thirteen months.
9. Managing cookies through your browser
Most browsers allow a reader to view which cookies are currently stored, delete some or all cookies, block new cookies from being set, or receive a notification before a cookie is stored, and the exact steps differ between browsers and browser versions. Blocking or deleting the strictly necessary cookie described in section 3 may affect features such as the mobile navigation menu, while blocking the preference or analytics cookies described in sections 4 and 5 will not affect access to any editorial content on the website. Because browser-level controls apply to the browser and device being used at the time, a reader who switches between a desktop browser and a mobile browser will need to apply the same preference separately on each. Further general guidance on browser cookie controls is usually available in the help section of each browser's own documentation.
10. Contact and complaints procedure
Questions about this Cookie Policy, or requests for more detail about a specific cookie listed above, can be sent to [email protected], by post to Bralkon Journal, Jalan Thamrin No. 12, 10350 Jakarta Pusat, DKI Jakarta, Indonesia, or by telephone at +62 21 2184 7202 during office hours, Monday to Friday, 09:00 to 17:00 WIB. We aim to acknowledge a cookie-related enquiry within five business days and to provide a full response within thirty calendar days. If a reader believes that a cookie has been used in a way that is inconsistent with this policy, they are encouraged to raise the matter with us directly in the first instance so that it can be reviewed and, where appropriate, corrected, before escalating the matter to the relevant supervisory authority described in the Privacy Policy.
11. Changes to this policy and revision log
We may update this Cookie Policy if the cookies used on the website change, for example if a new analytics tool or embedded feature is introduced, or if the applicable legal framework for cookie consent changes. Any update will be reflected in the effective date and version number shown at the top of this page, and significant changes will also be noted in the revision log below. The current and past revisions of this policy are summarised here: version 1.0 was published on 12 January 2026 and set out the original categories of strictly necessary, preference, and analytics cookies; version 1.1 was published on 4 April 2026 to add the description of third-party cookies associated with the Google Maps Platform embed introduced on the Contact page; version 1.2, the version currently in effect, was published on 18 August 2026 to add the named cookie examples, specific lifespans, and the retention and expiry summary in section 8.