Cookie Policy
This Cookie Policy describes the small text files and comparable browser storage that Elaron Journal uses on elaron.info, why each one exists, how long it is kept, and how a reader can change their preferences at any point. It should be read alongside the Privacy Policy, which explains our broader approach to personal information.
1. Purpose and scope
This notice covers cookies and similar storage set by elaron.info itself, known as first-party cookies, and by the limited set of third-party tools we use to keep the site secure and to measure readership when permission is given. It applies to every page a reader can reach from the homepage, including articles, the About and Methodology pages, and the Contact page. It does not apply to any external website a reader might open from a link within an article, since that site sets its own cookies under its own policy. If a reader arrives at elaron.info from a search engine or a social platform, any cookie set by that referring service before arrival is outside the scope of this document.
2. What a cookie is
A cookie is a small piece of text that a website asks a browser to store, usually consisting of a name, a value, and an expiry date. The browser then sends that text back to the website on later visits so the site can recognise returning behaviour, such as a previously selected preference. Cookies cannot, by themselves, read information from other websites or from files stored elsewhere on a device, and none of the cookies described below can access a reader's contacts, photographs, or location. Some functions on this page rely on comparable browser storage rather than a classic cookie, and where that is the case we describe it using the same categories for clarity.
3. Session cookie
A cookie named session_id is created when a reader opens the site and is used to support basic navigation and elementary protection against automated abuse of the contact form. It contains a randomly generated value with no personal meaning on its own and cannot be reversed to reveal a name or email address. This cookie expires automatically when the browser session ends, meaning it is removed once the browser is fully closed rather than persisting across visits. Because it is necessary for the site to function correctly, this cookie is set regardless of the choice made in the cookie banner, consistent with the "strictly necessary" category recognised in most cookie frameworks.
4. Preference cookie
A cookie named cookie_consent records whether a reader selected "Accept All", "Accept Selected", or "Functional Only" in the banner shown on first visit. It typically lasts 12 months from the date it is set, after which the banner will appear again so the choice can be renewed. The value stored is limited to the selected option and the date it was recorded; it does not contain the text of any message sent through the contact form or any browsing history. Clearing browser cookies, or visiting from a new browser or device, removes this record and causes the banner to reappear on the next visit.
5. Analytics cookies
When a reader selects an option that includes analytics, cookies typically named _ga and _ga_<container-id>, associated with a widely used web analytics service, may be set to distinguish one visit from another and to group pages viewed during a single session. The _ga cookie is generally retained for up to 13 months, and the session-scoped analytics cookie is retained for the shorter of 30 minutes of inactivity or the browser session, in line with the analytics provider's default configuration. These cookies are not active until a reader affirmatively selects the analytics option, and choosing "Functional Only" prevents them from being set. Reports produced from this data are viewed by the editorial team in aggregate form, such as total page views per article, and are not used to identify an individual reader.
6. Cookie summary table
| Name | Category | Purpose | Typical lifespan |
|---|---|---|---|
| session_id | Strictly necessary | Navigation continuity and basic form abuse prevention | Ends when browser session closes |
| cookie_consent | Preference | Stores the reader's cookie banner selection | 12 months |
| _ga | Analytics (optional) | Distinguishes unique visits for aggregate reporting | Up to 13 months |
| _ga_<container-id> | Analytics (optional) | Tracks session state for the analytics service | Up to 13 months, or session-scoped depending on activity |
7. Legal basis for using cookies
Strictly necessary cookies are used on the basis of our legitimate interest in operating a functioning and reasonably secure website, an interest that is narrow in scope and proportionate to the minimal data involved. Preference and analytics cookies are used only on the basis of consent, gathered through the banner shown when a reader first visits, consistent with the consent-based approach expected under Indonesia's UU PDP for non-essential tracking technologies. Consent can be withdrawn at any time, and withdrawing it does not affect the reader's ability to browse the public pages of the site, since no content is placed behind an analytics-consent barrier.
8. Managing your preferences on this site
The cookie banner shown on first visit allows a reader to accept all cookies, accept a selected subset, or restrict the site to functional cookies only. A "Cookie Settings" link is available in the footer of every page, allowing the choice to be reopened and changed at any later time without needing to clear browser data manually. When a preference is changed, the new selection takes effect on the next page load, and any previously set analytics cookie that is no longer authorised is not renewed and will expire according to its normal lifespan. We recommend reviewing cookie preferences periodically, particularly after this policy is updated.
9. Browser-level controls
Most browsers allow cookies to be viewed, blocked, or deleted through their settings menu, and the exact steps vary by browser and device. Blocking all cookies, including the strictly necessary session cookie, may cause parts of the site, such as the contact form, to behave unexpectedly, since some basic functionality depends on it. Readers who wish to limit tracking more broadly can also use private or incognito browsing modes, which typically discard cookies once the window is closed, or browser extensions designed to manage third-party trackers. We do not control how a given browser labels or groups its cookie settings, so readers unfamiliar with these controls may wish to consult their browser's own help documentation.
10. Third-party providers involved
Where analytics is enabled by consent, the relevant cookies are associated with a third-party analytics provider that processes the resulting data on our behalf under standard data processing terms. That provider may store aggregated log data on infrastructure located outside Indonesia, including in the Asia Pacific region. No advertising network, social media pixel, or cross-site retargeting cookie is used on elaron.info at this time, and if that were to change in the future, this policy would be updated in advance and the change reflected in the revision log below.
11. International transfers related to cookie data
Because our analytics provider may process information outside Indonesia, cookie-derived identifiers can be transferred to servers located in other jurisdictions, principally within the Asia Pacific region. We select providers that apply recognised safeguards, including encryption in transit and contractual limits on further use of the data, and we do not enable any cookie whose primary purpose is to circumvent local data protection obligations. Readers who prefer not to have any information leave Indonesia can select "Functional Only" in the banner, which disables the analytics cookies described in section 5.
12. Retention and deletion
Each cookie's lifespan is set out in the summary table above and is not extended beyond the stated period through automatic renewal; when a cookie expires, the browser deletes it and, if the relevant feature is still needed, a fresh cookie is issued on the next qualifying visit. A reader can also delete any cookie manually at any time through browser settings, which takes effect immediately regardless of the original expiry date. We periodically review whether each cookie remains necessary for its stated purpose and remove any cookie that is no longer in active use from both this policy and the underlying site code.
13. Complaints and contact
Questions or concerns about cookies used on this site can be sent to [email protected], or by post to Jalan Sudirman No. 45, 12930 Jakarta Selatan, DKI Jakarta, Indonesia. We aim to acknowledge a cookie-related query within 5 business days and to provide a full response within 30 calendar days, consistent with the timelines described in our Privacy Policy. If a reader remains unsatisfied after our response, they may raise the matter with Indonesia's competent personal data protection authority under the UU PDP, or with the equivalent authority in their own country of residence.
14. Changes to this policy and revision log
We may revise this Cookie Policy when we add, remove, or change a cookie, or when the underlying law or our analytics configuration changes. Material updates are reflected in the "Updated" date at the top of this page and summarised in the log below, so that a returning reader can quickly identify what has changed since their last visit.
- Version 1.0 — 3 January 2026: Initial publication describing the session and preference cookies in use at launch.
- Version 1.1 — 22 March 2026: Added the analytics cookie category and the cookie summary table with named cookies and lifespans.
- Version 1.2 — 18 August 2026: Clarified browser-level controls, named the international transfer considerations for analytics data, and set out complaint response times.
This document is provided for general information and does not constitute legal advice. Cookie names and lifespans reflect typical configuration and may vary slightly as browsers and service providers update their own defaults.