Cookie policy.
This cookie policy sets out, in detail, the small files and similar technologies used by Drevak Journal, including their exact names, their purposes, their lifespans, and the choices available to a reader browsing from Indonesia or elsewhere. The editorial team has deliberately limited the site to the smallest set of technologies needed to operate a readable, secure publication, rather than deploying broad advertising or profiling scripts. This document should be read together with the separate privacy policy, which explains how any personal information connected with these technologies is otherwise handled. Where a cookie described below is optional, a reader who declines it can still read every published article without any loss of core functionality. The policy applies to every page served under the drevak.info domain, including the homepage, article pages, the contact page, and every legal page, and it applies equally whether a reader arrives from a search engine, a shared link, or a direct visit.
1. Scope of this document
This policy covers every cookie and comparable browser-storage technology that Drevak Journal itself sets when a reader visits the site, and it does not attempt to describe technologies controlled by unrelated third parties that a reader might encounter elsewhere on the internet. It applies to visitors browsing from Indonesia, where the editorial desk is based, and equally to visitors reaching the site from any other country, since the same three technologies described below are used regardless of a visitor's location. The scope excludes any offline record-keeping the publication may undertake, such as postal correspondence logs, which are instead addressed in the separate privacy policy referenced throughout this document. Where a future feature, such as an embedded video or an embedded map, would introduce an additional cookie, that addition will be disclosed here by name and by lifespan before the feature is switched on for readers.
2. What a cookie is
A cookie is a small text record that a browser stores on behalf of a particular website, and that the website can read back on a later visit to recognise a returning browser. A cookie can remember a simple preference, such as a cookie-banner choice, support a temporary browsing session, such as a form-protection token, or contribute to an aggregate statistic about how many times a page was viewed. A cookie set by Drevak Journal does not, on its own, reveal a reader's name, email address, or postal address, and none of the cookies described in this policy are used to build an individual advertising profile. Similar technologies, such as local browser storage used to remember a display preference, are treated the same way as cookies throughout this document for clarity, and any reference below to a cookie should be read as covering both mechanisms unless stated otherwise.
3. Data collected through cookies
The data recorded through the three technologies described in this policy is limited to a consent value, a temporary form-protection token, and an aggregate, non-identifying record of page views by article and by date. None of these records include a reader's name, postal address, telephone number, or the content of any message submitted through the contact form, and none of them are cross-referenced against any other list the publication holds. The aggregate analytics record, described fully in section 8, groups visits by broad categories such as country and referring page rather than by individual browser fingerprint, and it is not used to reconstruct an individual reading history tied to a named person. Where a reader also submits information directly through the contact form, that separate submission is governed by the privacy policy rather than by this cookie policy, since it is not stored inside a cookie at all.
4. Legal basis for use
The strictly necessary cookie described in section 6, which records a reader's banner choice, is used on the basis that it is required for the basic functioning of a feature the reader has actively engaged with, namely the cookie banner itself, and it is therefore set without requiring a separate opt-in. The session-scoped form-protection technology described in section 7 is used on the same necessity basis, since the contact form cannot operate its safeguard against automated submission without it. The optional analytics technology described in section 8 is used only where a reader has given affirmative consent through the banner, and it is never activated by default or set before that consent is recorded. Where local law in a reader's country requires a different basis or a different consent mechanism, the editorial desk will adapt the banner presented to that reader accordingly, though the underlying three technologies themselves remain unchanged.
5. Categories of cookies used
Drevak Journal groups its cookies into three categories that mirror the choices offered in the cookie banner: functional cookies that are necessary for the banner and basic site behaviour to work, a session-scoped technical record that supports the contact form, and an optional analytics cookie that is set only if a reader actively accepts it. No cookie in any of these three categories is used for third-party advertising, retargeting, or cross-site tracking. Each category is described individually, by name and lifespan, in the sections that follow so that a reader can identify exactly what is stored on their device, and each category can be independently accepted or declined through the banner described in section 7 of this policy without affecting the other two.
6. Functional cookie: drevak_cookie_consent
The cookie named drevak_cookie_consent records the choice a reader makes when the banner first appears, storing a simple value such as all, selected, or functional depending on which button was used. This cookie lasts for one hundred eighty days from the date it is set, after which the banner will appear again so the reader can confirm or update their choice. It is classified as strictly necessary because, without it, the banner would reappear on every page load, which would itself be a poorer experience than remembering a single prior choice. A reader can clear this cookie at any time through their browser's own settings, which will cause the banner to reappear on the next visit, and doing so has no other effect on the availability of any article on the site.
7. Session technology: drevak_session
The contact page may set a short-lived session record named drevak_session when a reader begins filling in the contact form, and this record supports basic form protection against automated submission. The record lasts only until the browsing session ends and, in any case, for a maximum of twenty-four hours, after which it expires automatically regardless of whether the session is still open. It does not contain the text of any message typed into the form, and it is not read by any page outside the contact flow. A reader who disables this technology through browser settings may find that the contact form does not submit correctly, since the record is used specifically to confirm that a submission came from the form itself rather than from an automated script.
8. Optional analytics cookie: drevak_analytics
If a reader accepts analytics through the cookie banner, an aggregate record named drevak_analytics may be set for a period of up to fourteen months from the date of acceptance. This record helps the editorial team understand general reading patterns, such as which articles receive the most attention over a given month, without assembling a named profile tied to an individual reader's real-world identity. The underlying measurement is carried out using a self-hosted installation of Umami Analytics, run on infrastructure the publication controls directly rather than through a third-party advertising network, and no data collected through this cookie is sold or shared for advertising purposes. Analytics are entirely optional, and declining them, or selecting functional-only in the banner, does not restrict access to any article, image, or page on the site. A reader who initially accepts analytics can withdraw that acceptance at any time using the procedure described in section 10 below.
9. Named processors and infrastructure providers
Beyond the self-hosted analytics installation described in section 8, Drevak Journal relies on a small number of infrastructure providers to keep the site available, including a hosting provider that serves the underlying web pages and a domain registrar that maintains the drevak.info domain record. These providers process technical connection data, such as an IP address and a timestamp, only to the extent necessary to deliver the requested page, and they do not receive the content of the cookies described in this policy. The editorial desk maintains a written arrangement with its hosting provider covering the security and confidentiality of any data passing through its servers, consistent with the commitments described in the separate privacy policy. No cookie data described in this document is passed to an advertising network, a data broker, or a social-media platform, and the publication does not currently use any such service on its editorial pages.
10. How to change or withdraw a cookie choice
A reader can change a previously recorded cookie choice at any time by selecting the Cookie Settings link that appears in the footer of every page, which reopens the consent banner and allows a new selection to be recorded. A reader can also use their own browser's cookie management controls to view, block, or delete any cookie set by this or any other website, independently of the in-page banner. Blocking or deleting the functional cookie described in section 6 will simply cause the banner to reappear on the next visit, without any other effect on the reading experience. Withdrawing consent for the optional analytics cookie described in section 8 takes effect for future visits and does not retroactively alter aggregate statistics already recorded, since those earlier statistics are stored only in aggregate form and are not linked back to an individual browser once recorded.
11. Cookies and mobile browsing
The cookie behaviour described in this policy applies equally to readers using a desktop browser and to readers using a mobile browser, since the underlying technology functions the same way across device types. A mobile browser's own settings menu typically offers the same options to view or clear stored cookies as a desktop browser, and a reader on a mobile device can use the Cookie Settings link in the footer in the same way as described in section 10. Drevak Journal does not use a separate mobile application, so no additional application-level tracking technology applies beyond what is described in this document. A reader switching between a desktop and a mobile device will be shown the cookie banner separately on each device, since a cookie choice is stored per browser and per device rather than centrally.
12. International transfers connected to cookie data
Where the aggregate analytics record described in section 8 is processed on infrastructure located outside Indonesia, the editorial desk selects hosting regions that maintain contractual and technical safeguards consistent with the transfer commitments described in the separate privacy policy. The strictly necessary and session-scoped technologies described in sections 6 and 7 remain on the device itself and are read only by the page that set them, so no separate cross-border transfer of their content occurs beyond the reader's own request to load a page. Any change to the hosting region used for the analytics installation will be reflected in the revision log in section 13 before it takes effect, together with a description of the safeguard applied to that region. A reader with a question about a specific transfer arrangement can raise it through the contact procedure described in section 14.
13. Retention, storage, and revision log
Each cookie's lifespan is stated individually in sections 6 through 8, and no cookie described in this policy persists beyond the fourteen-month maximum that applies to the optional analytics record. This policy was last substantively revised on 18 August 2026, at which point the three named cookies and their stated lifespans were confirmed as accurate and current, and dedicated sections on legal basis, named processors, and international transfers were added to the document. On 2 June 2026, an earlier revision first introduced the drevak_analytics cookie and its fourteen-month retention period, replacing an undated general reference to analytics that had appeared in the original publication of this page. On 14 January 2026, the policy was first published alongside the launch of the site, describing only the strictly necessary consent cookie that was in use at that time. Any future addition or removal of a cookie will be reflected here with an updated revision date before the change takes effect.
14. Questions and contact procedure
A reader with a question about any cookie described in this policy, or about how to exercise the choices described in section 10, can contact the Jakarta editorial desk at [email protected]. The desk aims to acknowledge cookie-related questions within two business days and to provide a substantive response within five business days, during its published hours of Monday to Friday, 09:00 to 17:00 WIB. Postal correspondence can be sent to Jalan Imam Bonjol No. 34, 10310 Jakarta Pusat, DKI Jakarta, Indonesia, and time-sensitive matters can be raised by telephone at +62 21 2184 7205 during the same published hours. This cookie policy should be read alongside the separate privacy policy, which explains the broader handling of any personal information connected with the technologies described here, and a reader who is not satisfied with the response received may also refer to the complaints procedure set out in that privacy policy.