NutriBali NutriBali
Overhead view of a nutrition consultation table with empty cups, a blank notepad and a kitchen scale in cool daylight

Website document

Cookie Policy

This page explains what cookies are, which ones this website uses, and how you can control them in your browser. It sits alongside the privacy policy, which covers personal data in more detail.

Read the privacy policy Contact the team

Read this first

A short version you can read in under a minute

Cookies are the reason a form can remember a half-typed answer when you change pages, and the reason a returning visitor does not see the same notice twice. On a site like this one, that is most of what they do.

NutriBali uses cookies to keep the site working, to understand which pages people actually read, and to hold small choices you have already made. They are not used to assemble an advertising profile of you, and the data they carry is not sold on.

If you would rather not have them, your browser is the place to act. You can view, block and delete cookies from every major browser's settings, and you can ask your browser to warn you before one is placed. Turning off the essential ones will break forms and parts of the site, so it is worth knowing which is which before you switch them off.

At a glance

Categories used on this site
4
Required for forms and security
1
Used to build ad profiles
None
Where you turn them off
Browser

Plain explanation

What cookies are

Cookies are small text files that a website asks your browser to store on your device. When you open another page on the same site, or come back later, the browser sends that file back so the site can recognise the request.

The important part is what they are not. A cookie is not a program, it does not run on its own, and it cannot read other files on your device. It holds a short label and a value — usually a session identifier, a language choice, or a simple yes-or-no that a notice has been shown.

Some cookies last only while your browser is open. Others stay for a set period so that a preference survives a restart. Which of the two applies depends on the purpose, not on the site's preference.

Person's hands at a kitchen table with a laptop angled away so the screen is not legible, beside a glass of water
Browser settings, not the site itself, are where you see, block and delete the cookies a website has placed.
Bright prep counter with shallow bowls of cut vegetables, a mortar and pestle and a knife on a wooden board

Reasons and limits

Why this site uses cookies

Two jobs come first. Cookies keep pages behaving consistently as you move between them, and they keep forms working — a registration form or a contact message needs to know that the fields you filled in belong to the same visit.

The second job is quieter. Aggregated visit information shows which pages people actually finish reading and where they tend to leave. That shapes how the meal planning material is organised and which explanations sit close to which examples. The numbers describe pages, not people.

What we do not do with them

  • We do not build advertising profiles of individual visitors.
  • We do not sell cookie data, and it is not shared for advertising purposes.
  • We do not use a cookie to follow you to other websites after you leave.

The privacy policy describes how personal data is handled overall, including what happens after a registration or contact message.

Read the privacy policy
Matte kitchen scale beside two shallow ceramic dishes of lentils and rice in cool daylight
Measurement and record-keeping live in different places: page totals describe the site, while personal records are handled under the privacy policy.

Where the line sits

Cookies and personal data

Most of the cookies used here carry no name, no email address and no phone number. A session identifier tells the server that two requests came from the same browser; it does not tell us who is sitting at that browser.

There is one case where the two meet. If a cookie is connected to a registration or a contact message you sent, the personal data involved is handled exactly as the privacy policy describes — the cookie is the link between the request and the form submission, not a separate record.

Beyond that, cookie data is not sold, and it is not shared with advertising networks. If you send us a question about a specific cookie, it helps to include the page you were on and what you were doing at the time, so the answer can point at the actual behaviour rather than a general description.

Contact the team

Practical steps

Managing cookies in your browser

Every major browser lets you look at the cookies a site has stored, remove individual ones, and block a site or a category from placing new ones. The controls sit under a privacy or site-data section of the browser's settings, and the wording differs slightly between them.

  1. Open your browser's privacy or site-data settings

    You will usually find a list of stored items grouped by website, with the number of cookies each one is holding.

  2. Read before you delete

    Names like session or preference usually point at the categories on this page. Removing them is reversible; the site will simply set them again on your next visit.

  3. Set a warning instead of blocking

    Most browsers can notify you each time a site tries to place a cookie, which is a slower way to browse but gives you the choice every time.

  4. Remember what the essential ones carry

    Blocking those may stop the registration form and the contact form from submitting, and some pages may load without their usual behaviour.

Outside our control

Third-party content

Occasionally a page embeds content that belongs to another service. When that content loads, the service behind it may place its own cookies — for example to remember that a player was already opened or to measure how the embedded item performed.

We do not control those cookies and cannot read them. Their purpose, lifetime and opt-out route are described in that provider's own cookie and privacy documentation, which is worth checking before you interact with the embedded content.

If a provider's documentation is unclear to you, send us the page and the item you were looking at. We can tell you which service was involved, even where the cookie itself is theirs.