Cookie policy

Effective 1 January 2026; reviewed 1 October 2026. This page explains the small technologies Bliro may use when you browse. It is meant to complement, not replace, the fuller explanation of personal information handling found in the Bliro privacy policy. Where this page names a specific technology, that name reflects the current implementation and may change if the underlying hosting or analytics tool is updated. Readers who want to adjust their preference can do so at any time through the banner described in Section 5, without needing to contact the editorial desk. This page applies to the Bliro domain and does not describe cookies that a third-party site you visit through a link might set on its own.

1. What cookies do

This policy is published by Bliro, registered in Indonesia under Nomor Induk Berusaha (NIB) 0812026004571 and Nomor Pokok Wajib Pajak (NPWP) 03.147.882.6-016.000, with its editorial office at Jalan Cempaka Putih Raya No. 15, RT.005/RW.001, Cempaka Putih Timur, Jakarta Pusat 10510, Indonesia. Cookies are small files or browser storage values that remember a setting or help a service understand use. Bliro uses the least information needed for a calm, functional website. We do not use cookies to create health profiles. A cookie typically consists of a short identifier and an expiration date, stored by your browser and sent back to the site that set it on later visits. Some cookies are set directly by Bliro's hosting infrastructure, while others, where analytics is enabled, are set by a separate measurement provider acting on Bliro's instructions. The principle of using the least information needed means we avoid tracking technologies, such as persistent cross-site identifiers, that are not necessary for operating an editorial website. Because the site focuses on general wellness education rather than personalized health services, there is no technical need to link browsing behavior to a health profile. Bliro reviews its cookie configuration whenever the underlying hosting or analytics platform changes its defaults, to confirm the technologies in active use remain limited to the purposes described on this page.

  • a) First-party technologies: set directly by Bliro's hosting infrastructure.
  • b) Third-party technologies: set by an analytics provider only after consent.
  • c) No health profiling: browsing patterns are not linked to inferred medical conditions.

2. Essential technologies

Hosting and security systems may use short-lived session identifiers. These normally expire when your browser session ends. They support delivery, abuse prevention, and basic operation. Delivery support might include ensuring that a page you requested is served from the correct server in a load-balanced hosting environment. Abuse prevention relies on a short-lived identifier to recognize unusual request patterns, such as an automated script submitting the contact form repeatedly within seconds. Because these identifiers are essential to the site functioning correctly, they are not subject to the consent banner described in Section 5 and cannot be individually disabled without affecting basic operation. Despite being essential, these identifiers do not contain your name, email address, or message content and are deleted automatically when the session ends.

  • a) Load balancing: directs a request to the correct server during your visit.
  • b) Abuse prevention: recognizes automated or repeated submissions.
  • c) Consent status: essential, therefore not covered by the optional cookie banner.

3. Preference storage

The cookieChoice value records whether you selected Accept or Reject in the banner. It lasts up to 12 months unless you clear browser storage sooner. It does not contain your name or contact details. Storing this choice for up to 12 months means you are not asked to repeat the decision on every single visit during that period, which keeps the banner from becoming a recurring interruption. If you clear your browser's site data, change browsers, or switch devices, the stored choice is lost and the banner will appear again on your next visit. The value itself is a simple marker, such as accepted or rejected, rather than a detailed record of your browsing activity. After 12 months, the preference naturally expires and the banner reappears so you can confirm or change your choice.

  • a) Storage location: browser local storage on the device used to make the choice.
  • b) Duration: up to 12 months, or until browser data is cleared.
  • c) Content: a simple accepted-or-rejected marker, no personal identifiers.

4. Analytics

Optional analytics may measure page visits and broad technical patterns only after consent. A typical analytics identifier may last 13 months, while temporary campaign information may last 90 days. Bliro does not use analytics to infer medical conditions. Page visit measurement typically reports aggregated figures, such as how many readers viewed the movement or nutrition section in a given month, rather than a detailed log of one individual's path through the site. Broad technical patterns might include browser type or approximate region, used to understand whether the site renders correctly across common configurations. A temporary campaign identifier, lasting up to 90 days, may help us understand which referring page led to a visit without permanently linking that visit to a specific person. If you decline analytics in the banner, no analytics identifier is set, and your visit is not included in any aggregated reporting.

  • a) Aggregated reporting: page-level visit counts rather than individual visitor logs.
  • b) Standard identifier: lifespan up to 13 months, used only after consent.
  • c) Campaign identifier: shorter-lived, typically expiring within 90 days.

5. Your choices

You can reject optional cookies in the banner, clear storage through browser settings, or contact Bliro. Blocking essential technologies may affect site operation. Your choice does not affect access to editorial pages. Rejecting optional cookies in the banner takes effect immediately and prevents any analytics identifier from being set for that visit. Clearing storage through your browser's own settings removes both the cookieChoice preference and any analytics identifier already present, which also means the banner will reappear on your next visit. If you contact Bliro to ask about your current cookie status, we can explain the general categories in use but cannot look up an individual browser's storage remotely. Regardless of your choice, every article, resource page, and contact form remains fully accessible, since essential technologies are limited to basic delivery and security rather than gating content.

  • a) Banner choice: rejects optional analytics immediately for that visit.
  • b) Browser settings: clears both preference and analytics storage.
  • c) Content access: unaffected by either choice.

6. Third parties

Service providers may process technical information to host, secure, or measure the site. They must follow their own notices and applicable contractual safeguards. Bliro does not sell cookie data. A hosting provider processes technical request data to deliver pages and protect against abusive traffic, under a written agreement limiting use to that purpose. An analytics provider, where enabled, processes pseudonymous visit data under similar contractual restrictions and its own published privacy notice, which we encourage interested readers to review. These providers do not receive your name, email address, or message content merely because you visited the site; that information is only involved when you actively submit the contact form, as described in the privacy policy. Bliro does not permit a service provider to repurpose cookie data for that provider's own independent advertising.

  • a) Hosting provider: technical request data for delivery and abuse prevention.
  • b) Analytics provider: pseudonymous visit data, only after consent.
  • c) No resale: cookie data is not sold or repurposed for third-party advertising.

7. Mobile devices

Mobile browsers may use local storage in place of traditional cookies. The same purpose and retention principles apply. Device settings can usually clear both types of data. Many mobile browsers restrict traditional cookies by default, so a site like Bliro may rely more heavily on local storage to remember a simple preference such as cookieChoice. The practical effect for a reader is the same regardless of the underlying technology, including the 12-month preference duration described in Section 3 and the 13-month analytics ceiling described in Section 4. On most mobile operating systems, clearing browsing data or site data through the device or browser settings menu removes stored preferences and analytics identifiers together. Switching between a mobile browser and a desktop browser on the same device is treated as two separate storage contexts, so a preference set on one will not automatically apply to the other.

  • a) Local storage: functionally equivalent to a cookie for preference purposes.
  • b) Retention: same durations apply as described in Sections 3 and 4.
  • c) Cross-browser behavior: a preference set in one browser does not transfer to another.

8. International use

Some infrastructure may process technical data outside Indonesia. Transfers are limited to service delivery and protected through appropriate operational or contractual measures. A content delivery network, for example, may cache non-personal technical data at a regional server location closer to the reader to improve loading speed. Where an analytics or hosting partner is based outside Indonesia, the written agreement with that partner requires safeguards consistent with Law No. 27 of 2022, mirroring the approach described in the privacy policy's international transfers section. These transfers involve technical identifiers rather than the content of personal messages, which are handled separately as described in Section 6 of the privacy policy. Bliro reviews its infrastructure providers periodically to confirm that any cross-border processing remains limited to what service delivery genuinely requires.

  • a) Content delivery: regional caching of technical, non-personal data for speed.
  • b) Contractual safeguards: required of any provider operating outside Indonesia.
  • c) Periodic review: infrastructure providers reassessed for continued necessity.

9. Contact

For a cookie question, contact Jalan Cempaka Putih Raya No. 15, RT.005/RW.001, Cempaka Putih Timur, Jakarta Pusat 10510, Indonesia, or +62 21 7890 3215. A written letter is appropriate for a formal or detailed inquiry, while a phone call during Jakarta business hours is often faster for a quick clarification about how a specific technology works. We aim to respond to cookie-related questions within the same general timeframe described in the privacy policy, typically within 30 days for a substantive request. If your question relates to your own browser's current storage rather than our general practice, we may ask you to describe the device and browser you are using so our explanation is relevant. Questions about broader personal data rights, such as access or deletion requests, are handled under the privacy policy rather than this page. We log the date a cookie-related question is received so that, where a pattern of similar questions emerges, we can consider clarifying this page in a future revision.

  • a) Written inquiries: sent to the postal address above for formal questions.
  • b) Phone inquiries: available during Jakarta business hours for quick clarification.
  • c) Related rights requests: handled under the privacy policy, not this page.

10. Revision history

This policy was reviewed on 1 October 2026. Earlier wording was replaced to clarify preference storage and analytics duration. Future edits will carry a visible date. The 1 October 2026 review added the specific 12-month preference duration in Section 3 and the 13-month analytics ceiling in Section 4, which the original January publication described only in general terms. A future change that introduces a new category of optional technology, such as a new measurement tool, will be reflected on this page with an updated reviewed date and a brief explanation of what changed. Minor clarifications that do not alter practice, such as rewording a sentence for clarity, may not always warrant a separate announcement but are still captured in the reviewed date shown at the top. Readers who want to understand exactly what changed between versions may contact the editorial desk using the details in Section 9.

  • a) 1 January 2026: initial publication of this cookie policy.
  • b) 1 October 2026: added specific retention durations for preference and analytics storage.
  • c) Future updates: announced with a revised date and a short explanation of the change.