Privacy and Cookie Policies on Your Website: What They Must Include

By · 21 November 2026 · 4 min read

Illustration of a privacy policy page and a cookie banner with accept and reject options

Many company websites have a privacy policy copied from a template, sometimes from another company or written for another country's laws. What it says doesn't match what the website actually does. Others show a cookie banner, but the analytics tools keep running even when a visitor clicks "Reject".

This article covers what a company website in Indonesia should have in its privacy policy and cookie settings, with reference to Law Number 27 of 2022 on Personal Data Protection (Undang-Undang Nomor 27 Tahun 2022 tentang Pelindungan Data Pribadi, the UU PDP). It is not legal advice. To draft or review your policy, involve a legal adviser.

Why you need a privacy policy

The UU PDP sets the principle that personal data is collected in a limited, specific, lawful and transparent way, and processed with notice of its purpose and activities (Article 16(2)). Where the basis for processing is consent, Article 21 requires the Personal Data Controller to give the data subject certain information. On a website, the privacy policy is the natural place to give it.

The services you use may have their own conditions too. The Google Analytics terms of service, for example, require users to post a privacy policy that gives notice of the use of cookies, and to disclose that the website uses Google Analytics and how it collects and processes data.

What it should contain

Article 21(1) of the UU PDP lists the information that must be given when processing is based on consent. The list can serve as the framework for your privacy policy:

  • Legality of processing: your legal basis for processing the data.
  • Purpose of processing: for example answering quote requests, handling job applications or measuring visits.
  • Type and relevance of data: what data is collected from forms, cookies and other services.
  • Retention period of documents containing personal data, and the processing period.
  • Details of the information collected.
  • The data subject's rights, and how to exercise them.

Also add what makes the policy usable: the company name and a contact that someone actually reads, other parties that process data (hosting, form services, analytics), how you keep data secure, and the date of the last update. Article 21(2) requires you to notify data subjects before that information changes, so plan how you will do that too.

Cookies and personal data

A cookie is a small file the browser stores at a website's request. Some are needed for the website to work, for example to keep a login session. Others are for analytics or advertising. For example, according to Google's documentation, Google Analytics 4 sets a _ga cookie to distinguish users, with a default lifetime of two years.

The UU PDP doesn't use the word "cookie". But it defines personal data as data about a person who is identified or identifiable, on its own or combined with other information, directly or indirectly. Whether the data from a particular cookie on your website counts as personal data is a question for a legal adviser. Many companies choose to be careful and ask for consent for cookies that aren't strictly necessary.

An honest cookie banner

A cookie banner is only useful if the website behaves according to the visitor's choice. A few practical principles:

  • First list every cookie and script the website loads, including those from plugins, chat widgets, embedded videos and advertising pixels.
  • Group them: strictly necessary, analytics and advertising.
  • Don't load tools that aren't strictly necessary until the visitor agrees. Google offers consent mode to adjust how Google tags behave based on consent. Its documentation says no consent values are set by default, so the website owner has to set them.
  • Track nothing until the visitor allows it, don't pre-tick any option, and explain in your privacy policy how to withdraw consent (for example, by clearing the site's cookies).
  • Provide a way to change the choice at any time, such as a "Cookie settings" link at the bottom of the page.

A small example from our own website: since 13 October 2026, digimasi.com asks visitors for consent before loading Google Analytics.

Common mistakes

  • Copying a policy from another website, complete with another company's name, services or irrelevant foreign laws.
  • Policy and reality don't match: the policy says there are no advertising trackers, but an advertising pixel is installed.
  • A banner that is just decoration: analytics scripts run before or after the visitor rejects them.
  • English only, when most visitors read Indonesian. Article 22 asks for consent requests in simple, clear language.
  • A contact nobody reads: requests for access or deletion land in an inbox that is never opened.

Keeping the policy accurate

A privacy policy isn't a one-off document. Name one person responsible, and review it every time the website changes: a new form, a new analytics tool, a new vendor or a server move. If your website is multilingual, make sure every language version says the same thing and is updated at the same time. Keep records of consent too, because Article 24 requires the Personal Data Controller to be able to show proof of the consent given.

For the wider obligations, read Indonesia's Personal Data Protection Law and your company website. If your website has transactions or user accounts, read also whether your website must register as a PSE.

A good privacy policy isn't the longest one, but the one that most honestly describes what your website does.

We can help on the technical side: listing the cookies and scripts on your website, and making sure tools that aren't strictly necessary only load after the visitor agrees. The policy itself still needs reviewing by your legal adviser. Get in touch.