Updated 5 October 2026

Cookie policy

This page explains the small browser technologies used by Genese. The site is designed to remain readable without optional measurement cookies. Our current banner records a visitor’s choice so the question is not shown on every visit.

  1. 1. What cookies do

    Cookies are small text values stored by a browser. They can remember a preference, support a session or help a publisher understand broad use. They cannot, by themselves, reveal a person’s identity or medical condition. For example, a simple preference cookie might store the single word accept, which tells the site only that the banner was dismissed, not who the visitor is. The practical consequence is that a cookie alone cannot be used to build a named profile unless it is deliberately combined with other identifying information Genese does not collect through routine browsing. An edge case involves a shared household computer, where a preference stored by one family member may apply to the next person using the same browser, since cookies are tied to a browser rather than a person. This basic explanation applies to every cookie described later on this page.

    • a) A cookie stores a small value in the browser, not a person's name or identity.
    • b) Cookies are tied to a browser, not verified to an individual user.
    • c) Genese does not combine cookie identifiers with contact-message content.

  2. 2. Essential preference

    Genese uses the local browser key cookieChoice with the value accept or reject. It is used only to prevent the banner from returning immediately after a choice. It remains until the visitor clears site data or a browser policy removes it. For example, a visitor who selects Accept on a desktop browser will not see the banner again on that same browser until the value is cleared or expires through browser policy. The practical consequence is that the banner behaviour is consistent and predictable rather than appearing on every single page load. An edge case involves switching between a phone and a laptop; because cookieChoice is stored per browser, the choice made on one device does not automatically transfer to the other, so the banner may appear again on the second device. No identifying detail beyond the accept or reject value is stored in this cookie.

    • a) Name: cookieChoice. Values: accept or reject.
    • b) Scope: first-party, specific to the browser on which it is set.
    • c) Lifespan: persists until browser storage is cleared or a browser policy removes it.

  3. 3. Session cookies

    At present Genese does not require an account or a logged-in session. If a future feature introduces a session cookie, the name, purpose, secure attributes and expiry will be documented here before launch. The site will not use a hidden session to create a health profile. For example, if Genese later introduces a saved-articles feature requiring sign-in, a session cookie would identify an active login session only for the duration needed to keep a reader signed in. The practical consequence of not currently requiring an account is that no reader is tracked across visits through a login-linked identifier today. An edge case would be a temporary session token used solely to protect the contact form against automated submission, which, if introduced, would be classified and documented as a strictly necessary cookie rather than a tracking one. Any such addition would be announced on this page with its name, purpose and expiry before launch.

    • a) No account or login session currently exists on the site.
    • b) A future session cookie would be strictly necessary and limited to maintaining sign-in state.
    • c) Any session cookie introduced later will be documented here before deployment.

  4. 4. Analytics

    Optional analytics are not necessary to read the website. If enabled, they will load only after a visitor selects acceptance where applicable and will use an explained provider, purpose and lifespan. Rejecting optional analytics will not reduce access to articles. For example, an aggregate measurement tool might report that a glossary page received a certain number of views in a month, without identifying which specific visitor read it. The practical consequence of this aggregate approach is that editorial decisions about which topics to expand can be informed by general interest without building an individual reading history. An edge case involves a visitor who accepts analytics and later changes their mind; clearing the cookieChoice value and selecting Reject on the next visit stops further collection by that tool going forward, though data already aggregated before the change is not retroactively altered. Any analytics provider used in the future will be named here along with its specific cookie or storage identifier.

    • a) Analytics, where used, report aggregate patterns rather than individual reading histories.
    • b) Access to every article is unaffected by accepting or rejecting optional analytics.
    • c) A later change of choice stops future collection but does not alter already-aggregated data.

  5. 5. Preferences

    Preference storage may remember choices such as the cookie response or accessibility display setting. Such values are intended to improve usability, not to infer sensitive traits or deliver personalised health advertising. For example, a larger-text display preference, if introduced, would simply remember a visitor's chosen font size for their next visit to the same browser. The practical consequence is that preference storage makes repeat visits more convenient without building a profile used for targeted advertising. An edge case involves a preference that becomes outdated after a design update; in that situation the stored value may be ignored or reset automatically until the visitor sets a new preference under the updated design. Genese does not use preference cookies to tailor article recommendations based on assumed health status.

    • a) Preference values improve convenience, such as remembering a display setting.
    • b) Preferences are not used to infer health status or target advertising.
    • c) Outdated preference values may be reset automatically after a design update.

  6. 6. Third parties

    Embedded third-party content may set its own technologies when a visitor activates it. Genese limits embeds and cannot control a third party’s policy after navigation. Check the provider’s notice before submitting information on an external page. For example, an embedded video player, if used on an article page, may set its own cookies once a visitor presses play, separate from anything Genese controls. The practical consequence is that interacting with an embed can trigger a third party's own cookie policy rather than ours. An edge case involves an embed that loads automatically rather than on click; where that occurs, Genese aims to use click-to-load designs so a third-party cookie is not set before the visitor chooses to interact with the content. We review embedded content periodically to limit unnecessary third-party exposure.

    • a) Embeds that require a click to activate reduce automatic third-party cookie exposure.
    • b) A third party's own cookie notice governs any cookie it sets once activated.
    • c) Embedded content is reviewed periodically to limit unnecessary third-party exposure.

  7. 7. Browser controls

    Most browsers allow visitors to inspect, delete or block stored values. Blocking all storage may cause the banner to return, but the editorial pages should remain available. Device-level privacy settings may also alter how consent is remembered. For example, a visitor using a browser's built-in tracking protection may find that the cookieChoice value is cleared automatically after a period of inactivity, which is a setting controlled by the browser rather than by Genese. The practical consequence is that the banner reappearing is not necessarily a technical fault on our side; it often reflects a browser or device privacy setting working as designed. An edge case involves a browser extension that blocks all first-party storage; in that situation the banner may appear on every visit because no preference can be retained at all. Instructions for managing cookies vary by browser and are generally available in that browser's own help documentation.

    • a) Browser tracking-protection settings can clear cookieChoice automatically after inactivity.
    • b) A storage-blocking extension may prevent any preference from being remembered.
    • c) Cookie management instructions are available in each browser's own help documentation.

  8. 8. Retention

    The cookieChoice preference is stored in the browser rather than in a Genese account. Optional analytics records, if introduced, will be retained for no more than 13 months unless a shorter period is stated. Server security logs follow the 30-day period in the privacy policy. For example, because cookieChoice lives in the visitor's own browser rather than on a Genese server, there is no central database entry for Genese to delete when a visitor clears that cookie themselves. The practical consequence is that a visitor has direct, immediate control over that particular value without needing to contact us. An edge case involves an analytics provider that retains aggregated, non-identifying statistics for internal reporting slightly longer than the 13-month consent record itself; where that occurs it will be described in the specific provider's entry once such a tool is introduced. These retention figures are reviewed whenever the site's cookie configuration changes.

    • a) cookieChoice: stored client-side; no separate Genese server record exists to delete.
    • b) Optional analytics consent records: retained for up to 13 months where applicable.
    • c) Retention figures are reviewed whenever the site's cookie configuration changes.

  9. 9. Consent withdrawal

    Clear site storage in the browser to withdraw a recorded choice, then revisit the site and select a different option. You may also contact Genese and ask for help understanding the current cookie configuration. For example, a visitor using a shared office computer might clear only the cookieChoice value through browser settings without clearing saved passwords or bookmarks, since browsers typically allow clearing cookies selectively by site. The practical consequence is that withdrawing a cookie choice does not require a full browser reset. An edge case involves mobile browsers with limited settings menus, where clearing site data may require going through the device's general application settings rather than an in-browser control; the browser's own help pages typically explain this per device type. Once cleared, the next visit will show the cookie banner again so a fresh choice can be recorded.

    • a) Clearing cookieChoice alone does not require a full browser reset.
    • b) Mobile devices may require clearing site data through device settings rather than an in-browser menu.
    • c) The cookie banner reappears automatically once the stored choice is cleared.

  10. 10. International processing

    Infrastructure supporting the website may operate across borders. Genese requires providers to limit processing to service delivery and uses safeguards appropriate to the information involved. Cookie identifiers are not intentionally combined with contact messages. For example, a hosting provider's content delivery network may process a request from a reader in one country through a server located in another, with the cookie value simply travelling along as part of that routine request. The practical consequence is that the physical location of a server does not change which values are stored or how long they are kept; those rules remain as described on this page regardless of server location. An edge case involves a future analytics provider based outside Indonesia; if introduced, Genese would require contractual safeguards comparable to those described in the privacy policy before enabling it. This approach is intended to keep cookie-related processing narrow and well defined even when infrastructure spans multiple countries.

    • a) Server location does not change the retention or purpose rules described on this page.
    • b) A future cross-border analytics provider would require contractual safeguards before use.
    • c) Cookie identifiers remain separate from the content of contact messages.

  11. 11. Changes

    Revision history: 5 October 2026, wording aligned with the fixed bottom-right banner and local cookieChoice behaviour. Future additions will name new cookies, purposes and lifespans before they are deployed. For example, if Genese introduces a reader survey tool, its cookie name, purpose and retention period would be added to this page as a new dated entry before the survey goes live, not after. The practical consequence is that a returning visitor can always check this page to see the complete, current list of cookies in use rather than relying on memory of an older version. An edge case involves a cookie that is retired rather than added; in that situation the entry describing it will note that it is no longer in use, with the date of removal, rather than being deleted from this page's history silently. This log is intended to give readers a transparent record of how cookie use on Genese has evolved.

    • a) 5 October 2026: current version aligned with the fixed bottom-right banner and cookieChoice behaviour.
    • b) New cookies are documented before deployment, not retroactively.
    • c) Retired cookies are noted as discontinued along with the date of removal.

  12. 12. Contact

    For questions, contact Genese at Jalan Kemang Raya No. 12, Mampang Prapatan, Jakarta Selatan, 12730, DKI Jakarta, Indonesia, or call (021) 7586-9172. For example, a reader uncertain whether a specific plugin on an article page sets a cookie may ask us to confirm before assuming either way. The practical consequence of asking directly is a specific, accurate answer rather than a generic restatement of this page. An edge case involves a question that also touches the separate privacy policy, such as how a cookie-choice record interacts with a contact message; in that situation we will refer to both documents together in the reply. Written correspondence by post to the address above is accepted as an alternative to a phone call.

    • a) Specific questions about a particular page or feature receive a specific, individual answer.
    • b) Questions spanning both cookies and broader privacy topics are answered with reference to both pages.
    • c) Written correspondence by post to the address above is accepted as an alternative to a phone call.